outages.live
Live
DatabricksIncident ·

ES-2342108

ResolvedOfficial update
0

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.

State

Resolved

Started

Lasted

2 h 51 min

Worst impact

Major outage

Timeline

5 updates
23:2100:0300:4601:2902:12
Major outagePartial outageDegradedUpdate postedTimes in UTC

Investigating

2 h 51 min 100%

Updates

Times in UTC

As posted by Databricks

Resolved
Investigating

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

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

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

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.

Affected components

4
ComputeDatabricks SQLLakeflowUS West 2

Databricks in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

1

Days with an incident

2

Median duration

2 h 51 min

This incident

About the median

Follow Databricks

Your coding agent knows when Databricks is down, and tells you when a failure is theirs, not yours. You can also get Databricks incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "databricks" and tell me if Databricks has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=databricks
Slack
/feed subscribe https://outages.cc/feed.xml?providers=databricks

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane