Final Update: Thursday, 21 November 2019 22:53 UTC
We've confirmed that all systems are back to normal with no customer impact as of 11/21, 22:20 UTC. Our logs show the incident started on 11/21, 20:05 UTC and that during the 2 hours and 25 minutes that it took to resolve the issue 100% of customers would have experienced issues accessing data for Log Analytics in South UK and East Japan. In addition, customers may have had issues accessing Service Map.
Root Cause: Engineers determined that a configuration error caused requests to a backend service to become unhealthy.
Incident Timeline: 2 Hours & 15 minutes - 11/21, 20:05 UTC through 11/21, 22:20 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused
Update: Thursday, 21 November 2019 21:58 UTC
Root cause has been isolated to a configuration error caused requests to a backend service to become unhealthy which is impacting the customers ability to access data for Log Analytics for South UK and East Japan. Service map is also impacted which will keep customers from seeing accurate network maps. To address this issue we are redeploying with new certificates. The deployment should finish within 1 hour. The incident started at 20:05 UTC for East Japan and 20:32 UTC for South UK.