CockroachDB: Modifying cluster topology to existing AWS clusters may get stuck
Timeline of updates
- resolved
This incident has been resolved. If you are still experiencing problems with modifying AWS clusters please reach out to support.
From CockroachDB’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.cockroachlabs.cloud (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by CockroachDB, started 2022-10-15 03:14 UTC, resolved after 31 h, 1 update(s).
- Title
- Modifying cluster topology to existing AWS clusters may get stuck
- Vendor
- CockroachDB
- Date
- URL
- https://rewindex.com/company/cockroachdb/incidents/cn8wv7h95l55
CockroachDB profileRecent CockroachDB incidentsAll outages on October 15, 2022CockroachDB in October 2022MarkdownJSON