Final Update: Friday, 07 January 2022 15:05 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/07, 14:25 UTC. Our logs show the incident started on 01/07, 11:57 UTC and that during the 2 hours & 28 minutes that it took to resolve the issue. Some customers may have experienced delayed or missed Log Search Alerts and data access issues in West US2 region. Some customers using Azure Sentinel may also experienced data access issues and delayed or misfired alerts.
We've confirmed that all systems are back to normal with no customer impact as of 01/07, 14:25 UTC. Our logs show the incident started on 01/07, 11:57 UTC and that during the 2 hours & 28 minutes that it took to resolve the issue. Some customers may have experienced delayed or missed Log Search Alerts and data access issues in West US2 region. Some customers using Azure Sentinel may also experienced data access issues and delayed or misfired alerts.
- Root Cause: The failure was due to one of our dependent service.
- Incident Timeline: 2 Hours & 28 minutes - 01/07 11:57 UTC through 01/07, 14:25 UTC
Update: Friday, 07 January 2022 12:52 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and data access issues. Some customers using Azure Sentinel may also experience data access issues and delayed or misfired alerts.
Work Around: None.
Next Update: Before 01/07 17:00 UTC
-Srikanth
Updated Jan 07, 2022
Version 6.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