First published on MSDN on Dec 12, 2018
Final Update: Wednesday, 12 December 2018 21:05 UTC
We've confirmed that all systems are back to normal with no customer impact as of 12/12, 13:50 UTC. Our logs show the incident started on 12/12, 08:00 UTC and that during the 5 hours 50 minutes that it took to resolve the issue, all the customers in East US region may have experienced data latency in Azure Log Analytics.
-
Root Cause: The data was latent as one of the backend services responsible for data ingestion had failures, resulting in delayed data availability.
-
Incident Timeline: 5 hours 50 minutes - 12/12, 08:00 UTC through 12/12, 13:50 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
-Sapna
