Home
%3CLINGO-SUB%20id%3D%22lingo-sub-809552%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2008%2F17%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809552%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Saturday%2C%2017%20August%202019%2018%3A12%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F17%2C%2017%3A00%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F17%2C%2015%3A15%20UTC%20and%20that%20during%20the%202%20hours%20and%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%2C%26nbsp%3B%20customers%20using%20non-retrying%20SDKs%20in%20the%20North%20Europe%20region%20could%20have%20experienced%20up%20to%202.6%25%20data%20loss.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%26quot%3BSegoeUI%26quot%3B%2C%26quot%3BLato%26quot%3B%2C%26quot%3BHelvetica%20Neue%26quot%3B%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3EThe%20failure%20was%20due%20to%20one%20of%20our%20backend%20services%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%2045%20minutes%20-%2008%2F17%2C%2015%3A15%20UTC%20through%2008%2F17%2C%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Application%20Insights%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Eric%20Singleton%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-809552%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 17 August 2019 18:12 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/17, 17:00 UTC. Our logs show the incident started on 08/17, 15:15 UTC and that during the 2 hours and 45 minutes that it took to resolve the issue,  customers using non-retrying SDKs in the North Europe region could have experienced up to 2.6% data loss.
  • Root Cause: The failure was due to one of our backend services
  • Incident Timeline: 2 Hours & 45 minutes - 08/17, 15:15 UTC through 08/17, 17:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Eric Singleton