First published on MSDN on Jan 18, 2019
Final Update: Friday, 18 January 2019 15:16 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/18, 14:30 UTC. Our logs show the incident started on 01/18, 12:30 UTC and that during the 2 hours that it took to resolve the issue most of the customers experienced delay in notification delivery and the status was incorrectly displayed.
  • Root Cause: The failure was due to issues in one of our dependent service .
  • Incident Timeline:  2Hours - M/D,  01/18, 12:30 UTC through 01/18, 14:30 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.

-Monish
Update: Friday, 18 January 2019 13:48 UTC

The issue is under investigation within Application Insights. Some customers will still continue to experience delay in notification delivery and status in the portal may display incorrectly.
  • Work Around: None
  • Next Update: Before 01/18 17:00 UTC
-Monish
Update: Friday, 18 January 2019 10:53 UTC

We continue to investigate issues within Application Insights. Some customers continue to experience delay in notification delivery and data access issues in the portal. Initial findings indicate that the problem began at 01/18~12:35 UTC.
  • Work Around: None
  • Next Update: Before 01/18 14:00 UTC
-Monish