Final Update: Thursday, 01 August 2019 20:30 UTC
We've confirmed that all systems are back to normal with no customer impact as of 8/01, 20:30 UTC. Our logs show the incident started on 8/01, 18:43 UTC and during the 1 hours and 47 minutes that it took to resolve the issue some customers might have experienced Alerting failure issues in East US region.
-Ian Cairns
We've confirmed that all systems are back to normal with no customer impact as of 8/01, 20:30 UTC. Our logs show the incident started on 8/01, 18:43 UTC and during the 1 hours and 47 minutes that it took to resolve the issue some customers might have experienced Alerting failure issues in East US region.
- Root Cause: The failure was due to issues in one of our backend services.
- Incident Timeline: 1 Hours & 47 minutes - 8/01, 18:43 UTC through 8/01, 20:30 UTC
-Ian Cairns
Initial Update: Thursday, 01 August 2019 20:26 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience Alerting failures and data latency issues.
-Ian Cairns
We are aware of issues within Log Search Alerts and are actively investigating. Some customers may experience Alerting failures and data latency issues.
- Work Around: None
- Next Update: Before 08/01 22:30 UTC
-Ian Cairns
Updated Aug 01, 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