This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Final Update: Thursday, 16 June 2022 05:12 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/16, 04:30 UTC. Our logs shows the incident started on 06/16, 00:10 UTC and that during the 4 hours & 20 minutes that it took to resolve the issue . Some customers may have experienced issues with missed alerts or missed alerts notifications in West US2 region during the impacted duration.
-Srikanth
We've confirmed that all systems are back to normal with no customer impact as of 06/16, 04:30 UTC. Our logs shows the incident started on 06/16, 00:10 UTC and that during the 4 hours & 20 minutes that it took to resolve the issue . Some customers may have experienced issues with missed alerts or missed alerts notifications in West US2 region during the impacted duration.
- Root Cause: The failure was due to backend dependencies become unhealthy.
- Incident Timeline: 4 Hours & 20 minutes - 06/16, 00:10 UTC through 06/16, 04:30 UTC.
-Srikanth
Initial Update: Thursday, 16 June 2022 03:24 UTC
Starting at 00:10 UTC on 16 Jun 2022, you have been identified as a customer using Azure Monitor in West US 2 who may experience issues with missed alerts or missed alerts notifications.
- Next Update: Before 06/16 05:30 UTC or as events warrant
- Work Around: None
We are aware of this issue and are actively investigating. The next update will be provided in 2 hours, or as events warrant.
-Shwetha Huilgol