AWS Databricks in US East 1 experienced a major outage beginning at 22:57 UTC on September 21, 2026, resulting in complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected users encountered cluster launch failures, allocation timeouts, notebook attach failures, and jobs or pipeline runs that failed to start or progress. The root cause was identified within approximately 50 minutes, with mitigation efforts initiated in coordination with AWS.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with