Changes / Databricks / ES-2231583
Databricks: Critical incident: ES-2231583
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: critical (vendor)Changed Detected Source: status.databricks.com (opens in new tab)
What changed
Before: not present
After: ES-2231583
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-09-21 23:22 UTC
Before: not present
After: 2026-09-22 00:51 UTC
Before: not present
After: Compute, Databricks SQL, Lakeflow
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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 inconvenience this may have caused. If you require further details about this incident, please submit a support ticket or contact help@databricks.com.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: ES-2231583 (this change) | Major incident |
All Databricks changes → · Databricks profile · Markdown · JSON