We've confirmed that all systems are back to normal with no customer impact as of 02/19, 08:14 UTC. Our logs show the incident started on 02/19, 07:35 UTC and that during the 39 minutes that it took to resolve the issue 4% of customers in SEAU may have experienced data access and data latency issues.
- Root Cause: The failure was due to issue with one of our backend service.
- Incident Timeline: 39 minutes - 02/19, 07:35 UTC through 02/19, 08:14 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
We are aware of issues within Log Analytics and are actively investigating. Some customers in SEAU may experience Data Access issues.
- Work Around: None
- Next Update: Before 02/19 11:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here