Final Update: Thursday, 25 February 2021 11:53 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/25, 11:35 UTC. Our logs show the incident started on 02/25, 09:25 UTC and that during the 2 hours and 10 minutes that it took to resolve the issue some customers may have experienced issues with missed or delayed Log Search alerts or experienced difficulties accessing data for resources hosted in East US region.
-Harshita
We've confirmed that all systems are back to normal with no customer impact as of 02/25, 11:35 UTC. Our logs show the incident started on 02/25, 09:25 UTC and that during the 2 hours and 10 minutes that it took to resolve the issue some customers may have experienced issues with missed or delayed Log Search alerts or experienced difficulties accessing data for resources hosted in East US region.
- Root Cause: The failure was due to a backend service becoming unhealthy.
- Incident Timeline: 2 Hours & 10 minutes - 02/25, 09:25 UTC through 02/25, 11:35 UTC
-Harshita
Initial Update: Thursday, 25 February 2021 10:32 UTC
We are aware of issues within Log Search Alerts and are actively investigating. Some Customers may experience issues with missed or delayed Log Search alerts or experienced difficulties accessing data for resources hosted in East US region.
We are aware of issues within Log Search Alerts and are actively investigating. Some Customers may experience issues with missed or delayed Log Search alerts or experienced difficulties accessing data for resources hosted in East US region.
- Work Around: None
- Next Update: Before 02/25 14:00 UTC
-Harshita
Updated Feb 25, 2021
Version 3.0