- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 12of 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-22 00:51 UTC and 2026-09-22 00:51 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
- resolved
September 21, 2026 23:22 UTC Investigating - We are actively investigating an issue affecting Databricks compute. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 21, 2026 23:25 UTC Investigating - Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may experience degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, operation timeouts, and jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures and job run terminations during cluster startup • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue is under active investigation, with triage ongoing in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 21, 2026 23:48 UTC Identified - Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may be experiencing a complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may encounter compute launch and termination failures, cluster allocation timeouts, and jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures; clusters stuck in Pending or Starting, and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. September 21, 2026 23:58 UTC Monitoring - Impact Summary Between 22:57 UTC and 23:45 UTC on September 21, 2026, customers using Databricks on AWS in US East 1 may have experienced complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch failures, allocation timeouts, and failed or terminated workloads during this window. Symptoms • Classic compute cluster launch failures, with clusters stuck in Pending or Starting and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing 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 22, 2026 00:51 UTC Resolved - Impact Summary Between 22:57 UTC and 23:45 UTC on September 21, 2026, customers using Databricks on AWS in US East 1 may have experienced complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have been unable to launch new compute, and jobs and pipeline runs may have failed, remained pending, or terminated unexpectedly during this window. Symptoms • Cluster launch failures, with clusters stuck in Pending or Starting, and notebook attach failures • Serverless workloads failing to start, with allocation timeouts or unexpected workload termination • Jobs and pipeline runs not starting on schedule, failing immediately, or not progressing Current Status The incident has been fully resolved, and service is operating normally. Next Update This is the final update for this incident. We apologize for any inconve
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-8e9359563c
Is Databricks still down?
No, this incident was resolved 2026-09-22 00:51 UTC. For Databricks's live state, see https://down.guide/databricks.
How long did it last?
0m, from 2026-09-22 00:51 UTC to 2026-09-22 00:51 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.