This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Friday, 07 January 2022 19:28 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/07, 18:47 UTC. Our logs show the incident started on 1/07, 17:38 UTC and that during the 51 minutes that it took to resolve the issue customers using Azure Monitor may have experienced delayed or missed Alerts
We've confirmed that all systems are back to normal with no customer impact as of 1/07, 18:47 UTC. Our logs show the incident started on 1/07, 17:38 UTC and that during the 51 minutes that it took to resolve the issue customers using Azure Monitor may have experienced delayed or missed Alerts
- Root Cause: The failure was due to unhealthy clusters
- Incident Timeline: 51 minutes - 1/07, 17:38 UTC through 1/07, 18:47 UTC
-Eric Singleton