**AWS Databricks Service Incident – US East 1** Starting at 06:27 UTC on November 20, 2026, Databricks on AWS in US East 1 experienced degraded availability with Serverless Compute, Jobs, and Notebooks, lasting approximately 1.7 hours. Users encountered failures starting serverless workloads, cluster allocation timeouts, intermittently failing or delayed scheduled jobs, and notebook command errors. The root cause was identified and mitigation was put in place, with the recommended workaround being to retry failed tasks or use the Repair Run feature for affected job runs.
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 with the Databricks service.
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 06:27 UTC November 20, 2026, customers using Databricks on AWS in US East 1 may experience degraded availability with Serverless Compute. Affected customers may encounter failures when starting or running serverless workloads for notebooks, workflows, and Lakeflow pipelines.
Symptoms
• Serverless workloads failing to start or cluster allocation timeouts
• Unexpected termination of serverless jobs, pipelines, and apps
• Errors returned when executing serverless workloads, including library installation failures
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.
Impact Summary
Starting at 06:27 UTC November 20, 2026, customers using Databricks on AWS in US East 1 may be experiencing degraded availability with Serverless Compute, Jobs, and Notebooks. Affected customers may encounter failures when starting serverless workloads, failed or delayed job runs, and errors when executing notebook commands.
Symptoms
• Serverless workloads failing to start or cluster allocation timeouts
• Scheduled jobs failing intermittently or remaining pending
• Notebook commands failing with errors or timing out
Recommendations
Customers whose scheduled serverless jobs fail intermittently should retry the failed tasks or use Repair run.
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.
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