Databricks: ES-2375763, ES-2375817
Databricks updated the incident title from ES-2375763 to ES-2375763, ES-2375817, adding a second incident identifier. The evidence shows only a title edit, with no changes to customer impact or incident details.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: ComputeLakeflowNotebooks
Timeline of updates
- investigating
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.
- investigating
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.
- identified
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.
- monitoring
Impact Summary Between 06:27 UTC and 09:45 UTC November 20, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded availability with Serverless Compute, Jobs, and Notebooks. Affected customers may have encountered errors, cluster launch failures, or delays when starting or running serverless workloads during this window. Symptoms • Serverless workloads failing to start or encountering cluster allocation timeouts • Jobs remaining pending or failing to launch • Notebook commands failing or unable to attach to serverless compute 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.
- resolved
Impact Summary Between 06:27 UTC and 09:45 UTC on November 20, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded availability with Serverless Compute, Jobs, and Notebooks. Affected customers may have encountered failures when starting serverless workloads, cluster allocation timeouts, or jobs and notebooks that did not run as expected during this window. Symptoms • Serverless workloads failing to start or stuck pending cluster allocation • Jobs not starting on schedule, remaining pending, or failing unexpectedly • Notebook commands failing or unexpected workload termination 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.
Changes Rewindex caught on this incident
- Major incident: ES-2375763
- Incident updated: ES-2375763
- Incident silently edited: ES-2375763, ES-2375817
- Incident updated: ES-2375763, ES-2375817
- Incident updated: ES-2375763, ES-2375817
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.databricks.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Databricks, started 2026-11-20 08:22 UTC, resolved after 2.6 h, 5 update(s); edited after publishing.
- Title
- ES-2375763, ES-2375817
- Vendor
- Databricks
- Date
- URL
- https://rewindex.com/company/databricks/incidents/6b00032f2431f42d3f335c0f
Databricks profileRecent Databricks incidentsAll outages on November 20, 2026Databricks in November 2026MarkdownJSON