Home
%3CLINGO-SUB%20id%3D%22lingo-sub-809862%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2008%2F18%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809862%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%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EFinal%20Update%3C%2FU%3E%3A%20Sunday%2C%2018%20August%202019%2013%3A25%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%2F18%2C%2012%3A45%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F18%2C%2011%3A20%20UTC%20and%20that%20during%20the%201%20hours%2025%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20customers%20using%20non-retrying%20SDK's%20close%20to%20North%20Europe%20geographically%20region%20could%20have%20experienced%20up%20to%206.5%25%20data%20loss.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20our%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%2020%20minutes%20-%2008%2F18%2C%2011%3A20%20UTC%20through%2008%2F18%2C%2012%3A45%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-Monish%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-809862%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Sunday, 18 August 2019 13:25 UTC

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

-Monish