%3CLINGO-SUB%20id%3D%22lingo-sub-744227%22%20slang%3D%22en-US%22%3EExperienced%20error%20on%20Alerts%20Summary%20page%20for%20Azure%20Monitor%20in%20Azure%20Portal-07%2F09%20-Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-744227%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%2009%20July%202019%2007%3A49%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2007%2F09%2C%2006%3A30%20AM%20UTC.%20Our%20logs%20show%20that%20the%20incident%20started%20on%2007%2F09%2C%2012%3A00%20AM%20UTC%20and%20that%20during%20the%206%20hours%2030%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20would%20have%20experienced%20error%20while%20accessing%20Alerts%20Summary%20page%20under%20Azure%20Monitor%20in%20Azure%20Portal.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20in%20one%20of%20our%20back-end%20services%20which%20went%20in%20to%20unhealthy%20state%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%206%20Hours%20%26amp%3B%2030%20minutes%20-%2007%2F09%2C%2012%3A00%20AM%20UTC%26nbsp%3Bthrough%2007%2F09%2C%2006%3A30%20AM%20UTC%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Sapna%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-744227%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Tuesday, 09 July 2019 07:49 UTC

We've confirmed that all systems are back to normal with no customer impact as of 07/09, 06:30 AM UTC. Our logs show that the incident started on 07/09, 12:00 AM UTC and that during the 6 hours 30 minutes that it took to resolve the issue some customers would have experienced error while accessing Alerts Summary page under Azure Monitor in Azure Portal.
  • Root Cause: The failure was due to issues in one of our back-end services which went in to unhealthy state
  • Incident Timeline: 6 Hours & 30 minutes - 07/09, 12:00 AM UTC through 07/09, 06:30 AM UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Sapna