Final Update: Monday, 15 March 2021 00:21 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/15, 00:21 UTC. Our logs show the incident started on 03/14 , 23:42 UTC and that during the 39 minutes that it took to resolve the issue some of customers experienced ingesting telemetry in East US 2 intermittent data latency, data gaps and incorrect alert activation.
-Subhash
We've confirmed that all systems are back to normal with no customer impact as of 03/15, 00:21 UTC. Our logs show the incident started on 03/14 , 23:42 UTC and that during the 39 minutes that it took to resolve the issue some of customers experienced ingesting telemetry in East US 2 intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to one of the dependent services being unhealthy.
- Incident Timeline: 0 Hours & 39 minutes - 03/14, 23:42 UTC through 03/15, 00:21 UTC
-Subhash
Updated Mar 15, 2021
Version 3.0Azure-Monitor-Team
Silver Contributor
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity