Final Update: Wednesday, 13 July 2022 07:07 UTC
We've confirmed that all systems are back to normal with no customer impact as of 7/13, 05:20 UTC. Our logs show the incident started on 7/13, 04:40 UTC and that during the 40 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 in North Central US region.
-Ashok
We've confirmed that all systems are back to normal with no customer impact as of 7/13, 05:20 UTC. Our logs show the incident started on 7/13, 04:40 UTC and that during the 40 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 in North Central US region.
- Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
- Incident Timeline: 40 minutes - 7/13, 04:40 UTC through 7/13, 05:20 UTC
-Ashok
Initial Update: Wednesday, 13 July 2022 05:29 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.
-Anmol
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts.
- Work Around: None
- Next Update: Before 07/13 07:30 UTC
-Anmol
Updated Jul 13, 2022
Version 3.0
Azure-Monitor-Team
Microsoft
Microsoft
