Databricks Azure experienced a major incident on September 7, 2026 affecting Compute and Lakeflow and 1 more component, lasting 23h 23m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 07, 2026, 06:40 AM UTC
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.
- investigating Sep 07, 2026, 06:40 AM UTC
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.
- investigating Sep 07, 2026, 07:32 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks in East US 2 may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job runs that fail or terminate during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing to start or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation, in 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.
- investigating Sep 07, 2026, 07:32 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks in East US 2 may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job runs that fail or terminate during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing to start or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation, in 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.
- identified Sep 07, 2026, 07:36 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 07:36 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 08:35 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 08:35 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 09:33 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 09:33 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 10:37 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 10:37 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 11:33 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 11:33 AM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 12:38 PM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, or unexpected termination of workloads during cluster startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 12:38 PM UTC
Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, or unexpected termination of workloads during cluster startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing, remaining pending, or terminating during cluster startup 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 1 hour, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 01:41 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 01:41 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 02:53 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to Serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 02:53 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to Serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 04:17 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 04:17 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 06:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 06:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 08:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 08:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 10:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 07, 2026, 10:46 PM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 08, 2026, 12:46 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 08, 2026, 12:46 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 08, 2026, 03:46 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, some Azure Databricks customers experienced degraded availability with Classic Compute and Jobs. Impact included cluster launch failures and timeouts, as well as job or pipeline runs that failed or did not complete. At approximately 14:28 UTC, the cloud provider applied a mitigation. Service availability has improved in East US 2, UAE North, Sweden Central, and West Europe, and recovery has also begun in North Central US. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. We are continuing to monitor the recovery closely, and service availability is now significantly improved compared with earlier in the incident. The incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- identified Sep 08, 2026, 03:46 AM UTC
Impact Summary: Starting at 06:03 UTC on September 07, 2026, some Azure Databricks customers experienced degraded availability with Classic Compute and Jobs. Impact included cluster launch failures and timeouts, as well as job or pipeline runs that failed or did not complete. At approximately 14:28 UTC, the cloud provider applied a mitigation. Service availability has improved in East US 2, UAE North, Sweden Central, and West Europe, and recovery has also begun in North Central US. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. We are continuing to monitor the recovery closely, and service availability is now significantly improved compared with earlier in the incident. The incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.
- monitoring Sep 08, 2026, 04:58 AM UTC
Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been mitigated and service is operational. Mitigation was completed in coordination with the cloud provider, and recovery continues to be monitored. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Sep 08, 2026, 04:58 AM UTC
Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been mitigated and service is operational. Mitigation was completed in coordination with the cloud provider, and recovery continues to be monitored. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- resolved Sep 08, 2026, 06:04 AM UTC
Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been resolved, and all affected services have been restored. Resolution was confirmed in coordination with the cloud provider. Next Update: This is the final update for this incident. We apologise for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription