Final Update: Sunday, 26 June 2022 17:55 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/26, 14:25 UTC. Our logs show the incident started on 06/26, 13:40 UTC and that during the hours that it took to resolve the issue customers experienced issues with data access, missed or delayed log search alerts, data gaps and data latency.
-Arish Balasubramani
We've confirmed that all systems are back to normal with no customer impact as of 06/26, 14:25 UTC. Our logs show the incident started on 06/26, 13:40 UTC and that during the hours that it took to resolve the issue customers experienced issues with data access, missed or delayed log search alerts, data gaps and data latency.
- Root Cause: Engineers determined that the backend downstream service degraded to a bad state, causing this issue to happen.
- Mitigation: Engineers determined that the impacted backend downstream service started to recover automatically by Scaling out to mitigate this issue.
- Incident Timeline: 06/26, 13:40 UTC through 06/26, 14:25 UTC
-Arish Balasubramani
Published Jun 26, 2022
Version 1.0
Azure-Monitor-Team
Microsoft
Microsoft
