First published on MSDN on Sep 30, 2018
Final Update: Sunday, 30 September 2018 20:00 UTC

We've confirmed that all systems are back to normal with no customer impact as of 09/30, 19:41 UTC. Our logs show the incident started on 09/30, 07:47 UTC and that during the ~12 hours that it took to resolve the issue, some customers may have experienced issues while accessing telemetry in Application Insights and with the creation of classic alerts.
  • Root Cause: The failure was due to the issues in one of the dependent services of Application Insights responsible for the feature
  • Incident Timeline:11 hours 54 minutes - 09/30, 07:47 UTC through 09/30, 19:41 UTC.
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Sapna
Update: Sunday, 30 September 2018 18:02 UTC

We continue to investigate issues within Application Insights. Root cause is not fully understood yet. Some customers continue to experience issues with accessing telemetry in Application Insights and with the creation of classic alerts.

  • Work Around: None
  • Next Update: Before 10/01 00:30 UTC
-Sapna
Update: Sunday, 30 September 2018 14:01 UTC

We continue to investigate issues within Application Insights. Some customers may experience issues with accessing telemetry in Application Insights and with the creation of classic alerts. Initial findings indicate that the problem began at 09/30 ~08:00 UTC.
  • Work Around: None
  • Next Update: Before 09/30 18:30 UTC
-Mohini
Initial Update: Sunday, 30 September 2018 09:41 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience issues with accessing their telemetry in Application Insights and with the creation of classic alerts.
  • Next Update: Before 09/30 12:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Rama