Final Update: Thursday, 30 June 2022 15:23 UTC
We've confirmed that all systems are back to normal with no customer impact as of 06/30, 12:20 UTC. Our logs show the incident started on 06/30, 11:25 UTC and that during the 55 minutes that it took to resolve the issue some of the customers using Log analytics and Azure Sentinel in East US region may have experienced data access issue and delayed or missed alerts.
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 06/30, 12:20 UTC. Our logs show the incident started on 06/30, 11:25 UTC and that during the 55 minutes that it took to resolve the issue some of the customers using Log analytics and Azure Sentinel in East US region may have experienced data access issue and delayed or missed alerts.
- Root Cause: The failure was due to one of the backend dependent service becoming unhealthy.
- Incident Timeline: 55 minutes - 06/30, 11:25 UTC through 06/30, 12:20 UTC
-Soumyajeet
Initial Update: Thursday, 30 June 2022 12:58 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in East US region.
-Soumyajeet
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in East US region.
- Next Update: Before 06/30 16:00 UTC
-Soumyajeet
Updated Jun 30, 2022
Version 2.0
Azure-Monitor-Team
Microsoft
Microsoft
