Azure Databricks experienced compute service failures in the East US region for 10.9 hours, affecting Classic Compute, Jobs Compute, and later Serverless Compute workloads. Customers encountered cluster launch failures, job run failures during startup, and Serverless workloads failing to start. The incident was caused by an underlying Azure cloud provider issue, with Databricks engineering working directly with Azure to implement mitigations and achieve partial recovery.
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.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters or running jobs.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
Recommendations
No customer action is required at this time.
Current Status
Databricks engineering is actively investigating. We are aware of a cloud provider incident and are monitoring for impact.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters or running jobs.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
Recommendations
No customer action is required at this time.
Current Status
Databricks engineering is working directly with the cloud provider to mitigate this incident. We will provide updates as the situation progresses.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs. Starting at 14:24 UTC, Serverless Compute workloads may also fail to start.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
Databricks engineering is working directly with the cloud provider to mitigate this incident. We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs. Starting at 14:24 UTC, Serverless Compute workloads may also fail to start.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
Databricks engineering is working directly with the cloud provider to mitigate this incident. We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs. Starting at 14:24 UTC, Serverless Compute workloads may also fail to start.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
- We are starting to see recovery in Serverless Compute.
- Databricks engineering is working directly with the cloud provider to mitigate this incident. The cloud provider is taking mitigation actions.
- We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs.
Starting at 14:24 UTC, Serverless Compute workloads may also fail to start or encounter delays.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
- Serverless cluster launches are mostly succeeding but some delays may be encountered.
- We are starting to see some recovery in Classic Compute and Jobs.
- The cloud provider has partially restored service in the region, with additional mitigation in progress.
- We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs.
Starting at 14:24 UTC, Serverless Compute workloads may also fail to start or encounter delays.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
- Serverless cluster launches are mostly succeeding but some delays may be encountered.
- We are starting to see some recovery in Classic Compute and Jobs.
- The cloud provider has partially restored service in the region, with additional mitigation in progress.
We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026, 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs.
Starting at 14:24 UTC, Serverless Compute workloads may also fail to start or encounter delays.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
- Serverless cluster launches are mostly succeeding but some delays may be encountered.
- We had seen some recovery in Classic Compute and Jobs, but have observed some new performance regression.
- The cloud provider has partially restored service in the region, with additional mitigation in progress.
We will provide updates as the situation progresses. Please refer to the Azure status page for additional information: https://azure.status.microsoft
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting on 24 April 2026 at 11:39 UTC, customers using Classic Compute and Jobs Compute in Azure East US may experience failures when starting clusters and running jobs.
Starting at 14:24 UTC, Serverless Compute workloads may also fail to start or encounter delays.
Symptoms
Customers may observe:
- Cluster launch failures
- Job run failures or terminations during cluster startup
- Serverless Compute workloads failing to start
Recommendations
No customer action is required at this time.
Current Status
- Serverless cluster launches are mostly succeeding but some delays may be encountered.
- We had seen some recovery in Classic Compute and Jobs Compute, but have observed some new performance regression.
- The cloud provider has partially restored service in the region, with additional mitigation in progress. Please refer to the Azure status page for additional information: https://azure.status.microsoft.com/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