Experiencing Alerting Failure issue in Azure Portal for Many Data Types - 01/31 - Resolved

Published Jan 31 2022 10:42 AM 617 Views
Final Update: Monday, 31 January 2022 19:47 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/31, 19:15 UTC. Our logs show the incident started on 01/31, 14:30 UTC and that during the 4 hours and 45 minutes that it took to resolve the issue some customers using Azure Monitor may have experienced delayed Alerts notification up to 2 hours.
  • Root Cause: The failure was due to an issue in one of our backend services.
  • Incident Timeline: 4 Hours & 45 minutes - 01/31, 14:30 UTC through 01/31, 19:15 UTC
We understand that customers rely on Azure Monitor as a critical service and apologize for any impact this incident caused.

-Saika

Initial Update: Monday, 31 January 2022 18:39 UTC

We are aware of issues within Azure Monitor and are actively investigating. Some customers using Azure Monitor may experience issues with delayed Alerts notification.
  • Work Around: None
  • Next Update: Before 01/31 22:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Saika

%3CLINGO-SUB%20id%3D%22lingo-sub-3094604%22%20slang%3D%22en-US%22%3EExperiencing%20Alerting%20Failure%20issue%20in%20Azure%20Portal%20for%20Many%20Data%20Types%20-%2001%2F31%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3094604%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%20Monday%2C%2031%20January%202022%2019%3A47%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F31%2C%2019%3A15%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F31%2C%2014%3A30%20UTC%20and%20that%20during%20the%204%20hours%20and%2045%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20using%20Azure%20Monitor%20may%20have%20experienced%20delayed%20Alerts%20notification%20up%20to%202%20hours.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20an%20issue%20in%20one%20of%20our%20backend%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%204%20Hours%20%26amp%3B%2045%20minutes%20-%2001%2F31%2C%2014%3A30%20UTC%20through%2001%2F31%2C%2019%3A15%20UTC%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-Saika%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%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%3EInitial%20Update%3C%2FU%3E%3A%20Monday%2C%2031%20January%202022%2018%3A39%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitor%20and%20are%20actively%20investigating.%20Some%20customers%20using%20Azure%20Monitor%20may%20experience%20issues%20with%20delayed%20Alerts%20notification.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F31%2022%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Saika%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Jan 31 2022 12:04 PM
Updated by: