Final Update: Monday, 31 January 2022 15:46 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/31, 15:20 UTC. Our logs show the incident started on 01/31, 15:20 UTC and that during the 5 hours& 20 mins that it took to resolve the issue. Some customers may have experienced ingestion data latency ,possible delayed and missed alerts in West Europe region.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 01/31, 15:20 UTC. Our logs show the incident started on 01/31, 15:20 UTC and that during the 5 hours& 20 mins that it took to resolve the issue. Some customers may have experienced ingestion data latency ,possible delayed and missed alerts in West Europe region.
- Root Cause: The failure was due to one of our dependent service.
- Incident Timeline: 5 Hours & 20 minutes - 01/31, 10:00 UTC through 01/31, 15:20 UTC
-Srikanth
Update: Monday, 31 January 2022 15:03 UTC
We are aware of issues within Application insights and are actively investigating. Some customers may experience ingestion data latency ,possible delayed and missed alerts in West Europe region.
We are aware of issues within Application insights and are actively investigating. Some customers may experience ingestion data latency ,possible delayed and missed alerts in West Europe region.
- Work Around: None.
- Next Update: Before 01/31 19:30 UTC.
Updated Jan 31, 2022
Version 2.0