Azure Databricks experienced a 12-hour service disruption starting at 05:25 UTC on May 29, 2026, caused by underlying Azure cloud provider infrastructure issues. The incident affected Classic Compute, Serverless Compute, Databricks Apps, Unity Catalog, and Jobs Service, with customers experiencing cluster launch failures, job execution failures, and degraded application availability. Services showed gradual recovery throughout the incident as Databricks worked with Azure to resolve the underlying infrastructure problems.
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 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We are actively investigating failures affecting Classic Compute, Serverless Compute, and Databricks Apps in collaboration with our cloud provider, and are working to restore full service availability as quickly as possible.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. For live updates on the underlying infrastructure status, customers can refer to the Azure status page at https://azure.status.microsoft/en-us/status.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute appears to be showing partial recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability.
Symptoms
• Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads
• Jobs and runs failing to start or complete due to compute unavailability
• Databricks Apps and Unity Catalog experiencing degraded availability or errors
Recommendations
No customer action is required at this time.
Current Status
We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status.
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