Live

ES-2377115

AI/BI, Lakeflow, Notebooks, and US West 2 had a partial outage. Databricks reports that the outage is resolved and lasted 47 minutes.

State

Resolved

Started

Lasted

47 min

Worst impact

Partial outage

Timeline

4 updates
22:0422:1622:2822:3922:51
Partial outageDegradedUpdate postedTimes in UTC

Investigating

47 min 100%

Updates

Times in UTC

As posted by Databricks

Resolved
Investigating

Impact Summary Between 21:24 UTC and 22:11 UTC on November 20, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Jobs and Login. Affected customers may have encountered job run failures, delayed job triggers, or authentication errors during this window. Symptoms • Job runs failing immediately or not completing • Scheduled or triggered jobs starting late or remaining pending • Intermittent login or authentication errors 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 21:24 UTC November 20, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Jobs, Delta Sharing, AI/BI Dashboards, and other related services. Affected customers may encounter failed job runs, errors when accessing shared data, or delays and failures in dashboard processing. Symptoms • Job runs failing with infrastructure-related termination errors • Errors or failed requests when accessing data through Delta Sharing • Delayed or failed AI/BI Dashboard processing 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

Impact Summary Starting at 21:40 UTC November 20, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Jobs, Delta Sharing, AI/BI Dashboards, and other related services. Affected customers may encounter failed job runs, errors when accessing shared data, or delays and failures in dashboard processing. Symptoms • Job runs failing with infrastructure-related termination errors • Errors or failed requests when accessing data through Delta Sharing • Delayed or failed AI/BI Dashboard processing 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.

Affected components

4
AI/BILakeflowNotebooksUS West 2

Databricks in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

5

Median duration

2 h 41 min

This incident

71% 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 41 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