Final Update: Thursday, 02 June 2022 00:42 UTC
We've confirmed that all systems are back to normal with no customer impact as of 6/02, 00:20 UTC. Our logs show the incident started on 6/01, 09:30 UTC and that during the 14 hours and 50 minutes that it took to resolve the issue customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 6/02, 00:20 UTC. Our logs show the incident started on 6/01, 09:30 UTC and that during the 14 hours and 50 minutes that it took to resolve the issue customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
- Root Cause: The failure was due to an unhealthy backend dependency.
- Incident Timeline: 14 Hours & 50 minutes - 6/01, 09:30 UTC through 6/02, 00:20 UTC
-Eric Singleton
Update: Wednesday, 01 June 2022 23:19 UTC
Still in the process of recovering the backend dependency. Some customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
Still in the process of recovering the backend dependency. Some customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
- Work Around:
- Next Update: Before 06/02 01:30 UTC
Update: Wednesday, 01 June 2022 20:49 UTC
Root cause has been isolated to a backend dependency which was impacting. Some customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
Root cause has been isolated to a backend dependency which was impacting. Some customers using Application Insights in North Europe may experience intermittent log data latency and/or gaps. Additionally, users may have experienced incorrect alert activation during the impacted period
- Work Around:
- Next Update: Before 06/01 23:00 UTC
Updated Jun 01, 2022
Version 6.0Azure-Monitor-Team
Former Employee
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity