First published on MSDN on Jun 23, 2018
Final Update: Saturday, 23 June 2018 10:45 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/23, 09:50 UTC. Our logs show the incident started on 06/23, 09:35 UTC and that during the 15 min that it took to resolve the issue 9% of customers experienced data access issues while accessing through azure portal.
-Monish
We've confirmed that all systems are back to normal with no customer impact as of 06/23, 09:50 UTC. Our logs show the incident started on 06/23, 09:35 UTC and that during the 15 min that it took to resolve the issue 9% of customers experienced data access issues while accessing through azure portal.
- Root Cause: The failure was due to an issue in one of our dependent platform services.
- Incident Timeline: 15 minutes - 06/23, 09:35 UTC through 06/23, 09:50 UTC
-Monish
Update: Saturday, 23 June 2018 10:11 UTC
We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience Data Access Issue in Azure Portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/23~09:35 UTC.
We continue to investigate issues within Application Insights. Root cause is not fully understood at this time. Some customers continue to experience Data Access Issue in Azure Portal. We are working to establish the start time for the issue, initial findings indicate that the problem began at 06/23~09:35 UTC.
- Work Around: None
- Next Update: Before 06/23 12:30 UTC
Published Feb 19, 2019
Version 1.0