ES-2375763
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 updatesInvestigating
53 min 100%
Updates
Times in UTCAs posted by Databricks
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.
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
3Databricks in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
5
Median duration
2 h 51 min
This incident
69% shorter than the median
Other Databricks incidents
All incidentsDatabricks·ES-2367923
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.
Databricks·ES-2359687
Databricks reported degraded performance with AI/BI, Databricks Apps, Model Serving, and Genie in all listed regions. The incident is resolved. It lasted from 15:50 UTC to about 23:09 UTC on November 13, 2026.
Databricks·ES-2342108
Databricks Compute, Databricks SQL, Lakeflow, and US West 2 had a major outage. Databricks reports that the outage is resolved. The outage lasted 171 minutes.
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.
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.
https://outages.live/feed.xml?providers=databricks/feed subscribe https://outages.live/feed.xml?providers=databricksFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane