Final Update: Saturday, 30 March 2019 03:23 UTC
We've confirmed that all systems are back to normal with no customer impact as of 3/30, 3:20 AM UTC. Our logs show the incident started on 3/30, 2:56 UTC and that during the ~20 min that it took to resolve the issue some of the customers in south-east Asia might have experienced data access issue in Azure portal.
-Anupama
We've confirmed that all systems are back to normal with no customer impact as of 3/30, 3:20 AM UTC. Our logs show the incident started on 3/30, 2:56 UTC and that during the ~20 min that it took to resolve the issue some of the customers in south-east Asia might have experienced data access issue in Azure portal.
- Root Cause: The failure was due to the issues in one of our dependency service.
- Incident Timeline: 20 minutes - 3/30, 2:56 UTC through 3/30, 3:20 UTC
-Anupama
Initial Update: Saturday, 30 March 2019 02:56 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues while accessing their data on Azure portal. Query performance and API's will also be affected.
-Anupama
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience issues while accessing their data on Azure portal. Query performance and API's will also be affected.
- Work Around: none
- Next Update: Before 03/30 06:00 UTC
-Anupama
Updated Mar 30, 2019
Version 2.0
