Final Update: Saturday, 18 January 2020 13:18 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/18, 13:00 UTC. Our logs show the incident started on 01/18, 07:39 UTC and that during the 5 hours 21 minutes that it took to resolve the issue some of customers in West Europe Region might have experienced data access and data latency issue in the Azure portal and failures when queried through API for Log analytics and alerting failure and delays for log search alerts.
-Monish
We've confirmed that all systems are back to normal with no customer impact as of 01/18, 13:00 UTC. Our logs show the incident started on 01/18, 07:39 UTC and that during the 5 hours 21 minutes that it took to resolve the issue some of customers in West Europe Region might have experienced data access and data latency issue in the Azure portal and failures when queried through API for Log analytics and alerting failure and delays for log search alerts.
- Root Cause: The failure was due to an issue with one of our dependent service.
- Incident Timeline: 5 Hours & 21 minutes - 01/18, 07:39 UTC through 01/18, 13:00 UTC
-Monish
Initial Update: Saturday, 18 January 2020 09:12 UTC
We are aware of issues within Log Analytics and Log Search Alerts and are actively investigating. Some customers in west Europe Region may experience data access issue in the Azure portal and failures when queried through API for Log Analytics and Alerting failure for Log Search alerts.
-Monish
We are aware of issues within Log Analytics and Log Search Alerts and are actively investigating. Some customers in west Europe Region may experience data access issue in the Azure portal and failures when queried through API for Log Analytics and Alerting failure for Log Search alerts.
- Work Around: None.
- Next Update: Before 01/18 13:30 UTC
-Monish
Updated Jan 18, 2020
Version 2.0