# Databricks: ES-2342108

> Databricks reports that Compute, Databricks SQL, Lakeflow, and US West 2 did not work. Databricks reports that the incident is resolved. The outage lasted 171 minutes.

- Provider: [Databricks](https://outages.cc/databricks.md)
- Type: Incident
- State: Resolved
- Worst impact: Major outage
- Started: 2026-11-06 23:21 UTC
- Resolved: 2026-11-07 02:12 UTC (lasted 2 h 51 min)
- Components: Compute, Databricks SQL, Lakeflow, US West 2
- Official update: https://status.databricks.com

## Updates from Databricks

### resolved, 2026-11-07 02:12 UTC

No text.

### investigating, 2026-11-07 00:54 UTC

Impact Summary From 22:42 UTC on November 06, 2026 to 00:43 UTC on November 07, 2026, Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs were unavailable for customers using Databricks on AWS in the us-west-2 region. Affected customers may have encountered cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Service has been restored. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly Recommendations No customer action is required at this time. Current Status Service has been restored as of 00:43 UTC on November 07, 2026. We are actively monitoring to confirm full stabilization. We are aware of a cloud provider incident and are monitoring for impact. Refer to the cloud provider's status page for more information: https://health.aws.com/health/status Nex

### investigating, 2026-11-07 00:42 UTC

Impact Summary Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs. Affected customers may encounter cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly 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. The cloud provider has implemented mitigations to improve the availability of Serverless Compute, and we are seeing early signs of recovery in both Classic Compute and Serverless Compute. We are aware of a cloud provider incident and are monitoring for

### investigating, 2026-11-06 23:51 UTC

Impact Summary Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs. Affected customers may encounter cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly 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. We are aware of a cloud provider incident and are monitoring for impact. Refer to the cloud provider's status page for more information: https://health.aws.com/health/status Next Update We will provide another update within 1 hour, or sooner if there i

### investigating, 2026-11-06 23:24 UTC

Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Classic Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, delayed or failed SQL warehouse startups, and failures or delays in job and pipeline runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • SQL warehouses stuck in Starting or Resuming, with failed or slow queries • Jobs and pipeline runs failing, remaining pending, or not starting on schedule Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider, and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.