We've confirmed that all systems are back to normal with no customer impact as of 8/13, 17:50 UTC. Our logs show the incident started on 8/13, 09:50 UTC and that during the 8 hours that it took to resolve the issue , customers in South UK location would have experienced data latency.
Root Cause: The failure was due to issues with configuration of one of our back-end service.
Incident Timeline: 8 Hours - 8/13, 09:50 UTC through 8/13, 17:50 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
Update: Monday, 13 August 2018 17:44 UTC
Root cause has been isolated to issue with configuration of one of our back-end service. Some customers continue to experience data latency in South UK region and we estimate 2 hours before all backlog data is addressed.
Work Around: none
Next Update: Before 08/13 20:00 UTC
Update: Monday, 13 August 2018 14:58 UTC
We continue to investigate issues within Log Analytics. Root cause is not fully understood at this time. Some customers continue to experience data latency in South UK region. We are working to establish the start time for the issue, initial findings indicate that the problem began at 08/13 ~11:30 UTC>. We currently have no estimate for resolution.
Next Update: Before 08/13 17:00 UTC
Initial Update: Monday, 13 August 2018 13:03 UTC
We are aware of issues within Log Analytics and are actively investigating. Some customers may experience data latency in South UK region..
Work Around: None
Next Update: Before 08/13 15:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.