We've confirmed that all systems are back to normal with no customer impact as of 03/02, 10:40 UTC. Our logs show the incident started on 03/02, 08:30 UTC and that during the 2 Hours & 10 minutes that it took to resolve the issue some customers may have experienced intermittent data latency, data access and incorrect alert activation in Japan East region.
Root Cause: The failure was due to issue with one of our backend service which became unhealthy during the impacted window.
Incident Timeline: 2 Hours & 10 minutes - 03/02, 08:30 UTC through 03/02, 10:40 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.