%3CLINGO-SUB%20id%3D%22lingo-sub-1434177%22%20slang%3D%22en-US%22%3EExperiencing%20Latency%20and%20Data%20Gaps%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2006%2F02%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1434177%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%20Tuesday%2C%2002%20June%202020%2018%3A31%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%206%2F2%2C%2016%3A32%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%206%2F2%2C%2015%3A24%20UTC%20and%20that%20during%20the%201%20hour%20and%208%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20experienced%20intermittent%20data%20latency%2C%20data%20gaps%20and%20incorrect%20alert%20activation..%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20a%20dependent%20backend%20service%20going%20into%20a%20bad%20state%20and%20auto-mitigation%20taking%20slightly%20longer%20than%20expected.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hours%20%26amp%3B%208%20minutes%20-%206%2F2%2C%2015%3A24%20UTC%20through%206%2F2%2C%2016%3A32%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-Jeff%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-1434177%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 02 June 2020 18:31 UTC

We've confirmed that all systems are back to normal with no customer impact as of 6/2, 16:32 UTC. Our logs show the incident started on 6/2, 15:24 UTC and that during the 1 hour and 8 minutes that it took to resolve the issue some customers experienced intermittent data latency, data gaps and incorrect alert activation..
  • Root Cause: The failure was due to a dependent backend service going into a bad state and auto-mitigation taking slightly longer than expected.
  • Incident Timeline: 1 Hours & 8 minutes - 6/2, 15:24 UTC through 6/2, 16:32 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Jeff