Final Update: Tuesday, 13 April 2021 22:52 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/13, 22:42 UTC. Our logs show the incident started on 04/13, 19:20 UTC and that during the 3 hours and 22 minutes that it took to resolve the issue customers ingesting telemetry in their Log Analytics Workspace in West Europe geographical region may have experienced intermittent data latency and incorrect alert activation.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 04/13, 22:42 UTC. Our logs show the incident started on 04/13, 19:20 UTC and that during the 3 hours and 22 minutes that it took to resolve the issue customers ingesting telemetry in their Log Analytics Workspace in West Europe geographical region may have experienced intermittent data latency and incorrect alert activation.
- Root Cause: The failure was due to a backend dependency.
- Incident Timeline: 3 Hours & 22 minutes - 04/13, 19:20 UTC through 04/13, 22:42 UTC
-Eric Singleton
Initial Update: Tuesday, 13 April 2021 20:59 UTC
We are aware of issues within Log Analytics and are actively investigating. Customers ingesting telemetry in their Log Analytics Workspace in West Europe geographical region may have experienced intermittent data latency and incorrect alert activation.
-Eric Singleton
We are aware of issues within Log Analytics and are actively investigating. Customers ingesting telemetry in their Log Analytics Workspace in West Europe geographical region may have experienced intermittent data latency and incorrect alert activation.
- Work Around: None
- Next Update: Before 04/13 23:00 UTC
-Eric Singleton
Updated Apr 13, 2021
Version 2.0