Final Update: Monday, 24 May 2021 14:51 UTC
We've confirmed that all systems are back to normal with no customer impact as of 05/24, 14:30 UTC. Our logs show the incident started on 05/24, 10:57 UTC and that during the 3 Hours & 33 minutes that it took to resolve the issue, some customers may have experienced intermittent data latency and incorrect alert activation for resources in South UK region.
We've confirmed that all systems are back to normal with no customer impact as of 05/24, 14:30 UTC. Our logs show the incident started on 05/24, 10:57 UTC and that during the 3 Hours & 33 minutes that it took to resolve the issue, some customers may have experienced intermittent data latency and incorrect alert activation for resources in South UK region.
- Root Cause: The failure was due to an issue with dependent service.
- Incident Timeline: 3 Hours & 33 minutes - 05/24, 10:57 UTC through 05/24, 14:30 UTC
-Ramesh
Update: Monday, 24 May 2021 13:35 UTC
Root cause has been isolated to capacity issue which caused data latency. To address this issue we increased the capacity. Some customers may continue to experience intermittent data latency and incorrect alert activation for resources in South UK region.
Root cause has been isolated to capacity issue which caused data latency. To address this issue we increased the capacity. Some customers may continue to experience intermittent data latency and incorrect alert activation for resources in South UK region.
- Work Around: None
- Next Update: Before 05/24 15:00 UTC
Updated May 24, 2021
Version 4.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