Final Update: Wednesday, 31 March 2021 14:17 UTC
We've confirmed that all systems are back to normal with no customer impact as of 03/31, 14:00 UTC. Our logs show the incident started on 03/31, 12:05 UTC and that during the 1 Hour & 55 minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in East US 2 region.
-Harshita
We've confirmed that all systems are back to normal with no customer impact as of 03/31, 14:00 UTC. Our logs show the incident started on 03/31, 12:05 UTC and that during the 1 Hour & 55 minutes that it took to resolve the issue some customers may have experienced data access issue and delayed or missed alerts in East US 2 region.
- Root Cause: The failure was due to issues with one of our dependent service.
- Incident Timeline: 1 Hour & 55 minutes - 03/31, 12:05 UTC through 03/31, 14:00 UTC
-Harshita
Initial Update: Wednesday, 31 March 2021 13:03 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in East US 2 region.
-Harshita
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data access issue and delayed or missed alerts in East US 2 region.
- Work Around: None
- Next Update: Before 03/31 16:30 UTC
-Harshita
Updated Mar 31, 2021
Version 1.0