%3CLINGO-SUB%20id%3D%22lingo-sub-1410986%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20issue%20in%20Azure%20Portal%20in%20multiple%20regions%20-%2005%2F22%20-%20Resolved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1410986%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%20Friday%2C%2022%20May%202020%2011%3A05%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%205%2F22%2C%2011%3A02%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%205%2F11%2C%2012%3A00%20UTC%20and%20that%20during%20the%2010%20days%2C%2023%20hours%20and%202%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20of%20customers%20may%20have%20experienced%20issues%20viewing%20Azure%20Monitor%20Alerts%20in%20Azure%20portal%20in%20multiple%20regions.%20Alert%20Notifications%20are%20not%20impacted.%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%20dependent%20services.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%2010%20days%2C%2023%20Hours%20%26amp%3B%202%20minutes%20-%205%2F22%2C%2012%3A00%20UTC%20through%205%2F22%2C%2011%3A02%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Monitor%20Alerts%26nbsp%3Bas%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Madhuri%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%3CU%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2022%20May%202020%2010%3A41%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Azure%20Monitor%20Alerts.%20Root%20cause%20is%20not%20fully%20understood%20at%20this%20time.%20Some%20customers%20continue%20to%20experience%20issues%20viewing%20Azure%20Monitor%20Alerts%20in%20Azure%20portal%20in%20multiple%20regions.%20Alert%20Notifications%20are%20not%20impacted.%20We%20are%20working%20to%20establish%20the%20start%20time%20for%20the%20issue%2C%20initial%20findings%20indicate%20that%20the%20problem%20began%20at%205%2F11%20~12%3A00%20UTC.%20We%20currently%20have%20no%20estimate%20for%20resolution.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F22%2017%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3E-Madhuri%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%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Friday%2C%2022%20May%202020%2006%3A56%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Azure%20Monitor%20Alerts%20and%20are%20actively%20investigating.%20Some%20customers%20may%20experience%20issues%20viewing%20alerts%20in%20Azure%20portal%20in%20multiple%20regions.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20None.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2005%2F22%2011%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Madhuri%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1410986%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%20Log%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMetric%20Alerts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESmart%20Diagnostics%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 22 May 2020 11:05 UTC

We've confirmed that all systems are back to normal with no customer impact as of 5/22, 11:02 UTC. Our logs show the incident started on 5/11, 12:00 UTC and that during the 10 days, 23 hours and 2 minutes that it took to resolve the issue some of customers may have experienced issues viewing Azure Monitor Alerts in Azure portal in multiple regions. Alert Notifications are not impacted.
  • Root Cause: The failure was due to an issue in one of our dependent services.
  • Incident Timeline: 10 days, 23 Hours & 2 minutes - 5/22, 12:00 UTC through 5/22, 11:02 UTC
We understand that customers rely on Azure Monitor Alerts as a critical service and apologize for any impact this incident caused.

-Madhuri

Update: Friday, 22 May 2020 10:41 UTC

We continue to investigate issues within Azure Monitor Alerts. Root cause is not fully understood at this time. Some customers continue to experience issues viewing Azure Monitor Alerts in Azure portal in multiple regions. Alert Notifications are not impacted. We are working to establish the start time for the issue, initial findings indicate that the problem began at 5/11 ~12:00 UTC. We currently have no estimate for resolution.
  • Work Around: None. 
  • Next Update: Before 05/22 17:00 UTC
-Madhuri

Initial Update: Friday, 22 May 2020 06:56 UTC

We are aware of issues within Azure Monitor Alerts and are actively investigating. Some customers may experience issues viewing alerts in Azure portal in multiple regions.
  • Work Around: None. 
  • Next Update: Before 05/22 11:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Madhuri