Cockroach Labs Outage History

Cockroach Labs is up right now

Cockroach Labs had 15 outages in the last 2 years totaling 328h 9m of downtime — averaging 0.6 incidents per month.

There were 15 Cockroach Labs outages since June 27, 2025 totaling 328h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cockroachlabs.cloud

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: CockroachDB Cloud Console
Timeline · 2 updates
  1. 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.

  2. 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
  1. 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.

  2. 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.

  3. 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.

  4. 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: CockroachDB Cloud Console
Timeline · 2 updates
  1. 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.

  2. 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 →

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
  1. investigating Feb 09, 2026, 03:04 AM UTC

    We are investigating connectivity issues to Standard and Basic clusters on AWS.

  2. 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.

  3. 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
  1. 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.

  2. 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.

  3. 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.

  4. 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
  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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
  1. 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.

  2. 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.

  3. 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
  1. 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.

  2. 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.

  3. 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 →

Major September 24, 2025

Google Kubernetes incident impacting cluster operations in GCP.

Detected by Pingoru
Sep 24, 2025, 12:31 PM UTC
Resolved
Sep 24, 2025, 04:00 PM UTC
Duration
3h 28m
Affected: CockroachDB Advanced
Timeline · 2 updates
  1. identified Sep 24, 2025, 12:31 PM UTC

    We are currently experiencing an incident impacting certain cluster operations on Google Cloud Platform due to an known ongoing Google Kubernetes-related issue. Customers may encounter errors when creating or editing clusters. Our engineering teams are actively monitoring the situation and communicating with Google regarding resolution.

  2. resolved Sep 24, 2025, 04:00 PM UTC

    Google has reported the issue has been resolved and we've verified cluster operations are functional.

Read the full incident report →

Major July 29, 2025

SQL availability impacted across multiple Serverless clusters.

Detected by Pingoru
Jul 29, 2025, 11:08 PM UTC
Resolved
Jul 29, 2025, 11:35 PM UTC
Duration
26m
Affected: CockroachDB Basic/Standard
Timeline · 3 updates
  1. investigating Jul 29, 2025, 11:08 PM UTC

    We are observing an incident impacting SQL availability across multiple Serverless clusters. We are currently investigating the issue.

  2. monitoring Jul 29, 2025, 11:17 PM UTC

    Correction from the original status update. This issue appears to have been isolated to cluster crl-prod-6rw. We have identified the cause, mitigated and confirmed that cluster availability has returned. We are currently completing additional validations.

  3. resolved Jul 29, 2025, 11:35 PM UTC

    We have confirmed resolution of the incident impacting SQL availability for the affected cluster. SQL availability is restored and the associated cluster is now healthy.

Read the full incident report →

Minor July 21, 2025

Dependent Service incident intermittently impacting CockroachCloud Operations

Detected by Pingoru
Jul 21, 2025, 09:39 PM UTC
Resolved
Jul 22, 2025, 04:22 AM UTC
Duration
6h 42m
Affected: CockroachDB Advanced
Timeline · 2 updates
  1. identified Jul 21, 2025, 09:39 PM UTC

    We are aware of an ongoing Incident with dependent service "Let's Encrypt": https://letsencrypt.status.io/, which may impact cluster creation and add region operations for CockroachDB Cloud Advanced clusters. We will update this status page with more information as it becomes available.

  2. resolved Jul 22, 2025, 04:22 AM UTC

    LetsEncrypt has indicated the issue has been mitigated. We have validated cluster creation behaviour is now returning to normal.

Read the full incident report →

Major July 3, 2025

Cluster operations impaired

Detected by Pingoru
Jul 03, 2025, 04:58 PM UTC
Resolved
Jul 03, 2025, 05:39 PM UTC
Duration
41m
Affected: CockroachDB Basic/StandardCockroachDB Advanced
Timeline · 2 updates
  1. investigating Jul 03, 2025, 04:58 PM UTC

    We are investigating an issue that may prevent or delay cluster operations from succeeding.

  2. resolved Jul 03, 2025, 05:39 PM UTC

    We have corrected a misconfiguration which was preventing cluster operations from succeeding. We are monitoring the success of cluster operations already in progress and new operations.

Read the full incident report →

Major July 2, 2025

Cluster operations taking longer than expected

Detected by Pingoru
Jul 02, 2025, 05:42 PM UTC
Resolved
Jul 02, 2025, 08:46 PM UTC
Duration
3h 3m
Timeline · 4 updates
  1. investigating Jul 02, 2025, 05:42 PM UTC

    We are investigating cluster operations, including creating or editing clusters, that are taking longer than usual.

  2. identified Jul 02, 2025, 06:50 PM UTC

    We have identified the issue preventing cluster operations from proceeding, and we see that operations are moving forward. We will next update this incident by 16:00 EDT.

  3. monitoring Jul 02, 2025, 07:32 PM UTC

    We continue to see cluster operations succeeding, and will actively monitor to ensure the issue does not reoccur.

  4. resolved Jul 02, 2025, 08:46 PM UTC

    All cluster operations are succeeding normally at this time.

Read the full incident report →

Major June 27, 2025

Issue impacting Basic and Standard tier cluster creation in AWS.

Detected by Pingoru
Jun 27, 2025, 10:29 PM UTC
Resolved
Jun 27, 2025, 10:36 PM UTC
Duration
6m
Affected: CockroachDB Basic/Standard
Timeline · 2 updates
  1. identified Jun 27, 2025, 10:29 PM UTC

    We have identified an issue impacting Basic and Standard tier cluster creation in AWS. We have conducted an initial investigation and actively working to resolve the issue.

  2. resolved Jun 27, 2025, 10:36 PM UTC

    We have identified and rolled out a fix for the issue impacting cluster creation in AWS. This incident is now resolved.

Read the full incident report →