outages.live
Live
DatabricksMaintenance · 2026-11-15 06:00 UTC

Generic Planned Maintenance

MaintenanceOfficial update

A maintenance event is scheduled to occur between Nov 15, 2026, 6:00 AM UTC and Nov 15, 2026, 7:00 AM UTC. Actual service interruption for individual regions during this window is expected to take approximately 5 minutes. The following services may be impacted: - Workspace authentication requests may fail or time out. - Cluster start/resize/termination requests may fail or time out. - Jobs relying on cluster start/resize/termination may not execute. - Jobs submitted through APIs/Schedulers may not execute - UI and Databricks SQL queries may time out. - Users may experience failures launching Databricks SQL Serverless Warehouses. - Users may not be able to access UC APIs. Currently running jobs may be interrupted.

The latest update from Databricks.

State

Scheduled

Starts

in 13 d

2026-11-15 06:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Databricks

Scheduled2026-11-02 13:12 UTC

A maintenance event is scheduled to occur between Nov 15, 2026, 6:00 AM UTC and Nov 15, 2026, 7:00 AM UTC. Actual service interruption for individual regions during this window is expected to take approximately 5 minutes. The following services may be impacted: - Workspace authentication requests may fail or time out. - Cluster start/resize/termination requests may fail or time out. - Jobs relying on cluster start/resize/termination may not execute. - Jobs submitted through APIs/Schedulers may not execute - UI and Databricks SQL queries may time out. - Users may experience failures launching Databricks SQL Serverless Warehouses. - Users may not be able to access UC APIs. Currently running jobs may be interrupted.

Affected components

11
Agent BricksAI/BIComputeDatabricks AppsDatabricks SQLGenieLakebaseLakeflow

Databricks in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

Not enough data

This incident

Not comparable

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