Final Update: Monday, 08 June 2020 16:15 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/08, 16:10 UTC. Our logs show the incident started on 6/08, 12:00 UTC and that during the 4 hours and 10 minutes that it took to resolve the issue, customers may have experience intermittent data latency and incorrect alert activation for Heartbeat, Perf and SecurityEvent in the East us Region
- Root Cause: The failure was due to one of our dependent services.
- Incident Timeline: 4 Hours & 10 minutes - 06/08, 12:00 UTC through 06/08, 16:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Eric Singleton
Initial Update: Monday, 08 June 2020 14:40 UTC
We are aware of issues within Azure Log Analytics and are actively investigating. Some of the customers may experience intermittent data latency and incorrect alert activation for Heartbeat, Perf and SecurityEvent in East US region.
- Work Around: none
- Next Update: Before 06/08 19:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Syed
