Final Update: Thursday, 04 February 2021 07:34 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/04, 07:35 UTC. Our logs show the incident started on 02/04, 06:12 UTC and that during the 1 Hour & 23 minutes that it took to resolve the issue some customers may have experienced data latency and incorrect alert activation in South Africa North region.
-Mohini
We've confirmed that all systems are back to normal with no customer impact as of 02/04, 07:35 UTC. Our logs show the incident started on 02/04, 06:12 UTC and that during the 1 Hour & 23 minutes that it took to resolve the issue some customers may have experienced data latency and incorrect alert activation in South Africa North region.
- Root Cause: The failure was due to incorrect configuration in one of the component of the service.
- Incident Timeline: 1 Hour & 23 minutes - 02/04, 06:12 UTC through 02/04, 07:35 UTC
-Mohini
Published Feb 04, 2021
Version 1.0Azure-Monitor-Team
Silver Contributor
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity