This article is contributed. See the original author and article here.
Final Update: Sunday, 30 January 2022 15:00 UTC
We’ve confirmed that all systems are back to normal with no customer impact as of 01/30, 14:25 UTC. Our logs show the incident started on 01/30, 13:25 UTC and that during the 1 hour that it took to resolve the issue some of customers using Azure Log Analytics or Azure Sentinel might have experienced delayed or missed Log Search Alerts and issues accessing data in West US2 region.
We’ve confirmed that all systems are back to normal with no customer impact as of 01/30, 14:25 UTC. Our logs show the incident started on 01/30, 13:25 UTC and that during the 1 hour that it took to resolve the issue some of customers using Azure Log Analytics or Azure Sentinel might have experienced delayed or missed Log Search Alerts and issues accessing data in West US2 region.
- Root Cause: The failure was due one of our backend service was unhealthy.
- Incident Timeline: 1 Hour – 01/30, 13:25 UTC through 01/30, 14:25 UTC
-Sai Kumar
Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.
Recent Comments