We've confirmed that all systems are back to normal with no customer impact as of 3/24, 02:32 UTC. Our logs show the incident started on 3/23, 23:25 UTC and that during the 3 hours and 7 minutes that it took to resolve the issue customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region.
Root Cause: The failure was due to an underlying dependency
Incident Timeline: 3 Hours & 7 minutes - 3/23, 23:25 UTC through 3/24, 2:32 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.
Update: Thursday, 24 March 2022 01:33 UTC
Root cause has been isolated to an underlying dependency which is in the process of recovering. Customers may experience up to 2 hours of ingestion latency and missed or delayed Log Search Alerts in the West Europe region