First published on MSDN on Dec 09, 2018
Final Update: Sunday, 09 December 2018 03:35 UTC

We've confirmed that all our systems are back to normal with no customer impact as of 12/08, 23:55 UTC. Our logs show the incident started on 12/08, 23:20 UTC and that during the 35 minutes that it took to resolve the issue around 8% of customers in Australia SouthEast and East US may have experienced data access errors in OMS portal for Azure Log Analytics.
  • Root Cause: The failure was due to issues in one of our back-end services
  • Incident Timeline: 35 minutes - 12/08, 23:55 UTC through 12/08, 23:20 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.