This article is contributed. See the original author and article here.

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.

  • 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

We understand that customers rely on Azure Monitor Service as a critical service and apologize for any impact this incident caused.


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.
  • Work Around: None
  • Next Update: Before 02/26 09:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

Brought to you by Dr. Ware, Microsoft Office 365 Silver Partner, Charleston SC.

%d bloggers like this: