- Level
- confirmed
- Worst impact
- Major outage
- Components
- Compute, Databricks SQL, Lakeflow
- Regions
- us
- Down Index
- 60of 100
Summary
Databricks says Classic Compute, Serverless Compute, Databricks SQL and Lakeflow Jobs were unavailable for AWS customers in us-west-2 from 22:42 UTC November 6 to 00:43 UTC November 7, 2026. Service is restored and being monitored for full stabilization.
Written by anthropic/claude-haiku-5.5 from Databricks's own updates.
What to do
Check whether you use Databricks Compute, Databricks SQL, Lakeflow 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 2h 50m it lasted.
Anything that failed between 2026-11-06 23:21 UTC and 2026-11-07 02:11 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 4
- investigating
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.
provider
- identified
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 is a material change in service status.
provider
- identified
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 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 is a material change in service status.
provider
- monitoring
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 Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-9d88eb2acc
Is Databricks still down?
No, this incident was resolved 2026-11-07 02:11 UTC. For Databricks's live state, see https://down.guide/databricks.
How long did it last?
2h 50m, from 2026-11-06 23:21 UTC to 2026-11-07 02:11 UTC, by the times Databricks posted.
What was affected?
Databricks named Compute, Databricks SQL, Lakeflow in us.
What caused it?
Databricks hasn't published a root cause. If it does, it shows here.
Where does this come from?
Databricks's official status page, https://status.databricks.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.