Databricks: Incident updated: ES-2375763
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.
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.
How the archive is checked, and what it cannot prove.
Rewindex captured this after the last checkpoint; the next run () commits it.
History of this incident
TodayFriday, November 20Fri, Nov 20
1 rewrite, 4 incident changes
- Incident updateIncident
Incident updateES-2375763, ES-2375817
- Normal progressIncident
Incident updateES-2375763, ES-2375817
- Wording onlyEdited by the vendor
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.
- Normal progressIncident
Incident updateES-2375763this change
- DegradationMajor incident
Cite this
Incident updated: ES-2375763 on Databricks’s status page, changed 2026-11-20 09:43 UTC (change 2 of 5).
- Title
- Incident updated: ES-2375763
- Vendor
- Databricks
- Date
- URL
- https://rewindex.com/change/r096c03a533f2cd