First published on MSDN on Jun 26, 2018
Final Update: Tuesday, 26 June 2018 07:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/26, 07:10 UTC. Our logs show the incident started on 06/25, 16:00 UTC and that during the 15 hours and 10 minutes that it took to resolve the issue most customers who would have tried to open the End-to-End transactions blade would have experienced slowness in the Azure Portal.
-Varun
We've confirmed that all systems are back to normal with no customer impact as of 06/26, 07:10 UTC. Our logs show the incident started on 06/25, 16:00 UTC and that during the 15 hours and 10 minutes that it took to resolve the issue most customers who would have tried to open the End-to-End transactions blade would have experienced slowness in the Azure Portal.
- Root Cause: The failure was due to an issue with one of our data retrieval service.
-
Incident Timeline: 15 Hours & 10 minutes - 06/25, 16:00 UTC through 06/26, 07:10 UTC.
-Varun
Initial Update: Tuesday, 26 June 2018 06:43 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience slowness while accessing the End-to-End transaction details view in Azure Portal.
-Varun
We are aware of issues within Application Insights and are actively investigating. Some customers may experience slowness while accessing the End-to-End transaction details view in Azure Portal.
- Work Around: None
- Next Update: Before 06/26 09:00 UTC
-Varun
Published Feb 19, 2019
Version 1.0