First published on MSDN on Nov 15, 2018
Final Update: Thursday, 15 November 2018 08:20 UTC

We've confirmed that all systems are back to normal with no customer impact as of 11/15, 07:00 UTC. Our logs show the incident started on 11/12,19:00 UTC and that during the 60 hours that it took to resolve the issue customers of affected 2481 subscriptions experienced Data Access issues globally while attempting to run queries.
  • Root Cause: The failure was due to one of our dependent services.
  • Incident Timeline: 60 Hours & 0 minutes - 11/12,19:00 UTC through 11/15, 07:00 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Madhuri
Update: Thursday, 15 November 2018 04:30 UTC

We continue to investigate issues within Application Insights and Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience data access issue while attempting to run queries . We are working to establish the start time for the issue, initial findings indicate that the problem began at 11/12 ~19:00 UTC. We currently have no estimate for resolution.
  • Next Update: Before 11/15 10:30 UTC

We are trying best to resolve the issue. Apologies for any inconveniences caused.

-Madhuri
Update: Wednesday, 14 November 2018 23:38 UTC

We continue to investigate issues within Application Insights and Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience Data Access  issues while attempting to run queries. We are working to establish the start time for the issue, initial findings indicate that the problem began at <11/12 ~19:00 UTC>. We currently have no estimate for resolution.
  • Next Update: Before 11/15 04:00 UTC
-Leela
Initial Update: Wednesday, 14 November 2018 19:59 UTC

We are aware of issues within Application Insights and Log Analytics and are actively investigating. Some customers may experience Data Access  issues while attempting to run queries.
  • Next Update: Before 11/15 00:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Leela