rewindex

ChangesDatabricksES-2342108

Databricks: Incident updated: ES-2342108

Incident updateNormal progress (rule, 100%)Changed status.databricks.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Databricks removed; blue is what they added. Muted text is unchanged context.

AddedUpdateidentified#1
Before: not present
After: 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 Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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 this record existed by then and has 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.

History of this incident

TodaySaturday, November 7Sat, Nov 7

3 incident changes

YesterdayFriday, November 6Fri, Nov 6

2 incident changes

Cite this

Incident updated: ES-2342108 on Databricks’s status page, changed 2026-11-07 00:43 UTC (change 3 of 5).

Title
Incident updated: ES-2342108
Vendor
Databricks
Date
URL
https://rewindex.com/change/r00415cf2873340

All Databricks changesDatabricks profileMarkdownJSON