Starting at 02:17 UTC on September 22, 2026, Azure Databricks Serverless Compute and Jobs Service in East US experienced degraded availability for approximately 9.7 hours, affecting serverless notebooks, workflows, and Lakeflow pipelines. Customers encountered workloads failing to start, cluster allocation timeouts, unexpected terminations, and jobs or pipelines stuck in a pending state. The root cause was identified in coordination with the cloud provider, and mitigation efforts were actively in progress as of the final update.
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 at 02:17 UTC September 22, 2026, customers using Azure Databricks in East US may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow Declarative Pipelines.
Symptoms
• Serverless workloads failing to start or remaining in a pending state while waiting for resources
• Cluster allocation and launch timeouts
• Unexpected termination of serverless workloads, or errors returned when attempting to execute them
Recommendations
No customer action is required at this time.
Current Status
The issue is under active investigation, including coordination with the cloud provider.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines.
Symptoms
• Serverless workloads failing to start or timing out during cluster allocation
• Unexpected termination of running serverless workloads
• Errors returned when attempting to execute serverless notebooks, jobs, or pipelines
• Pipelines remaining in a waiting-for-resources state
Recommendations
No customer action is required at this time.
Current Status
The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines.
Symptoms
• Serverless workloads failing to start or timing out during cluster allocation
• Unexpected termination of running serverless workloads
• Errors returned when attempting to execute serverless notebooks, jobs, or pipelines
• Pipelines remaining in a waiting-for-resources state
Recommendations
No customer action is required at this time.
Current Status
The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring.
Next Update
We will provide another update within 2 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines.
Symptoms
• Serverless workloads failing to start or timing out during cluster allocation
• Unexpected termination of running serverless workloads
• Errors returned when attempting to execute serverless notebooks, jobs, or pipelines
• Pipelines remaining in a waiting-for-resources state
Recommendations
No customer action is required at this time.
Current Status
The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring.
Next Update
We will provide another update within 2 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines.
Symptoms
• Serverless workloads failing to start or timing out during cluster allocation
• Unexpected termination of running serverless workloads
• Errors returned when attempting to execute serverless notebooks, jobs, or pipelines
• Pipelines remaining in a waiting-for-resources state
Recommendations
No customer action is required at this time.
Current Status
The issue has been identified in coordination with the cloud provider, and mitigation efforts are in progress. Impact is not yet confirmed to have stopped.
Next Update
We will provide another update within 2 hours, or sooner if there is a material change in service status.
Impact Summary
Starting at 02:17 UTC September 22, 2026, customers using Azure Databricks in East US may experience transient failures or degraded availability with Serverless Compute and Jobs. Affected customers may encounter cluster launch timeouts, unexpected workload termination, or jobs and pipelines that remain pending or fail to progress.
Symptoms
• Serverless workloads failing to start, with cluster launch or allocation timeouts
• Jobs and pipeline runs stuck waiting for resources, delayed, or failing to complete
• Cancellation requests for running jobs or pipelines remaining in progress for extended periods
Recommendations
No customer action is required at this time.
Current Status
The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider.
Next Update
We will provide another update within 2 hours, 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