Final Update: Wednesday, 15 August 2018 04:32 UTC
We've confirmed that all systems are back to normal with no customer impact as of 08/15, 04:10 UTC. Our logs show the incident started on 08/15, 02:00 UTC and that during the 2 hours and 10 minutes that it took to resolve the issue 100% of US government customers would have experienced data access in azure portal .
We've confirmed that all systems are back to normal with no customer impact as of 08/15, 04:10 UTC. Our logs show the incident started on 08/15, 02:00 UTC and that during the 2 hours and 10 minutes that it took to resolve the issue 100% of US government customers would have experienced data access in azure portal .
- Root Cause: The failure was due to one of our back end service which went in to bad state. Rebooting the impacted service helped in mitigating the issue
- Incident Timeline: 2 Hours & 10 minutes - 08/15, 02:00 UTC through 08/15, 04:M10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Rama
Initial Update: Wednesday, 15 August 2018 03:25 UTC
We are aware of issues within Log Analytics and are actively investigating. All the customers who uses Log Analytics may experience data access issues in USGov Cloud environment.
We are aware of issues within Log Analytics and are actively investigating. All the customers who uses Log Analytics may experience data access issues in USGov Cloud environment.
- Work Around: none
- Next Update: Before 08/15 06:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Praveen