We've confirmed that all systems are back to normal with no customer impact as of 05/12, 17:45 UTC. Our logs show the incident started on 05/12, 17:18 UTC and that during the ~27 min that it took to resolve the issue customers in EastUS2 using Azure Log Analytics may have encountered data access issues and/or delayed or missing Log Search Alerts for resources hosted in this region.
Root Cause: The failure was due to one of the backend services becoming unhealthy
Incident Timeline: 27 minutes - 05/12, 17:18 UTC through 05/12, 17:45 UTC.
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.