Final Update: Wednesday, 28 April 2021 22:02 UTC
We've confirmed that all systems are back to normal with no customer impact as of 04/28, 22:00 UTC. Our logs show the incident started on 04/28, 10:49 UTC and that during the 11 hours & 11 minutes that it took to resolve the issue customers may have experienced data access and delayed or missed alerts in the West US region.
-Vincent
We've confirmed that all systems are back to normal with no customer impact as of 04/28, 22:00 UTC. Our logs show the incident started on 04/28, 10:49 UTC and that during the 11 hours & 11 minutes that it took to resolve the issue customers may have experienced data access and delayed or missed alerts in the West US region.
- Root Cause: Due to a backend storage service that became unhealthy.
- Incident Timeline: 11 Hours & 11 minutes - 04/28, 10:49 UTC through 04/28, 22:00 UTC
-Vincent
Update: Wednesday, 28 April 2021 21:47 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may experience data access and delayed or missed alerts in West US region.
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers may experience data access and delayed or missed alerts in West US region.
- Work Around: None
- Next Update: Before 04/29 10:00 UTC
Initial Update: Wednesday, 28 April 2021 11:33 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 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 US region.
- Work Around: None
- Next Update: Before 04/28 16:00 UTC
-Soumyajeet
Updated Apr 28, 2021
Version 3.0