This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
Final Update: Thursday, 27 February 2020 11:35 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/27, 10:00 UTC. Our logs show the incident started on 02/27, 08:57 UTC and that during the 1 hour 03 minutes that it took to resolve the issue some customers in Central US region might have experienced data access issue and failures when queried through API.
-Syed
We've confirmed that all systems are back to normal with no customer impact as of 02/27, 10:00 UTC. Our logs show the incident started on 02/27, 08:57 UTC and that during the 1 hour 03 minutes that it took to resolve the issue some customers in Central US region might have experienced data access issue and failures when queried through API.
- Root Cause: The failure was due to an issue with one of our dependent service.
- Incident Timeline: 01 Hours & 03 minutes - 02/27, 08:57 UTC through 02/27, 10:00 UTC
-Syed
Initial Update: Thursday, 27 February 2020 10:08 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers in Central US may experience data access issue and failures when query through API.
-Syed
We are aware of issues within Log Analytics and are actively investigating. Some customers in Central US may experience data access issue and failures when query through API.
- Work Around: none
- Next Update: Before 02/27 12:08 UTC
-Syed