First published on MSDN on Nov 28, 2018
Final Update: Wednesday, 28 November 2018 01:32 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/28, 01:21 UTC. Our logs show the incident started on 11/27, 22:41 UTC and that during the 2 hours 42 minutes that it took to resolve the issue all the customers experienced data access issues in OMS and Azure Portal in Fairfax region.
Root Cause: The failure was due to issue in one of our backend services.
Incident Timeline: 2 Hours & 42 minutes - 11/27, 22:41 UTC through 11/28, 01:21 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Sindhu
Initial Update: Wednesday, 28 November 2018 00:13 UTC
We are aware of issues within Log Analytics and are actively investigating. All customers may experience data access issues in OMS and Azure Portal in Fairfax region.
Work Around: None
Next Update: Before 11/28 02:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Sindhu
