Skip to main content
Databricks

ES-2248197

Partial outage Lasted 0m · started · Databricks's page

Level
confirmed
Worst impact
Partial outage
Regions
us
Down Index
22of 100

What to do

  • Check whether you use Databricks in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-09-29 18:54 UTC and 2026-09-29 18:54 UTC may need a replay.
  • Subscribe to Databricks's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=databricks works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Databricks 1

  1. resolved

    September 29, 2026 17:10 UTC Investigating - Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Azure Databricks in West US 3 may experience failures or degraded availability with Declarative Pipelines. Affected customers may encounter pipeline runs that fail, do not start, or do not progress. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Missing or delayed pipeline status information 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. September 29, 2026 17:43 UTC Identified - Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Databricks may experience failures or degraded performance with Declarative Pipelines. Affected customers may find that pipeline runs fail intermittently or do not complete as expected. Symptoms • Pipeline runs failing with CONTROL_PLANE_FAILURE errors • Pipeline runs not progressing or terminating unexpectedly • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 29, 2026 17:55 UTC Monitoring - Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded availability with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipelines that did not progress as expected during this window. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Delayed or missing pipeline status information 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. September 29, 2026 18:54 UTC Resolved - Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded performance with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipeline runs that did not progress during this window. Symptoms • Pipeline runs failing with control plane failure errors • Pipeline runs not progressing or not terminating as expected • Delayed or missing pipeline status information Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit a support ticket or contact help@databricks.com.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-c2e12d8fb5

Is Databricks still down?

No, this incident was resolved 2026-09-29 18:54 UTC. For Databricks's live state, see https://down.guide/databricks.

How long did it last?

0m, from 2026-09-29 18:54 UTC to 2026-09-29 18:54 UTC, by the times Databricks posted.

What was affected?

Databricks named in us.

What caused it?

Databricks hasn't published a root cause. If it does, it shows here.

Where does this come from?

Databricks's official status page, https://status.databricks.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.