Final Update: Tuesday, 21 May 2019 13:44 UTC
We've confirmed that all systems are back to normal with no customer impact as of 5/21, 12:41 UTC. Our logs show the incident started on 5/21, 06:41 UTC and that during the 6 hours and 32 minutes that it took to resolve the issue customers in EUS, WCUS and France central experienced alerting failures.
-Madhuri
We've confirmed that all systems are back to normal with no customer impact as of 5/21, 12:41 UTC. Our logs show the incident started on 5/21, 06:41 UTC and that during the 6 hours and 32 minutes that it took to resolve the issue customers in EUS, WCUS and France central experienced alerting failures.
- Root Cause: The failure was due to the issue in one of our dependent services.
- Incident Timeline: 6 Hours & 32 minutes - 5/21, 06:09 UTC through 5/21, 12:41 UTC
-Madhuri
Update: Tuesday, 21 May 2019 12:48 UTC
Root cause has been isolated to failure in one of our dependent services which was impacting Alerting service. To address this issue we are working on bringing the service back. Some customers in WCUS, EUS and France Central may experience alerting failures.
Root cause has been isolated to failure in one of our dependent services which was impacting Alerting service. To address this issue we are working on bringing the service back. Some customers in WCUS, EUS and France Central may experience alerting failures.
- Work Around: None
- Next Update: Before 05/21 17:00 UTC
Updated May 21, 2019
Version 2.0Azure-Monitor-Team
Former Employee
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity