Databricks Azure incident

ES-2208537

Minor Resolved View vendor source →

Databricks Azure experienced a minor incident on September 12, 2026 affecting Compute and Lakeflow and 1 more component, lasting 2h 55m. The incident has been resolved; the full update timeline is below.

Started
Sep 12, 2026, 05:50 AM UTC
Resolved
Sep 12, 2026, 08:45 AM UTC
Duration
2h 55m
Detected by Pingoru
Sep 12, 2026, 05:50 AM UTC

Affected components

ComputeLakeflowUnity Catalog (West Europe)

Update timeline

  1. investigating Sep 12, 2026, 05:50 AM UTC

    Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters 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.

  2. investigating Sep 12, 2026, 05:50 AM UTC

    We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. investigating Sep 12, 2026, 06:43 AM UTC

    Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters 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 12, 2026, 06:43 AM UTC

    Impact Summary Starting at 05:06 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters 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 12, 2026, 08:05 AM UTC

    Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, and failed or terminated job and pipeline runs. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Notebook attach failures on customer-managed compute • Jobs and pipeline runs failing, terminating during cluster startup, or not progressing 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 12, 2026, 08:05 AM UTC

    Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, and failed or terminated job and pipeline runs. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Notebook attach failures on customer-managed compute • Jobs and pipeline runs failing, terminating during cluster startup, or not progressing 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 12, 2026, 08:36 AM UTC

    Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been mitigated and service is operational. Mitigation was carried out 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 12, 2026, 08:36 AM UTC

    Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been mitigated and service is operational. Mitigation was carried out 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 12, 2026, 08:45 AM UTC

    Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been resolved, and all affected services have been restored. Follow-up analysis is being conducted 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