ES-2281237

What to do

• Check whether you use Databricks in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-12 17:42 UTC and 2026-10-12 17:42 UTC may need a replay.

• Subscribe to Databricks's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=databricks works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Databricks 1

1. resolvedOct 12, 2026, 5:42 PM UTC

   October 12, 2026 12:57 UTC Investigating - 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. October 12, 2026 13:15 UTC Investigating - 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. October 12, 2026 14:12 UTC Investigating - 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. October 12, 2026 15:15 UTC Investigating - 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. October 12, 2026 16:14 UTC Identified - 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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.