Databricks Azure incident

ES-2206489

Resolved after 3 hours 49 minutes, affecting Compute and Lakeflow and 1 more, on September 11, 2026.

resolved Sep 11, 2026, 10:57 AM UTC

Impact Summary Between 06:03 UTC and 09:30 UTC on September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch and termination failures, along with delayed or failed job and pipeline runs during this window. Symptoms • Cluster launch failures or clusters remaining in Pending or Starting states • Cluster termination failures or delays • Jobs failing to start on schedule, remaining pending, or failing immediately • Pipeline runs failing to complete or not progressing Current Status The issue has been resolved, and all affected services have been restored. Recovery was confirmed in coordination with the cloud provider. Next Update This is the final update for this incident. We apologize 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

Started
Sep 11, 2026, 07:07 AM UTC
Resolved
Sep 11, 2026, 10:57 AM UTC
Duration
3h 49m
Detected by Pingoru
Sep 11, 2026, 07:07 AM UTC

Affected components

ComputeLakeflowUnity Catalog (Unity Catalog — China North 2)Unity Catalog (Unity Catalog — China North 3)

Update timeline

  1. investigating Sep 11, 2026, 07:07 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.

  2. investigating Sep 11, 2026, 07:07 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.

  3. investigating Sep 11, 2026, 08:00 AM UTC

    Impact Summary Starting at 06:03 UTC September 11, 2026, customers using Azure Databricks may experience degraded availability with cluster launch and cluster termination operations. Affected customers may encounter cloud provider launch failures, network health check failures, and delays or errors when starting or terminating compute. Symptoms • Cluster launch failures with cloud provider launch errors • Failed or delayed cluster termination requests • Network check failures during compute 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.

  4. investigating Sep 11, 2026, 08:00 AM UTC

    Impact Summary Starting at 06:03 UTC September 11, 2026, customers using Azure Databricks may experience degraded availability with cluster launch and cluster termination operations. Affected customers may encounter cloud provider launch failures, network health check failures, and delays or errors when starting or terminating compute. Symptoms • Cluster launch failures with cloud provider launch errors • Failed or delayed cluster termination requests • Network check failures during compute 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.

  5. identified Sep 11, 2026, 09:06 AM UTC

    Impact Summary Starting at 06:03 UTC on September 11, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch and termination failures, clusters remaining in a pending state, and job runs that fail to start or terminate unexpectedly. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Cluster termination requests failing or delayed • Jobs failing to start on schedule, remaining pending, or failing 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.

  6. identified Sep 11, 2026, 09:06 AM UTC

    Impact Summary Starting at 06:03 UTC on September 11, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch and termination failures, clusters remaining in a pending state, and job runs that fail to start or terminate unexpectedly. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Cluster termination requests failing or delayed • Jobs failing to start on schedule, remaining pending, or failing 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.

  7. monitoring Sep 11, 2026, 09:59 AM UTC

    Impact Summary Between 06:03 UTC and 09:30 UTC September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch and termination failures, delayed or failed job runs, and pipeline runs that did not complete during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster termination failures and notebook attach failures • Jobs and pipeline runs failing, remaining pending, or not progressing Current Status The issue has been mitigated and service is operational. Mitigation was confirmed 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.

  8. monitoring Sep 11, 2026, 09:59 AM UTC

    Impact Summary Between 06:03 UTC and 09:30 UTC September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch and termination failures, delayed or failed job runs, and pipeline runs that did not complete during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster termination failures and notebook attach failures • Jobs and pipeline runs failing, remaining pending, or not progressing Current Status The issue has been mitigated and service is operational. Mitigation was confirmed 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.

  9. resolved Sep 11, 2026, 10:57 AM UTC

    Impact Summary Between 06:03 UTC and 09:30 UTC on September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch and termination failures, along with delayed or failed job and pipeline runs during this window. Symptoms • Cluster launch failures or clusters remaining in Pending or Starting states • Cluster termination failures or delays • Jobs failing to start on schedule, remaining pending, or failing immediately • Pipeline runs failing to complete or not progressing Current Status The issue has been resolved, and all affected services have been restored. Recovery was confirmed in coordination with the cloud provider. Next Update This is the final update for this incident. We apologize 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

Your product runs on more than Databricks Azure

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →