Final Update: Monday, 23 May 2022 16:19 UTC
We've confirmed that all systems are back to normal with no customer impact as of 5/23, 15:50 UTC. Our logs show the incident started on 5/23, 09:22 UTC and that during the 6.5 hours that it took to resolve the issue some customers in the North Europe region may have experienced delayed or missed alerts.
-Jack Cantwell
We've confirmed that all systems are back to normal with no customer impact as of 5/23, 15:50 UTC. Our logs show the incident started on 5/23, 09:22 UTC and that during the 6.5 hours that it took to resolve the issue some customers in the North Europe region may have experienced delayed or missed alerts.
- Root Cause: The failure was due to a subset of backend service nodes becoming unavailable.
- Incident Timeline: 6 Hours & 28 minutes - 5/23, 09:22 UTC through 5/23, 15:50 UTC
-Jack Cantwell
Initial Update: Monday, 23 May 2022 13:41 UTC
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Data Ingestion Latency and delayed or missed Alerts in North Europe region.
-Deepika
We are aware of issues within Application Insights and are actively investigating. Some customers may experience Data Ingestion Latency and delayed or missed Alerts in North Europe region.
- Work Around: None
- Next Update: Before 05/23 18:00 UTC
-Deepika
Updated May 23, 2022
Version 2.0