CockroachDB change history

Connection attempts failed for multiple CockroachDB Cloud (Basic) tenants in GCP South America (São Paulo / southamerica-east1), preventing affected customers from connecting to clusters. CockroachDB rated the incident major; it started at 2026-09-17 19:08 UTC and was resolved at 2026-09-17 20:39 UTC, lasting 1 h 30 min. Connectivity was fully restored, with all affected clusters operating as expected.

CockroachDB Basic/Standard experienced major latency, delays, and connection issues affecting us-central-1, asia-east-1 (later listed as us-central1, asia-east1), europe-west4-b, and us-central1-b from 2026-09-01 15:36 UTC to 2026-09-01 19:45 UTC (4 h 8 min). CockroachDB attributed the disruption to Google Cloud networking outages; network-level mitigation restored infrastructure, and all services were confirmed restored.

CockroachDB reported a major outage preventing some Basic and Standard clusters in eu-west1 from connecting or executing queries. It ran from 2026-08-04 23:46 UTC to 2026-08-05 19:50 UTC (20 h 3 min). Immediate impact was mitigated by 2026-08-05 03:55 UTC; resolution followed monitoring confirming stability, with no root cause stated.

CockroachDB reported a major cluster creation failure affecting CockroachDB Basic/Standard starting at 2026-07-12 20:08 UTC. Cluster creation was restored at 2026-07-12 21:24 UTC, resolving the incident after 1 h 16 min.

CockroachDB Advanced reported a major degradation linked to elevated AWS error rates and degraded performance in one us-east-1 availability zone; clusters remained available. The incident ran from 2026-05-08 02:13 UTC to 2026-05-08 21:53 UTC (19 h 40 min), when all clusters in the affected zone were restored to a fully operational state.

CockroachDB reported a major Cloud Console outage affecting social login for customers using personal/non-SSO Microsoft accounts. It started at 2026-03-18 15:23 UTC and was resolved at 2026-03-18 16:02 UTC, lasting 39 min; Microsoft social login was restored.

CockroachDB reported a major incident affecting connectivity to Standard and Basic clusters on AWS, starting 2026-02-09 03:04 UTC and resolved at 2026-02-09 15:20 UTC (12 h 16 min). The vendor resolved an internal misconfiguration and reported normal cluster operation at 04:15 UTC, then monitored until resolution.

CockroachDB Advanced cluster creation on AWS took longer than usual in a major-impact incident starting 2026-02-02 16:56 UTC and resolved at 2026-02-02 19:46 UTC, lasting 2 h 49 min. CockroachDB deployed and verified a fix, restoring normal cluster creation times.

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.

CockroachDB reported a major degradation delaying Advanced cluster creation from 2025-10-30 14:50 UTC to 2025-10-30 16:05 UTC, lasting 1 h 15 min. Standard and Basic cluster creation remained normal. A mitigation restored creation, and all delayed clusters finished by resolution.

CockroachDB reported a major AWS us-east-1 outage causing failures or delays in cluster creation, node additions, and backups; existing clusters remained operational. The incident started at 2025-10-20 13:28 UTC and was resolved at 2025-10-21 14:56 UTC, lasting 25 h 27 min. AWS resolved the underlying outage, and CockroachDB verified normal operations had resumed.

CockroachDB Advanced had a major incident affecting cluster operations on Google Cloud Platform: customers could encounter errors creating or editing clusters due to a Google Kubernetes-related issue. It started at 2025-09-24 12:31 UTC and was resolved at 2025-09-24 16:00 UTC, lasting 3 h 28 min; Google reported resolution, and CockroachDB verified cluster operations were functional.

CockroachDB reported a major SQL availability incident affecting CockroachDB Basic/Standard, initially described as spanning multiple Serverless clusters but later isolated to crl-prod-6rw. It started at 2025-07-29 23:08 UTC and was resolved at 2025-07-29 23:35 UTC; the computed duration was 26 min. CockroachDB reported mitigation and restored availability but did not disclose the cause.

CockroachDB reported a major incident affecting cluster operations on CockroachDB Advanced and CockroachDB Basic/Standard, potentially preventing or delaying operations. It lasted 41 min, from 2025-07-03 16:58 UTC to 2025-07-03 17:39 UTC; CockroachDB corrected a misconfiguration and monitored in-progress and new operations.

CockroachDB reported a major degradation affecting cluster operations, including creating or editing clusters, on CockroachDB Advanced and CockroachDB Basic/Standard. It started at 2025-07-02 17:42 UTC and resolved at 2025-07-02 20:46 UTC, lasting 3 h 3 min; the vendor confirmed all cluster operations were succeeding normally.

CockroachDB reported a major incident affecting Basic and Standard tier cluster creation in AWS, starting at 2025-06-27 22:29 UTC and resolved at 2025-06-27 22:36 UTC; the computed duration was 6 min. The vendor rolled out a fix, restoring affected cluster creation.

CockroachDB reported a major outage affecting Cloud Advanced cluster creation and edits in GCP, plus potentially backups to Google Cloud Storage. It started at 2025-06-12 18:22 UTC and was resolved at 2025-06-12 21:31 UTC; the recorded duration was 3 h 8 min. Google Cloud API errors were cited; Google reported mitigations applied and services recovering.

A major outage prevented some metrics pages from loading in Cockroach Cloud Console for Basic and Standard tier clusters; metrics data collection was unaffected. The incident ran from 2025-06-04 19:10 UTC to 2025-06-04 21:35 UTC (2 h 25 min). The underlying service recovered, and the service provider confirmed the underlying issue was addressed.

CockroachDB reported a major outage affecting Basic/Standard clusters in AWS eu-west-1, eu-west-2, and eu-central-1 due to an AWS network blip. The incident record starts at 2025-06-01 07:29 UTC with a computed duration of 0 min; its update reports unavailability June 1, 19:29–19:35 UTC and automatic resolution at 19:35 UTC.

CockroachDB reported a major incident with elevated error rates on isolated Standard and Basic clusters from 2024-11-19 16:48 UTC to 2024-11-19 18:36 UTC, lasting 1 h 48 min. Engineering reported identifying and resolving the root cause, without specifying it, and confirmed resolution for all affected clusters.

CockroachDB reported a major incident involving increased restore errors in Serverless clusters, affecting CockroachDB Basic/Standard and CockroachDB Serverless. It started at 2024-08-09 21:37 UTC and was resolved at 2024-08-09 22:33 UTC, lasting 56 min. CockroachDB corrected a misconfiguration causing the errors and applied the fix to all serverless clusters.

CockroachDB reported a major outage affecting CockroachDB Advanced and CockroachDB Dedicated clusters with nodes in Azure Central US, which may have been unavailable starting 2024-07-18 23:20 UTC. The incident lasted 15 h 49 min and was resolved at 2024-07-19 15:09 UTC, after CockroachDB verified all Azure clusters were operational and backup jobs had completed.

CockroachDB reported a major outage preventing Dedicated cluster creation and edits and potentially affecting Cloud Console pages connecting to Serverless and Dedicated clusters; SQL connections worked normally. Starting 2024-07-18 01:56 UTC, it lasted 12 h 49 min and was resolved at 2024-07-18 14:45 UTC after the vendor addressed an unspecified underlying cause.

A major Google Cloud Platform networking outage affected a select number of GCP Cockroach Cloud clusters from 2024-05-17 00:42 UTC to 2024-05-17 02:01 UTC, lasting 1 h 19 min. Cockroach Labs monitored the issue and reported that it was resolved.

CockroachDB reported a major incident affecting AWS cluster operations, including creation and modification, starting 2023-12-22 02:01 UTC and lasting 24 h 45 min. Impact later narrowed to vertical scaling failures and delays. Resolved at 2023-12-23 02:46 UTC, the vendor stated all cluster operations should succeed and monitoring continued.

CockroachDB reported a major outage that made Serverless clusters in GCP europe-west1 inaccessible. The recorded start was 2023-11-21 14:14 UTC, but the resolved timestamp was earlier, at 2023-11-21 12:00 UTC; duration is unknown. No cause or fix was stated.

CockroachDB reported a major Cloud Console authentication outage from 2023-10-30 20:25 UTC to 2023-10-30 20:36 UTC, lasting 11 min. An upstream provider outage caused all authentication methods except username and password to fail; existing sessions continued until timeout. The provider incident was resolved and SSO authentication restored.

CockroachDB reported major connectivity issues isolated to its `Europe-West-1` Serverless cluster in GCP, starting 2023-09-08 15:47 UTC. A fix was implemented by 09-08 16:09 UTC, and the incident was resolved at 2023-09-08 17:01 UTC; the reported duration was 1 h 13 min.

CockroachDB Serverless clusters experienced intermittent connection failures in AWS us-east-1, with major impact, starting 2023-08-03 01:12 UTC. The incident lasted 2 h 40 min and was resolved at 2023-08-03 03:53 UTC after engineers deployed a fix.

CockroachDB reported a major Serverless degradation in AWS eu-west-1 and AWS ap-south-1: some clusters remained throttled after resource limits were increased. It started at 2023-08-02 16:05 UTC and was resolved at 2023-08-02 19:44 UTC, lasting 3 h 39 min; previously throttled clusters now reflect resource-limit changes.

CockroachDB reported a major outage affecting connections to Serverless clusters on the GCP Multi-Region Serverless Public Preview host; other serverless clusters remained fully functional. The incident started at 2023-07-25 21:55 UTC and was resolved at 2023-07-25 23:07 UTC, lasting 1 h 12 min; no cause or specific fix was stated.