%3CLINGO-SUB%20id%3D%22lingo-sub-1564563%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20failure%20for%20Azure%20Monitor%20-%2008%2F04%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1564563%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%20Tuesday%2C%2004%20August%202020%2007%3A38%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3E%3CDIV%20style%3D%22%22%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2008%2F04%2C%2002%3A42%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2008%2F04%2C%2000%3A35%20UTC%20and%20that%20during%20the%202%20hours%20and%207%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20the%20customers%20might%20have%20experienced%20delayed%20alerts.%20Alerts%20would%20have%20eventually%20fired.%20%3C%2FSPAN%3E%3CUL%20style%3D%22%22%3E%0A%20%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20back-end%20services.%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%20%3CLI%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%202%20Hours%20%26amp%3B%207%20minutes%20-%2008%2F04%2C%2000%3A35%20UTC%20through%2008%2F04%2C%2002%3A42%20UTC%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%3CSPAN%20style%3D%22font-family%3A%20Helvetica%3B%22%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3C%2FSPAN%3E%3C%2FDIV%3E%3CBR%20%2F%3E-Saika%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%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1564563%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 04 August 2020 07:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 08/04, 02:42 UTC. Our logs show the incident started on 08/04, 00:35 UTC and that during the 2 hours and 7 minutes that it took to resolve the issue some of the customers might have experienced delayed alerts. Alerts would have eventually fired.
  • Root Cause: The failure was due to an issue in one of our back-end services. 
  • Incident Timeline: 2 Hours & 7 minutes - 08/04, 00:35 UTC through 08/04, 02:42 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Saika