ES-2281237

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.

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.

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.

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.

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.