Final Update: Friday, 26 February 2021 08:34 UTC
We've confirmed that all systems are back to normal with no customer impact as of 02/26, 08:11 UTC. Our logs show the incident started on 02/26, 03:25 UTC and that during the 4 hours 45 Minutes that it took to resolve the issue some customers may have experienced data access, data latency and incorrect alert activations in Japan East region.
-Vamshi
We've confirmed that all systems are back to normal with no customer impact as of 02/26, 08:11 UTC. Our logs show the incident started on 02/26, 03:25 UTC and that during the 4 hours 45 Minutes that it took to resolve the issue some customers may have experienced data access, data latency and incorrect alert activations in Japan East region.
- Root Cause: The failure was due to issue in one of our dependent service.
- Incident Timeline: 4 Hours & 45 minutes - 02/26, 03:25 UTC through 02/26, 08:11 UTC
-Vamshi
Initial Update: Friday, 26 February 2021 04:57 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in Japan East region.
-Vamshi
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience delayed or missed Log Search Alerts in Japan East region.
- Work Around: None
- Next Update: Before 02/26 09:00 UTC
-Vamshi
Updated Feb 26, 2021
Version 4.0