outages.live
Live

Databricks

Databricks is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

11
Agent Bricks Operational
90 days agoNo incidentsToday
AI/BI Operational
90 days agoNo incidentsToday
Compute Operational
90 days agoNo incidentsToday
Databricks Apps Operational
90 days agoNo incidentsToday
Databricks SQL Operational
90 days agoNo incidentsToday
Genie Operational
90 days agoNo incidentsToday
Lakebase Operational
90 days agoNo incidentsToday
Lakeflow Operational
90 days agoNo incidentsToday
Notebooks Operational
90 days agoNo incidentsToday
Unity Catalog Operational
90 days agoNo incidentsToday
Free Edition Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Maintenance

Regular Planned Maintenance

A maintenance event is scheduled on Sunday, November 15, 2026, from 05:00 UTC to 06:00 UTC. A brief service interruption of approximately 10 minutes is expected during this window. During this maintenance period, the following capabilities may be temporarily unavailable: - Databricks SQL queries and SQL warehouses may return errors or fail to connect - API requests to Databricks SQL endpoints may fail - Jobs and scheduled queries relying on SQL warehouses may fail to execute Recommendations We recommend avoiding job submissions or SQL warehouse operations in AWS US East 2 (Ohio) during the maintenance window. No other customer action is required.

Maintenancestarts in 13 d

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane