Live

ES-2375763

Partial outageOfficial update
0

Databricks Serverless Compute does not work correctly for notebooks, workflows, and Lakeflow pipelines in US East 1. Databricks reports the issue as investigating. Databricks says no customer action is required at this time.

State

Investigating

Started

Ongoing for

53 min

Worst impact

Partial outage

Timeline

2 updates
08:2208:3508:4809:0109:14
Partial outageDegradedUpdate postedTimes in UTC

Investigating

53 min 100%

Updates

Times in UTC

As posted by Databricks

Investigating

Impact Summary Starting at 06:27 UTC November 20, 2026, customers using Databricks on AWS in US East 1 may experience degraded availability with Serverless Compute. Affected customers may encounter failures when starting or running serverless workloads for notebooks, workflows, and Lakeflow pipelines. Symptoms • Serverless workloads failing to start or cluster allocation timeouts • Unexpected termination of serverless jobs, pipelines, and apps • Errors returned when executing serverless workloads, including library installation failures 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.

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

3
ComputeLakeflowUS East 1

Databricks in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

5

Median duration

2 h 51 min

This incident

69% 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