Final Update: Monday, 27 June 2022 22:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/27, 21:40 UTC. Our logs show the incident started on 06/27 17:55 UTC and that during the 3 hours & 45 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.
-Vignesh
We've confirmed that all systems are back to normal with no customer impact as of 06/27, 21:40 UTC. Our logs show the incident started on 06/27 17:55 UTC and that during the 3 hours & 45 minutes that it took to resolve the issue some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.
- Root Cause: The failure was due to degraded downstream dependency.
- Impacted Region: UsGovVirginia
- Incident Timeline: 3 Hours & 45 minutes - 06/27 17:55 UTC through 06/27, 21:40 UTC
-Vignesh
Update: Monday, 27 June 2022 20:49 UTC
We continue to investigate issues within Log Analytics & Azure Sentinel. Root cause is not fully understood at this time. Some customers continue to experience data access issues and delayed or missed alerts. Initial findings indicate that the problem began at 06/27 17:55 UTC. We currently have no estimate for resolution.
We continue to investigate issues within Log Analytics & Azure Sentinel. Root cause is not fully understood at this time. Some customers continue to experience data access issues and delayed or missed alerts. Initial findings indicate that the problem began at 06/27 17:55 UTC. We currently have no estimate for resolution.
- Work Around: None
- Next Update: Before 06/27 22:00 UTC
Updated Jun 27, 2022
Version 3.0
Azure-Monitor-Team
Microsoft
Microsoft
