%3CLINGO-SUB%20id%3D%22lingo-sub-1299795%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Latency%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2004%2F11%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1299795%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%2011%20April%202020%2012%3A53%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2004%2F11%2C%2012%3A47%20MM%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2004%2F11%2C%2011%3A07%20UTC%20and%20that%20during%20the%201%20hour%20%26amp%3B%2040%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20experienced%20data%20latency%20and%20%3CFONT%20face%3D%22%26quot%3BSegoe%20UI%26quot%3B%2Csystem-ui%2C%26quot%3BApple%20Color%20Emoji%26quot%3B%2C%26quot%3BSegoe%20UI%20Emoji%26quot%3B%2Csans-serif%22%3Emisfiring%20alerts%20in%20East%20US%20region%3C%2FFONT%3E.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20one%20of%20the%20back%20end%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2040%20minutes%20-%2004%2F11%2C%2011%3A07%20UTC%20through%2004%2F11%2C%2012%3A47%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-Satya%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-1299795%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Saturday, 11 April 2020 12:53 UTC

We've confirmed that all systems are back to normal with no customer impact as of 04/11, 12:47 MM UTC. Our logs show the incident started on 04/11, 11:07 UTC and that during the 1 hour & 40 minutes that it took to resolve the issue some of the customers experienced data latency and misfiring alerts in East US region.
  • Root Cause: The failure was due to one of the back end services.
  • Incident Timeline: 1 Hour & 40 minutes - 04/11, 11:07 UTC through 04/11, 12:47 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Satya