Final Update:
We've confirmed that all systems are back to normal with no customer impact as of 6/9, 00:10 UTC. Our logs show the incident started on 6/8, 23:35 UTC and that during the 35 Minutes that it took to resolve the issue some of the customers in North Europe region would have experienced data latency and/or data loss while publishing logs to their workspace
- Root Cause: The failure was due to change that got deployed and was rolled back
- Incident Timeline: 35 Minutes - 6/8, 23:35 UTC through 6/9, 00:10 UTC
We understand that customers rely on Azure Log Analytics & Azure Sentinel as a critical service and apologize for any impact this incident caused.
Updated Jun 09, 2022
Version 3.0Azure-Monitor-Team
Silver Contributor
Joined February 13, 2019
Azure Monitor Status Archive
Follow this blog board to get notified when there's new activity