Changes / Databricks / ES-2281237
Databricks: Major incident: ES-2281237
Summary
Databricks reported a major outage affecting Serverless Compute on AWS in US West 2, causing workload startup failures, allocation timeouts, and dependent service failures; classic compute was unaffected. Reported impact began at 12:30 UTC on October 12, 2026; the incident was resolved at 2026-10-12 17:42 UTC, with a recorded duration of 4 h 45 min.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
Major incidentLabel: outage (model (Jev), 54%)Changed Detected Source: status.databricks.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: ES-2281237
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-10-12 12:57 UTC
Before: not present
After: 2026-10-12 17:42 UTC
Before: not present
After: AI/BI, Compute, Databricks SQL, Genie, Lakeflow
Before: not present
After: We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run serverless workloads for notebooks, jobs, and Lakeflow pipelines. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on serverless compute Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including notebooks, jobs, Lakeflow pipelines, SQL warehouses, and AI/BI dashboards and Genie. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start, or queries failing • AI/BI dashboards and Genie spaces failing to load or run queries Recommendations No customer action is required at this time. Current Status Our engineering teams are actively investigating elevated failures in Serverless compute allocation in this region. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including notebooks, jobs, Lakeflow pipelines, SQL warehouses, and AI/BI dashboards and Genie. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS • Serverless job runs are failing or terminating unexpectedly • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start, or queries failing • AI/BI dashboards and Genie spaces failing to load or run queries Recommendations No customer action is required at this time. Current Status Our engineering teams are actively investigating elevated failures in Serverless compute allocation in this region. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Starting at 12:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Serverless workloads, including jobs, Lakeflow pipelines, SQL warehouses, and AI/BI dashboards, and Genie. Classic (non-serverless) compute is not affected. Symptoms • Serverless workloads failing to start or timing out during cluster allocation, with errors such as ALLOCATION_TIMEOUT_NO_MATCHED_CLUSTERS or ALLOCATION_TIMEOUT_NO_UNALLOCATED_CLUSTERS • Serverless job runs failing or timing out • Errors when running Lakeflow pipelines on Serverless compute • Serverless SQL warehouses failing to start • AI/BI dashboards and Genie spaces are unable to run queries Recommendations No customer action is required at this time. Current Status Our engineering teams have identified a potential issue with retrieving container images required to start Serverless compute in this region. We are actively working with our cloud provider to resolve it. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Between 12:30 UTC and 16:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Genie. Affected customers may have encountered failures starting serverless workloads, cluster allocation timeouts, or failed and delayed job, pipeline, query, and dashboard operations during this window. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Serverless SQL warehouses are stuck in Starting, and queries, dashboards, or Genie requests are failing or timing out • Jobs and Declarative Pipelines run remaining pending, failing, or not progressing Current Status The issue has been mitigated, and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
Before: not present
After: Impact Summary Between 12:30 UTC and 16:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Genie. Affected customers may have encountered serverless workloads failing to start, cluster allocation timeouts, or failures in dependent jobs, pipelines, SQL warehouses, dashboards, and Genie experiences during this window. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Jobs and pipeline runs remaining pending, failing, or not progressing • Serverless SQL warehouses, AI/BI dashboards, and Genie spaces failing to start, load, or respond Current Status The issue has been resolved, and all affected services have been restored. 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 a support ticket or contact help@databricks.com.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: ES-2281237 (this change) Databricks reported a major outage affecting Serverless Compute on AWS in US West 2, causing workload startup failures, allocation timeouts, and dependent service failures; classic compute was unaffected. Reported impact began at 12:30 UTC on October 12, 2026; the incident was resolved at 2026-10-12 17:42 UTC, with a recorded duration of 4 h 45 min. | Major incident |
All Databricks changes → · Databricks profile · Markdown · JSON