First published on MSDN on Jan 11, 2019
Final Update: Friday, 11 January 2019 05:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 1/11/2019, 5:30 UTC. Our logs show the incident started on 1/11, 1:05 UTC and that during the time it took to resolve the issue all customers with workspaces in West Central US region experienced failures of agents to upload data as well as delayed ingest time and portal connectivity issues.
  • Root Cause: The failure was due to a misconfiguration of the region settings.
  • Incident Timeline: 4 Hours & 25 minutes - 1/11 1:05 UTC through 1/11, 5:30 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: Friday, 11 January 2019 05:06 UTC

Root cause has been isolated to a South UK Azure incident (99490009) which was impacting Log Analytics in the region. To address this issue we reconfigured the West Central region.  We expect functions to now be improving.

  • Work Around: None
  • Next Update: Before 01/11 11:30 UTC
-Jeff Miller
Initial Update: Friday, 11 January 2019 03:16 UTC

We are aware of issues within Log Analytics in West Central us region and are actively investigating. Some customers may experience failures to connect and ingestion delay.
  • Work Around: None
  • Next Update: Before 01/11 05:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jeff Miller