Final Update: Wednesday, 14 March 2018 14:22 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/14, 01:45 UTC. Our logs show the incident started on 03/14, 12:15 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue some customers experienced issues accesing azure log analytics workspaces.
We've confirmed that all systems are back to normal with no customer impact as of 03/14, 01:45 UTC. Our logs show the incident started on 03/14, 12:15 UTC and that during the 1 hour and 30 minutes that it took to resolve the issue some customers experienced issues accesing azure log analytics workspaces.
- Root Cause: The failure was due to an internal service in the Azure log analytics service.
- Incident Timeline: 1 Hours & 30 minutes - 03/14, 12:15 UTC through M/D, 01:45 UTC
We understand that customers rely on Azure log analytics service as a critical service and apologize for any impact this incident caused.
-suneel
Initial Update: Wednesday, 14 March 2018 12:51 UTC
We are aware of issues within ODS service and are actively investigating. Some customers may experience issues while accessing azure log analytics and issues related to alerting in Log analytics service.
We are aware of issues within ODS service and are actively investigating. Some customers may experience issues while accessing azure log analytics and issues related to alerting in Log analytics service.
- Work Around:
- Next Update: Before 03/14 02:45 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-suneel