Experiencing Data Latency Issue in Azure portal for Log Analytics - 02/23 - Resolved
Published Feb 22 2021 04:22 PM 1,040 Views
Final Update: Tuesday, 23 February 2021 03:38 UTC

We've confirmed that all systems are back to normal with no customer impact as of 2/23, 3:00 UTC. Our logs show the incident started on 2/22, 15:10 UTC and that during the  ~12 hours that it took to resolve the issue, customers in East US2 experienced delayed or missed alerts.
  • Root Cause: The failure was due to backend service becoming unhealthy due to high threshold.
  • Incident Timeline: 12 Hours  - 2/22, 15:10 UTC through 2/23, 3:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.


Update: Tuesday, 23 February 2021 02:45 UTC

Root cause has been isolated to one of the backend services becoming unhealthy due to overload which was impacting the alerts getting missed or delayed. To address this issue we are scaling out the backend service. Some customers may experience missed or delayed alerts and we estimate  ~1 hour before all latent data is addressed.
  • Work Around: None
  • Next Update: Before 02/23 04:00 UTC

Initial Update: Tuesday, 23 February 2021 00:21 UTC

We are aware of issues within Log Analytics and are actively investigating.  Some customers in East US2 may experience delayed or missed alerts.
  • Work Around: None
  • Next Update: Before 02/23 02:30 UTC
We are working hard to resolve this issue and apologize for any inconvenience.

Version history
Last update:
‎Feb 22 2021 07:58 PM
Updated by: