Azure Databricks experienced an incident beginning around 20:00 UTC on August 4, 2026, lasting approximately 36 minutes, during which customers encountered failures, errors, timeouts, and slowness across Classic Compute clusters, Notebooks, and the Jobs Service. API requests were also intermittently failing. The engineering team identified a likely problematic deployment as the cause and initiated a rollback to resolve the issue.
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 affecting Databricks compute.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 20:00 UTC on August 4, 2026, customers using Azure Databricks may be experiencing failures or errors when using Classic Compute or Notebooks services. Some operations may fail, time out, or be delayed. We are actively investigating the issue.
Symptoms
• Failures or errors when starting or running Classic Compute clusters
• Notebooks may fail to load, execute commands, or respond slowly
• Intermittent API request failures affecting compute and notebook operations
Recommendations
No customer action is required at this time.
Current Status
The incident is in the Investigating stage; teams have identified a likely correlated deployment and are actively rolling it back while confirming root cause.
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