Final Update: Friday, 07 January 2022 00:51 UTC
We've confirmed that all systems are back to normal with no customer impact as of 1/6, 23:40 UTC. Our logs show the incident started on 1/6, 21:10 UTC and that during the 2 hours and 30 minutes that it took to resolve the issue, some customers may have experienced delayed or missed Log Search Alerts and data access issues. Some customers using Azure Sentinel may have also experienced data access issues and delayed or misfired alerts.
-Eric Singleton
We've confirmed that all systems are back to normal with no customer impact as of 1/6, 23:40 UTC. Our logs show the incident started on 1/6, 21:10 UTC and that during the 2 hours and 30 minutes that it took to resolve the issue, some customers may have experienced delayed or missed Log Search Alerts and data access issues. Some customers using Azure Sentinel may have also experienced data access issues and delayed or misfired alerts.
- Root Cause: The failure was due to a backend dependency
- Incident Timeline: 2 Hours & 30 minutes - 1/6, 21:10 UTC through 1/6, 23:40UTC
-Eric Singleton
Initial Update: Thursday, 06 January 2022 23:00 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.
-Eric Singleton
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:
- Next Update: Before 01/07 01:00 UTC
-Eric Singleton
Updated Jan 06, 2022
Version 2.0