This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Wednesday, 29 January 2020 15:43 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/29, 15:05 UTC. Our logs show the incident started on 01/29, 12:05 UTC and that during the 3 hours that it took to resolve the issue customers using Log Analytics in East Asia who may have experienced data access issues, missed or delayed Log Search Alerts, and/or connecting to resources hosted in this region. Customers using Service Map may have seen that the service was unavailable and/or experienced difficulties accessing data for resources hosted in this region.
-Mohini
We've confirmed that all systems are back to normal with no customer impact as of 01/29, 15:05 UTC. Our logs show the incident started on 01/29, 12:05 UTC and that during the 3 hours that it took to resolve the issue customers using Log Analytics in East Asia who may have experienced data access issues, missed or delayed Log Search Alerts, and/or connecting to resources hosted in this region. Customers using Service Map may have seen that the service was unavailable and/or experienced difficulties accessing data for resources hosted in this region.
- Root Cause: The failure was due to configuration issues with one of our dependent service.
- Incident Timeline: 3 Hours - 01/29, 12:05 UTC through 01/29, 15:05 UTC
We understand that customers rely on Azure Log Analytics and Service Map as critical services and apologize for any impact this incident caused.
-Mohini
Initial Update: Wednesday, 29 January 2020 14:23 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue in East Asia region and may have missed or delayed Log Search Alerts.
- Work Around: None
- Next Update: Before 01/29 18:30 UTC
-Anusha