Final Update: Wednesday, 14 February 2018 19:52 UTC
We've confirmed that all systems are back to normal with no customer impact as of 2/14, 19:41 UTC. Our logs show the incident started on 2/14, 14:45 UTC and that during that time about 7% of customers received intermittent errors viewing metric and availability data
while using the overview blade in the Azure Management Portal.
We've confirmed that all systems are back to normal with no customer impact as of 2/14, 19:41 UTC. Our logs show the incident started on 2/14, 14:45 UTC and that during that time about 7% of customers received intermittent errors viewing metric and availability data
while using the overview blade in the Azure Management Portal.
- Root Cause: The failure was due to a bad instance state
- Incident Timeline: 4 Hours & 56 minutes - 2/14, 14:45 UTC through 2/14, 19:41 UTC
We understand that customers rely on Application Insights as a critical service and apologize for any impact this incident caused.
-J Miller
Initial Update: Wednesday, 14 February 2018 18:28 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Alerting failure. The following data types are affected: Availability.
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Alerting failure. The following data types are affected: Availability.
- Next Update: Before 02/14 20:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-J Miller
This post first appeared on MSDN Blogs | Get The Latest Information, Insights, Announcements, And News From Microsoft Experts And Developers In The MSDN Blogs., please read the originial post: here
