Final Update: Saturday, 17 June 2017 00:42 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 06/17, 00:00 UTC. Our logs show the incident started on 06/16, 22:56 UTC and that during the one hour that it took to resolve the issue, customers experienced data access issues while trying to access Application Insights data through Azure and Application Analytics portals.
We’ve confirmed that all systems are back to normal with no customer impact as of 06/17, 00:00 UTC. Our logs show the incident started on 06/16, 22:56 UTC and that during the one hour that it took to resolve the issue, customers experienced data access issues while trying to access Application Insights data through Azure and Application Analytics portals.
- Root Cause: The failure was due to the decommissioning of a secondary dependency in our gateway service. This activity resulted in an unexpected situation in the service which resulted in the it responding with errors to external requests. Restoring the dependency restored service health and mitigated the issue.
- Incident Timeline: 1 Hours & 4 minutes – 06/16, 22:56 UTC through 06/17, 00:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-Arun
Initial Update: Friday, 16 June 2017 23:22 UTC
We are aware of issues within Application Insights and are actively investigating. Customers may experience Data Access Issue in Azure and Application Analytics portal. The following data types are affected: Availability,Customer Event,Dependency,Exception,Metric,Page Load,Page View,Performance Counter,Request,Trace.
We are aware of issues within Application Insights and are actively investigating. Customers may experience Data Access Issue in Azure and Application Analytics portal. The following data types are affected: Availability,Customer Event,Dependency,Exception,Metric,Page Load,Page View,Performance Counter,Request,Trace.
- Next Update: Before 06/17 01:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Arun