CockroachDB: Cluster setting update caused a brief latency increase and availability impact on a single Serverless cluster.
Timeline of updates
- resolved
A cluster setting update resulted in higher than expected CPU activity, which caused increased latency and caused unavailability for a single Serverless cluster. The setting was rolled back to prevent further impact. The issue has been resolved. There should be no further availability impact.
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.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2707b6d905fe992c…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by CockroachDB, started 2024-06-17 14:48 UTC, resolved after 0 min, 1 update(s).
- Title
- Cluster setting update caused a brief latency increase and availability impact on a single Serverless cluster.
- Vendor
- CockroachDB
- Date
- URL
- https://rewindex.com/company/cockroachdb/incidents/rc20lvqbycp6
CockroachDB profileRecent CockroachDB incidentsAll outages on June 17, 2024CockroachDB in June 2024MarkdownJSON