Final Update: Wednesday, 13 July 2022 13:00 UTC
We've confirmed that all systems are back to normal with no customer impact as of 7/13, 12:30 UTC. Our logs show the incident started on 7/13, 11:05 UTC and that during the 1 hour 25 minutes that it took to resolve the issue, some of customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in Australia Southeast region.
-Ashok
We've confirmed that all systems are back to normal with no customer impact as of 7/13, 12:30 UTC. Our logs show the incident started on 7/13, 11:05 UTC and that during the 1 hour 25 minutes that it took to resolve the issue, some of customers using Log Analytics and Azure sentinel may have experienced data access issue and delayed or missed alerts in Australia Southeast region.
- Root Cause: The failure was due to dependent backend service which Azure Log Analytics relies upon became unhealthy.
- Incident Timeline: 1 Hours & 25 minutes - 7/13, 11:05 UTC through 7/13, 12:30 UTC
-Ashok
Initial Update: Wednesday, 13 July 2022 12:07 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may experience data access issue and delayed or missed alerts in Australia South East.
We are aware of issues within Log Analytics and are actively investigating. Some customers using Log Analytics and Azure sentinel may experience data access issue and delayed or missed alerts in Australia South East.
- Work Around: None
- Next Update: Before 07/13 14:30 UTC
-Ashok
Updated Jul 13, 2022
Version 2.0
Azure-Monitor-Team
Microsoft
Microsoft
