This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 08 April 2020 01:03 UTC
We've confirmed that all systems are back to normal with no customer impact as of 4/8, 00:35 UTC. Our logs show the incident started on 4/7, 23:04 UTC impacting the West Europe region. During the 1 hour and 31 minutes it took to resolve the issue, customers may have experienced data access issues as well as missed or delayed Log Search Alerts.
-Ian
We've confirmed that all systems are back to normal with no customer impact as of 4/8, 00:35 UTC. Our logs show the incident started on 4/7, 23:04 UTC impacting the West Europe region. During the 1 hour and 31 minutes it took to resolve the issue, customers may have experienced data access issues as well as missed or delayed Log Search Alerts.
- Root Cause: The failure was due to a back end service that had become unhealthy.
- Incident Timeline: 1 Hours & 31 minutes - 4/7, 23:04 UTC through 4/8, 00:35 UTC
-Ian
Initial Update: Tuesday, 07 April 2020 23:35 UTC
We are aware of issues within Log Analytics in West Europe and are actively investigating. Some customers may experience data access issues as well as missed or delayed Log Search Alerts in this region. This would have started at 23:04 4/7 UTC.
- Work Around: None
- Next Update: Before 04/08 01:00 UTC
-Ian