First published on MSDN on May 24, 2018
Final Update: Thursday, 24 May 2018 21:37 UTC

We've confirmed that all systems are back to normal with no customer impact as of 5/24, 21:25 UTC. Our logs show the incident started on 5/24, 19:45 UTC and that during the 40 minutes that it took to resolve the issue 10% of customers experienced delays in getting query results accounting for 1% of the overall query load in the impacted regions.
  • Root Cause: The failure was due to backend configuration issues.
  • Incident Timeline: 40 minutes - 5/24, 19:45 UTC through 5/24, 21:25 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff Miller
Update: Thursday, 24 May 2018 21:06 UTC
Issue is impacting South East Asia and South East Australia regions as of 5/24 2018 at 19:45 UTC.

Root cause has been isolated to a backend availability issue which was impacting queries. The backend service is in process of being restored. Some customers may experience delayed queries in these regions and we estimate 1 hour before the issue is fully addressed.
  • Work Around: None
  • Next Update: Before 05/24 23:30 UTC
-Jeff Miller