Final Update: Sunday, 16 January 2022 14:18 UTC
We've confirmed that all systems are back to normal with no customer impact as of 01/16, 13:40 UTC. Our logs show the incident started on 01/16, 10:50 UTC and that during the 2 hours and 50 minutes that it took to resolve the issue some of the customers may have experienced intermittent failures when querying data and missed or delayed alerts for resources hosted in West Central US region .
-Soumyajeet
We've confirmed that all systems are back to normal with no customer impact as of 01/16, 13:40 UTC. Our logs show the incident started on 01/16, 10:50 UTC and that during the 2 hours and 50 minutes that it took to resolve the issue some of the customers may have experienced intermittent failures when querying data and missed or delayed alerts for resources hosted in West Central US region .
- Root Cause: The failure was due to a backend dependency failure.
- Incident Timeline: 2 Hours & 50 minutes - 01/16, 10:50 UTC through 01/16, 13:40 UTC
-Soumyajeet
Initial Update: Sunday, 16 January 2022 13:17 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access and delayed or missed Log Search Alerts in West Central US region.
-Soumyajeet
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access and delayed or missed Log Search Alerts in West Central US region.
- Work Around: None
- Next Update: Before 01/16 15:30 UTC
-Soumyajeet
Updated Jan 16, 2022
Version 2.0