Final Update: Monday, 06 January 2020 20:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/6, 19:45 UTC. Our logs show the incident started on 1/6, 18:30 UTC and that during the 1 hour 15 minutes that it took to resolve the issue 6.4% of customers experienced data access in the Azure portal, query failures for Log Analytics and alerting failures for Log Search Alerts.
-Jeff
We've confirmed that all systems are back to normal with no customer impact as of 1/6, 19:45 UTC. Our logs show the incident started on 1/6, 18:30 UTC and that during the 1 hour 15 minutes that it took to resolve the issue 6.4% of customers experienced data access in the Azure portal, query failures for Log Analytics and alerting failures for Log Search Alerts.
- Root Cause: The failure was due to an unhealthy backend service response.
- Incident Timeline: 1 Hours & 15 minutes - 1/6, 18:30 UTC through 1/6, 19:45 UTC
-Jeff
Initial Update: Monday, 06 January 2020 19:44 UTC
We are aware of issues within Log Search Alerts in the West EU region and are actively investigating. Some customers may experience data access in the Azure portal, query failures for Log Analytics and alerting failures for Log Search Alerts..
-Jeff
We are aware of issues within Log Search Alerts in the West EU region and are actively investigating. Some customers may experience data access in the Azure portal, query failures for Log Analytics and alerting failures for Log Search Alerts..
- Next Update: Before 01/06 21:00 UTC
-Jeff
Updated Jan 06, 2020
Version 3.0