Azure Databricks experienced a service incident affecting the Notebooks service, where customers encountered errors when submitting notebook workloads to clusters, executing notebook commands, and attaching notebooks to clusters. The issue began at approximately 00:43 UTC on June 10, 2026 and lasted 1.6 hours, disrupting notebook workflows for a subset of users. The engineering team identified the root cause and implemented a mitigation to resolve the service disruption.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
We are actively investigating an issue with the Databricks service.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 00:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows.
Symptoms
• Errors when attempting to submit or run notebooks against a cluster
• Notebook commands failing to execute, resulting in connection or communication errors
• Inability to attach notebooks to clusters
Recommendations
No customer action is required at this time.
Current Status
We are actively investigating incident causing errors and failures for customers using the Notebooks service, and our engineering team is working to identify and apply a resolution.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 0:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows.
Symptoms
• Errors when attempting to submit or run notebooks against a cluster
• Notebook commands failing to execute, resulting in connection or communication errors
• Inability to attach notebooks to clusters
Recommendations
No customer action is required at this time.
Current Status
Our engineering team has identified the root cause of the incident impacting the Notebooks service and has implemented a mitigation. We are continuing to investigate and closely monitor the situation.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with