Live

ES-2367923

0

Databricks reported degraded Serverless Compute, Databricks SQL, and Lakeflow across all listed regions. Databricks identified the issue, completed a rollback, and stated that the service is operational again. Databricks resolved the incident after 93 minutes.

State

Resolved

Started

Lasted

1 h 33 min

Worst impact

Degraded

Timeline

4 updates
19:3019:5320:1620:4021:03
DegradedUpdate postedTimes in UTC

Investigating

1 h 33 min 100%

Updates

Times in UTC

As posted by Databricks

Resolved
Investigating

Impact Summary Between 18:43 UTC and 19:56 UTC November 17, 2026, customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered serverless workloads failing to start, cluster allocation timeouts, or jobs and pipeline runs that did not start or complete during this window. Symptoms • Serverless workloads failing to start or stalling at launch • Cluster allocation timeouts or errors when running serverless workloads • Jobs and pipeline runs remaining pending, failing, or not progressing Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Investigating

Impact Summary Starting at 2026-11-17 18:43 UTC, customers using Serverless Compute in multiple regions across AWS, Azure, and GCP may experience delays or failures when starting compute. Symptoms Customers may observe: - Serverless compute remaining in a starting state, or failing to start - Notebooks, jobs, or pipelines that use serverless compute being delayed or failing to start Recommendations No customer action is required at this time. Current Status We have identified the issue preventing serverless compute from starting. A rollback is in progress to restore normal service. Next Update We will provide another update within 1 hour.

Investigating

We are actively investigating an issue with the Databricks service. We will provide another update within 1 hour, or sooner if there is a material change in service status.

Affected components

20
ComputeDatabricks SQLLakeflowCA Central 1EU West 1EU West 2EU West 3EU Central 1

Databricks in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

4

Median duration

2 h 51 min

This incident

46% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 56 min
median 2 h 51 min
90 days agoToday

Other Databricks incidents

All incidents

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.live/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.live/feed.xml?providers=databricks
Slack
/feed subscribe https://outages.live/feed.xml?providers=databricks

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane