Cockroach Labs Outage History

Cockroach Labs had 14 outages in the last 2 years totaling 362h 52m of downtime — averaging 0.6 incidents per month.

There were 14 Cockroach Labs outages since October 20, 2025 totaling 362h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cockroachlabs.cloud

Minor October 6, 2026

Stock out issues in GCP us-central1

Detected by Pingoru: Oct 06, 2026, 09:21 PM UTC
Resolved: Oct 07, 2026, 07:33 PM UTC
Duration: 22h 11m

Affected: CockroachDB AdvancedContinuum Mission Critical

Timeline · 3 updates

investigating Oct 06, 2026, 09:21 PM UTC

We are currently monitoring stock out (lack of capacity) issues for instances in the GCP us-central1 region. If possible, customers are advised to use a different region when creating new clusters. It is expected that cluster creations and edits will eventually succeed as capacity becomes available. GCP has not provided a timeline for when these capacity issues will be resolved, but we will continue to monitor and update this page as we learn more.
monitoring Oct 06, 2026, 09:22 PM UTC

A fix has been implemented and we are monitoring the results.
resolved Oct 07, 2026, 07:33 PM UTC

We are continuing to monitor this issue; however Google can not provide an ETA as to when it will be resolved. We will continue to work with them to obtain the needed capacity. Customers are still advised to choose another region when spinning up new clusters to circumvent the capacity problems observed with us-central1.

Read the full incident report →

Major September 17, 2026

Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).

Detected by Pingoru: Sep 17, 2026, 07:08 PM UTC
Resolved: Sep 17, 2026, 08:39 PM UTC
Duration: 1h 30m

Affected: CockroachDB Basic/Standard

Timeline · 2 updates

investigating Sep 17, 2026, 07:08 PM UTC

CockroachDB Cloud (Basic) clusters hosted in GCP South America (São Paulo / southamerica-east1) are currently experiencing network connectivity issues. We are investigating and will provide an update shortly
resolved Sep 17, 2026, 08:39 PM UTC

This incident has been resolved. CockroachDB Cloud (Basic) clusters hosted in GCP South America (São Paulo / southamerica-east1) experienced network connectivity issues that have now been fully restored. Connectivity has returned to normal and all affected clusters are operating as expected. We apologize for any disruption this may have caused. If you continue to experience any issues, please contact support.

Read the full incident report →

Major September 1, 2026

Cloud Latency, Delays, Connection Issues

Detected by Pingoru: Sep 01, 2026, 03:36 PM UTC
Resolved: Sep 01, 2026, 07:45 PM UTC
Duration: 4h 8m

Affected: CockroachDB Basic/Standard

Timeline · 6 updates

investigating Sep 01, 2026, 03:36 PM UTC

Google Cloud is experiencing networking outages which is affecting Cockroach Cloud customers. Cockroach Cloud customers may experience heightened latency, delays, or connection issues. Our teams are aware and fully engaged on this incident. Known current Impacts: us-central-1, asia-east-1
investigating Sep 01, 2026, 03:39 PM UTC

Google Cloud is experiencing networking outages which is affecting Cockroach Cloud customers. Cockroach Cloud customers may experience heightened latency, delays, or connection issues. Our teams are aware and fully engaged on this incident. Known current Impacts: us-central-1, asia-east-1
investigating Sep 01, 2026, 04:04 PM UTC

We are still monitoring the situation, seeing some improvement over the last 15 minutes, but not fully resolved. Known current Impacts: us-central1, asia-east1, europe-west4-b
monitoring Sep 01, 2026, 04:13 PM UTC

Google is now reporting that us-central1 and asia-east1 are both resolved, however europe-west4-b is still actively impacted. Our internal teams are confirming no further errors in the last 15 minutes for us-central1 and asia-east1 regions. Known current Impacts: europe-west4-b
monitoring Sep 01, 2026, 04:37 PM UTC

We are learning that Google is reporting us-central1-b is also impacted and experiencing degradation. Following network-level mitigation efforts, the underlying network infrastructure has fully recovered. Google Product engineering teams across Cloud are currently validating the recovery status of individual services.
resolved Sep 01, 2026, 07:45 PM UTC

Google impacts are now reported as fully resolved. Internal teams have confirmed this report. All services are restored. Should you need further help, please reach out and file a ticket with Support.

Read the full incident report →

Major August 4, 2026

Cluster connectivity and execution issues

Detected by Pingoru: Aug 04, 2026, 11:46 PM UTC
Resolved: Aug 05, 2026, 07:50 PM UTC
Duration: 20h 3m

Affected: CockroachDB Basic/Standard

Timeline · 5 updates

investigating Aug 04, 2026, 11:46 PM UTC

We are investigating an issue affecting a subset of Free Tier clusters in eu-west-1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation.
investigating Aug 04, 2026, 11:47 PM UTC

We are investigating an issue affecting a subset of Basic clusters in eu-west1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation.
investigating Aug 04, 2026, 11:52 PM UTC

We are investigating an issue affecting a subset of Basic and Standard clusters in eu-west1, where some clusters may be unable to connect or execute queries. Teams have been notified and are actively working on mitigation.
monitoring Aug 05, 2026, 03:55 AM UTC

Teams have mitigated the immediate active impact, but work continues to ensure the problem does not recur and to fully understand the root cause. For now we will continue to monitor the situation. If you continue to experience impacts, please reach out to Support.
resolved Aug 05, 2026, 07:50 PM UTC

Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.

Read the full incident report →

Major July 12, 2026

Cluster Creation Failure

Detected by Pingoru: Jul 12, 2026, 08:08 PM UTC
Resolved: Jul 12, 2026, 09:24 PM UTC
Duration: 1h 16m

Affected: CockroachDB Basic/Standard

Timeline · 2 updates

investigating Jul 12, 2026, 08:08 PM UTC

We are currently aware of and investigating a cluster creation failure. Teams are engaged and actively working to mitigate as quickly as possible.
resolved Jul 12, 2026, 09:24 PM UTC

The cluster creation issue has been restored. Issue is resolved.

Read the full incident report →

Minor June 9, 2026

Unable to accept invites

Detected by Pingoru: Jun 09, 2026, 09:26 PM UTC
Resolved: Jun 09, 2026, 10:02 PM UTC
Duration: 36m

Affected: Cloud Console

Timeline · 2 updates

identified Jun 09, 2026, 09:26 PM UTC

We have identified a minor issue affecting Cloud customers who are unable to accept invites, preventing them from inviting new users to their organizations. Internal teams are aware and a fix is in flight. ETA: 30min - 1hour. We will provide the next update at the top of the hour or prior if the fix is deployed before that time.
resolved Jun 09, 2026, 10:02 PM UTC

Fix deployment is complete, tested and verified.

Read the full incident report →

Major May 8, 2026

Degraded performance in one AWS us-east-1 availability zone

Detected by Pingoru: May 08, 2026, 02:13 AM UTC
Resolved: May 08, 2026, 09:53 PM UTC
Duration: 19h 40m

Affected: CockroachDB Advanced

Timeline · 4 updates

monitoring May 08, 2026, 02:13 AM UTC

AWS is experiencing elevated error rates and degraded performance in a single availability zone in the us-east-1 region. CockroachDB clusters in us-east-1 remain available, and we are monitoring the situation and taking corrective action as appropriate to ensure SQL availability of CockroachDB clusters in this region.
monitoring May 08, 2026, 03:24 AM UTC

AWS's latest status update reports that they are continuing to work on the situation, and progress is slow. AWS has advised a next update time at 05:00 UTC. We continue to monitor the situation and take appropriate action to ensure uptime and availability for Cockroach DB clusters. We'll next update by about 05:00 UTC when we learn more from AWS.
monitoring May 08, 2026, 08:25 AM UTC

AWS reports continued progress towards resolving the issue in the US-EAST-1 Region and is working towards full recovery. Affected services may continue to experience elevated error rates and latencies until recovery is complete. We continue to monitor the situation and take appropriate action to ensure uptime and availability for CockroachDB clusters. We'll provide another update as we learn more from AWS.
resolved May 08, 2026, 09:53 PM UTC

All CockroachDB clusters in the affected AWS availability zone have been restored to a fully operational state. We will continue to monitor the upstream incident from AWS, but do not expect any impact to CockroachDB clusters.

Read the full incident report →

Major March 18, 2026

Cloud Console Social Login Auth Unavailable

Detected by Pingoru: Mar 18, 2026, 03:23 PM UTC
Resolved: Mar 18, 2026, 04:02 PM UTC
Duration: 39m

Affected: Cloud Console

Timeline · 2 updates

investigating Mar 18, 2026, 03:23 PM UTC

Social logins for customers using personal/non-SSO Microsoft accounts is currently unavailable. Our teams are aware and currently investigating.
resolved Mar 18, 2026, 04:02 PM UTC

Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.

Read the full incident report →

Minor March 1, 2026

Cluster unavailability and degraded cluster operations in AWS me-central...

Detected by Pingoru: Mar 01, 2026, 03:11 PM UTC
Resolved: Mar 11, 2026, 07:51 PM UTC
Duration: 10d 4h

Affected: CockroachDB Advanced

Timeline · 8 updates

Read the full incident report →

Major February 9, 2026

Connectivity issues to Standard and Basic clusters on AWS

Detected by Pingoru: Feb 09, 2026, 03:04 AM UTC
Resolved: Feb 09, 2026, 03:20 PM UTC
Duration: 12h 16m

Affected: CockroachDB Basic/Standard

Timeline · 3 updates

investigating Feb 09, 2026, 03:04 AM UTC

We are investigating connectivity issues to Standard and Basic clusters on AWS.
monitoring Feb 09, 2026, 04:15 AM UTC

We have resolved an internal misconfiguration, and see that Standard and Basic clusters are functioning normally again. We will continue to monitor to ensure that the error does not recur.
resolved Feb 09, 2026, 03:20 PM UTC

Standard and Basic clusters continue to function normally.

Read the full incident report →

Major February 2, 2026

Advanced cluster creation on AWS taking longer than expected

Detected by Pingoru: Feb 02, 2026, 04:56 PM UTC
Resolved: Feb 02, 2026, 07:46 PM UTC
Duration: 2h 49m

Affected: CockroachDB Advanced

Timeline · 4 updates

identified Feb 02, 2026, 04:56 PM UTC

We 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 02, 2026, 05:57 PM UTC

We 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 02, 2026, 07:31 PM UTC

We are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern.
resolved Feb 02, 2026, 07:46 PM UTC

We have deployed and verified a fix. Advanced clusters should now create within normal time frames.

Read the full incident report →

Critical October 31, 2025

Standard and Basic cluster creation on AWS delayed

Detected by Pingoru: Oct 31, 2025, 03:54 PM UTC
Resolved: Oct 31, 2025, 10:09 PM UTC
Duration: 6h 15m

Affected: CockroachDB Basic/Standard

Timeline · 7 updates

investigating Oct 31, 2025, 03:54 PM UTC

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.
investigating Oct 31, 2025, 04:21 PM UTC

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.
identified Oct 31, 2025, 06:22 PM UTC

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.
identified Oct 31, 2025, 06:59 PM UTC

We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time.
identified Oct 31, 2025, 07:58 PM UTC

We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time.
monitoring Oct 31, 2025, 08:18 PM UTC

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.
resolved Oct 31, 2025, 10:09 PM UTC

All cluster operations are working normally.

Read the full incident report →

Major October 30, 2025

Advanced Cluster Creation Delayed

Detected by Pingoru: Oct 30, 2025, 02:50 PM UTC
Resolved: Oct 30, 2025, 04:05 PM UTC
Duration: 1h 15m

Affected: CockroachDB Advanced

Timeline · 3 updates

investigating Oct 30, 2025, 02:50 PM UTC

We are investigating errors that cause creation for Advanced clusters to take longer than usual. Standard and Basic cluster creation is operating normally.
monitoring Oct 30, 2025, 03:25 PM UTC

We have applied a mitigation and observe that cluster creations are proceeding again. We will monitor all impacted cluster creations to ensure they succeed.
resolved Oct 30, 2025, 04:05 PM UTC

Cluster creation is operating normally, and all delayed clusters have finished creation.

Read the full incident report →

Major October 20, 2025

AWS us-east-1 outage impacting cluster operations and backups

Detected by Pingoru: Oct 20, 2025, 01:28 PM UTC
Resolved: Oct 21, 2025, 02:56 PM UTC
Duration: 1d 1h

Timeline · 3 updates

identified Oct 20, 2025, 01:28 PM UTC

We’re currently impacted by an ongoing AWS outage in the us-east-1 region. Customers may experience failures or delays when creating new clusters, adding nodes, or running backups in this region. Existing clusters remain operational, but backup operations may be delayed or fail intermittently. We’re continuing to monitor AWS recovery efforts and will provide updates as more information becomes available.
monitoring Oct 20, 2025, 10:52 PM UTC

AWS has resolved the underlying outage in the us-east-1 region, and we’re seeing recovery across CockroachDB Cloud operations. Cluster creation, scaling, and backups are now succeeding again. We’re continuing to monitor for full stability before marking this incident as resolved.
resolved Oct 21, 2025, 02:56 PM UTC

The earlier AWS outage in the us-east-1 region has been fully resolved. All CockroachDB Cloud operations, including cluster creation, scaling, and backups, are functioning normally again. We’ve verified recovery across affected systems and customer clusters, and normal operations have resumed.

Read the full incident report →