Experiencing Data Access Issue in Azure Portal for Metric – 03/11 – Resolved

Final Update: Friday, 11 March 2016 09:44 UTC

We've confirmed that all systems are back to normal with no customer impact as of 03/11, 09:44 UTC. Our logs show the incident started on 03/11, 03:54 UTC and that during the 5 hours & 50 minutes that it took to resolve the issue customers experienced data access issues and data gaps.
  • Root Cause: The failure was due to dependent service of Application Insights platform which once recovered mitigated the issue.
  • Lessons Learned: We have collected required telemetry data and will be investigating more using the same  to avoid such occurrences in future. 
  • Incident Timeline: 5 Hours & 50 minutes - 03/11, 03:54 UTC through 03/11, 09:44 UTC

We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.


Update: Friday, 11 March 2016 07:43 UTC
Root cause has been isolated to failures with one of the dependent service of Application Insights Storage platform. Once the dependent service has recovered, Application Insights Storage service has recovered. Customers whose data resides in South Central US region would have experienced a data access issue during the impacted period.
  • Work Around: None
  • Next Update: Before 03/11 12:00 UTC


Initial Update: Friday, 11 March 2016 03:54 UTC

We are aware of issues within Application Insights and are actively investigating. Some customers may experience Data Access Issue in Azure Portal. The following data types are affected: Metric.

The issue is a result of many of our clusters running over capacity. We are aware of this capacity issue and in order to deal with it we are in process reducing data retention for our customers. This data retention change will not go in affect until 03/16/2016.
In the mean time we are running a high risk of reoccurrence of such issues impacting our customers' ability to access metrics data reliably.
Our logs suggest < 1% of users are impacted by this issue.

  • Work Around: None
  • Next Update: Before 03/11 08:00 UTC

We are working hard to resolve this issue and apologize for any inconvenience.
-Pankaj Suri

Comments (0)

Skip to main content