Changes / CockroachDB / Standard and Basic cluster creation on AWS delayed

CockroachDB: Critical incident: Standard and Basic cluster creation on AWS delayed

Summary

CockroachDB reported a critical incident affecting Basic and Standard clusters on AWS: cluster creation, some edits, and Cloud Console functions were disrupted; GCP operated normally. It lasted 6 h 15 min, from 2025-10-31 15:54 UTC to 2025-10-31 22:09 UTC. The vendor resolved the underlying issue, re-enabled creation on all clouds, and confirmed all cluster operations were normal.

Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 95%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Standard and Basic cluster creation on AWS delayed
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-31 15:54 UTC
AddedResolved time#5
Before: not present
After: 2025-10-31 22:09 UTC
AddedAffected components#6
Before: not present
After: CockroachDB Basic/Standard
AddedUpdateinvestigating#7
Before: not present
After: We are investigating errors that are causing delays in creation of Basic and Standard clusters on AWS. Basic and Standard cluster creation on GCP is operating normally at this time.
AddedUpdateinvestigating#8
Before: not present
After: We are investigating errors with Basic and Standard clusters on AWS. Cluster creation, certain cluster edit operations (such as adding a region), and certain CockroachDB Cloud Console functionality (such as listing databases or users) are also impacted. Basic and Standard clusters on GCP are operating normally at this time.
AddedUpdateidentified#9
Before: not present
After: We have identified the cause of cluster creation failures impacting Basic and Standard AWS clusters. As a precautionary measure, while we apply a fix, we have disabled all cluster creation in Cockroach Cloud. We will restore cluster creation when it is safe to do so. There is no SQL availability impact to any existing clusters. We will update here by 3:00 PM US/Eastern with more information.
AddedUpdateidentified#10
Before: not present
After: We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time.
AddedUpdateidentified#11
Before: not present
After: We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time.
AddedUpdatemonitoring#12
Before: not present
After: We have resolved the underlying issue that was preventing cluster creation and other cluster operations. We have re-enabled cluster creation on all clouds. We will monitor the situation to ensure that everything continues to operate normally.
AddedUpdateresolved#13
Before: not present
After: All cluster operations are working normally.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: Standard and Basic cluster creation on AWS delayed (this change)
CockroachDB reported a critical incident affecting Basic and Standard clusters on AWS: cluster creation, some edits, and Cloud Console functions were disrupted; GCP operated normally. It lasted 6 h 15 min, from 2025-10-31 15:54 UTC to 2025-10-31 22:09 UTC. The vendor resolved the underlying issue, re-enabled creation on all clouds, and confirmed all cluster operations were normal.
Major incident

All CockroachDB changes → · CockroachDB profile · Markdown · JSON