Final Update: Sunday, 22 May 2022 08:22 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/22, 07:19 UTC. Our logs show the incident started on 05/22, 04:44 UTC and that during the 2 hours and 36 minutes that it took to resolve the issue. Some customers using Application Insights components in USGOV Virginia ingesting telemetry in USGOV Texas and USDoD Central geographical regions may have experienced intermittent data latency, data gaps and incorrect alert activation.
-Anmol
We've confirmed that all systems are back to normal with no customer impact as of 05/22, 07:19 UTC. Our logs show the incident started on 05/22, 04:44 UTC and that during the 2 hours and 36 minutes that it took to resolve the issue. Some customers using Application Insights components in USGOV Virginia ingesting telemetry in USGOV Texas and USDoD Central geographical regions may have experienced intermittent data latency, data gaps and incorrect alert activation.
- Root Cause: The failure was due to backend dependent service becoming unhealthy.
- Incident Timeline: 2 Hours & 35 minutes - 05/22, 04:44 UTC through 05/22, 07:19 UTC
-Anmol
Updated May 22, 2022
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