%3CLINGO-SUB%20id%3D%22lingo-sub-2112584%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20latency%20Issue%20for%20Azure%20Monitor%20Service%20-%2002%2F03%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2112584%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%20Wednesday%2C%2003%20February%202021%2013%3A13%20UTC%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2002%2F03%2C%2012%3A03%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2002%2F03%2C%2007%3A58%20UTC%20and%20that%20during%20the%204%20Hours%20%26amp%3B%2005%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20may%20have%20experienced%20data%20latency%20and%20incorrect%20alert%20activation%20in%20South%20UK%20and%20South%20East%20Australia%20region.%3CBR%20%2F%3E%3CUL%20style%3D%22font-size%3A%2014px%3B%22%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20with%20one%20of%20our%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20%26amp%3B%205%20minutes%20-%2002%2F03%2C%2007%3A58%20UTC%20through%2002%2F03%2C%2012%3A03%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20Service%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Mohini%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-2112584%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Wednesday, 03 February 2021 13:13 UTC

We've confirmed that all systems are back to normal with no customer impact as of 02/03, 12:03 UTC. Our logs show the incident started on 02/03, 07:58 UTC and that during the 4 Hours & 05 minutes that it took to resolve the issue some customers may have experienced data latency and incorrect alert activation in South UK and South East Australia region.
  • Root Cause: The failure was due to an issue with one of our backend service.
  • Incident Timeline: 4 Hours & 5 minutes - 02/03, 07:58 UTC through 02/03, 12:03 UTC
We understand that customers rely on Azure Monitor Service as a critical service and apologize for any impact this incident caused.

-Mohini