Home
Final Update: Thursday, 21 March 2019 00:01 UTC

We've confirmed that all systems are back to normal with no customer impact as of 3/20, 23:10 UTC. Our logs show the incident started on 3/20, 22:25 UTC and that during the 45 minutes that it took to resolve the issue up to 24% of customers experienced 502 or 504 failures when attempting to query Log Analytics data in East US, West Central US, .
  • Root Cause: The failure was due to a misconfigured traffic manager.
  • Incident Timeline:  45 minutes - 3/20, 22:25 UTC through 3/20, 23:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jeff Miller