rewindex

CompaniesDatabricksIncidents

Databricks: ES-2342108

CriticalStatus: resolvededitedStarted Resolved (2.8 h)5 updatesstatus.databricks.com (opens in new tab)

Affected components: ComputeDatabricks SQLLakeflow

Timeline of updates

  1. investigating

    Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS in US West 2 may experience degraded availability with Classic Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, delayed or failed SQL warehouse startups, and failures or delays in job and pipeline runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • SQL warehouses stuck in Starting or Resuming, with failed or slow queries • Jobs and pipeline runs failing, remaining pending, or not starting on schedule Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider, 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.

  2. identified

    Impact Summary Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs. Affected customers may encounter cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly 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. We are aware of a cloud provider incident and are monitoring for impact. Refer to the cloud provider's status page for more information: https://health.aws.com/health/status (opens in new tab) Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  3. identified

    Impact Summary Starting at 22:42 UTC on November 06, 2026, customers using Databricks on AWS may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs. Affected customers may encounter cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly 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. The cloud provider has implemented mitigations to improve the availability of Serverless Compute, and we are seeing early signs of recovery in both Classic Compute and Serverless Compute. We are aware of a cloud provider incident and are monitoring for impact. Refer to the cloud provider's status page for more information: https://health.aws.com/health/status (opens in new tab) Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  4. monitoring

    Impact Summary From 22:42 UTC on November 06, 2026 to 00:43 UTC on November 07, 2026, Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs were unavailable for customers using Databricks on AWS in the us-west-2 region. Affected customers may have encountered cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Service has been restored. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly Recommendations No customer action is required at this time. Current Status Service has been restored as of 00:43 UTC on November 07, 2026. We are actively monitoring to confirm full stabilization. We are aware of a cloud provider incident and are monitoring for impact. Refer to the cloud provider's status page for more information: https://health.aws.com/health/status (opens in new tab) Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  5. resolved

    Impact Summary From 22:42 UTC on November 06, 2026 to 00:43 UTC on November 07, 2026, Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs were unavailable for customers using Databricks on AWS in the us-west-2 region. Affected customers may have encountered cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly Current Status This incident has been resolved, and normal operation of all affected services has been restored. 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. This incident was related to a cloud provider issue. Additional information is available on the cloud provider's status page: https://health.aws.com/health/status (opens in new tab)

Changes Rewindex caught on this incident

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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Rewindex captured a newer version 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: critical) posted by Databricks, started 2026-11-06 23:21 UTC, resolved after 2.8 h, 5 update(s); edited after publishing.

Title
ES-2342108
Vendor
Databricks
Date
URL
https://rewindex.com/company/databricks/incidents/6aee60df45f950041fd2fbf6

Databricks profileRecent Databricks incidentsAll outages on November 6, 2026Databricks in November 2026MarkdownJSON