CockroachDB Status · History · Incident #2314
RESOLVEDAdvanced cluster creation on AWS taking longer than expected
Major · Started Feb 2, 2026 · 4:56 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
CockroachDB Status · History · Incident #2314
RESOLVEDMajor · Started Feb 2, 2026 · 4:56 PM
Duration
2h 49m
Severity
Major
Detection lead
—
User reports
—
Summary
We have deployed and verified a fix. Advanced clusters should now create within normal time frames.
Started
Feb 2, 2026 · 4:56 PM
Resolved
Feb 2, 2026 · 7:46 PM
Duration
2h 49m
Severity
Major
Event timeline
Identified
Feb 2 · 4:56 PM CockroachDBWe have identified an issue that is causing Advanced cluster creation on AWS to take longer than usual. We are preparing a fix, and will update this status page with more information when we have an ETA for resolution.
Identified
Feb 2 · 5:57 PM CockroachDBWe are preparing a fix for deployment, which should restore AWS cluster creation times to normal levels. We will update the status page when the fix is deployed, or by 14:30 US/Eastern with more information.
Identified
Feb 2 · 7:31 PM CockroachDBWe are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern.
Resolved
Feb 2 · 7:46 PM CockroachDBWe have deployed and verified a fix. Advanced clusters should now create within normal time frames.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT