Final Update: Thursday, 25 February 2021 07:25 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/25, 06:50 UTC. Our logs show the incident started on 02/25, 00:30 UTC and that during the 6 Hours 20 Minutes that it took to resolve the issue some customers may have experienced delayed or missed Log Search Alerts and Queries for customer data would not return expected results in West US 2 region.
We've confirmed that all systems are back to normal with no customer impact as of 02/25, 06:50 UTC. Our logs show the incident started on 02/25, 00:30 UTC and that during the 6 Hours 20 Minutes that it took to resolve the issue some customers may have experienced delayed or missed Log Search Alerts and Queries for customer data would not return expected results in West US 2 region.
- Root Cause: Our investigation determined that a backend services became unhealthy, preventing requests from completing.
- Incident Timeline: 6 Hours & 20 minutes - 02/25, 00:30 UTC through 02/25, 06:50 UTC.
-Vamshi
Initial Update: Thursday, 25 February 2021 04:55 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Queries for customer data would not return expected results in West US 2 region.
-Harshita
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts and Queries for customer data would not return expected results in West US 2 region.
- Work Around: None
- Next Update: Before 02/25 11:00 UTC
-Harshita
Updated Feb 25, 2021
Version 2.0