Final Update: Sunday, 20 September 2020 15:38 UTC
We've confirmed that all systems are back to normal with no customer impact as of 09/20, 14:05 UTC. Our logs show the incident started on 09/20, 12:35 UTC and that during the 1 hours 30 minutes that it took to resolve the issue, some customers from Australia South East region may have experienced failures while accessing their data. Customers who have setup Log Search alerts in this region may also have experienced failures accessing alerts and action rules for the resources.
-Madhav
We've confirmed that all systems are back to normal with no customer impact as of 09/20, 14:05 UTC. Our logs show the incident started on 09/20, 12:35 UTC and that during the 1 hours 30 minutes that it took to resolve the issue, some customers from Australia South East region may have experienced failures while accessing their data. Customers who have setup Log Search alerts in this region may also have experienced failures accessing alerts and action rules for the resources.
- Root Cause: The failure was due to <provide a transparent failure statement but don't mention specific technologies>.
- Incident Timeline: 1 Hours & 30 minutes - 09/20, 12:35 UTC through 09/20, 14:05 UTC
-Madhav
Initial Update: Sunday, 20 September 2020 14:10 UTC
We are aware of issues within Log Analytics and Log Search Alerts and are actively investigating. Some customers in Australia South East region may experience intermittent data access issues when accessing application data. Customers that have set up Log Search Alerts may experience those alerts missing or being delayed.
-Madhav
We are aware of issues within Log Analytics and Log Search Alerts and are actively investigating. Some customers in Australia South East region may experience intermittent data access issues when accessing application data. Customers that have set up Log Search Alerts may experience those alerts missing or being delayed.
- Work Around: None
- Next Update: Before 09/20 16:30 UTC
-Madhav
Updated Sep 20, 2020
Version 3.0