Cockroach Labs Outage History

Started Oct 20, 2026, 07:53 AM UTC· resolved Oct 20, 2026, 02:53 PM UTC

1. investigating Oct 20, 2026, 07:53 AM UTC

   GCP europe-west2-b and availability zone is currently experiencing issues. We will continue to monitor this situation and update status once we have more information.

2. identified Oct 20, 2026, 11:48 AM UTC

   GCP has mitigated the power event that caused this disruption in the europe-west2 region and is working on mitigating impacted services. We will update once we have confirmation of mitigation.

3. monitoring Oct 20, 2026, 12:57 PM UTC

   GCP has mitigated the power event that caused this disruption in the europe-west2 region and most GCP services have recovered. We will continue to track and ensure impacted CRL services return to normal operation before resolving.

4. resolved Oct 20, 2026, 02:53 PM UTC

   GCP has mitigated the power event that caused this disruption in the europe-west2 region. All GCP and CRL services has returned to normal operation. No further action is required.

Read the full incident report →

Started Oct 06, 2026, 09:21 PM UTC· resolved Oct 07, 2026, 07:33 PM UTC

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

2. monitoring Oct 06, 2026, 09:22 PM UTC

   A fix has been implemented and we are monitoring the results.

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

Started Sep 17, 2026, 07:08 PM UTC· resolved Sep 17, 2026, 08:39 PM UTC

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

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

Started Sep 01, 2026, 03:36 PM UTC· resolved Sep 01, 2026, 07:45 PM UTC

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

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

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

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

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

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

Started Aug 04, 2026, 11:46 PM UTC· resolved Aug 05, 2026, 07:50 PM UTC

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

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

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

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

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

Started Jul 12, 2026, 08:08 PM UTC· resolved Jul 12, 2026, 09:24 PM UTC

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

2. resolved Jul 12, 2026, 09:24 PM UTC

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

Read the full incident report →

Started Jun 09, 2026, 09:26 PM UTC· resolved Jun 09, 2026, 10:02 PM UTC

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 →

Started May 08, 2026, 02:13 AM UTC· resolved May 08, 2026, 09:53 PM UTC

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 →

Started Mar 18, 2026, 03:23 PM UTC· resolved Mar 18, 2026, 04:02 PM UTC

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 →

Started Mar 01, 2026, 03:11 PM UTC· resolved Mar 11, 2026, 07:51 PM UTC

1. monitoring Mar 01, 2026, 03:11 PM UTC

   A power outage at an AWS facility in the me-central-1 (Mid-East) region may cause failures or slower than usual progress on cluster operations. AWS is aware of the issue and is working to restore power. We are monitoring the situation, and will provide updates as we receive them from AWS.

2. monitoring Mar 01, 2026, 08:43 PM UTC

   Current conflict in the region has led to objects impacting the AWS data center creating a fire earlier today. Power was shut down to prevent further damage. AWS is working on multiple mitigation paths to restore services as quickly as possible. We will provide the next update by 4PM PST or sooner if we have more to share.

3. monitoring Mar 01, 2026, 11:09 PM UTC

   AWS is reporting positive signs of recovery at this time, but are still working on multiple mitigation paths to fully restore services. We continue to keep a close eye on the situation and will provide another update by 6PM PST, or sooner if we have additional information to share.

4. monitoring Mar 02, 2026, 01:51 AM UTC

   AWS is reporting significant signs of recovery for specific APIs and requests, but several still remain to be mitigated and will likely take several hours more to complete, if not into tomorrow. Our teams have begun testing with this update but have reported we are still impacted at this time. We will continue to monitor the situation closely and will provide one more update this evening by 7PM PST, or sooner if we have additional information to share.

5. monitoring Mar 02, 2026, 02:47 AM UTC

   AWS continues to work on mitigation efforts, including stabilizing impacted APIs and implementing interim workarounds. Our teams are actively reviewing and validating these mitigations; however, this effort will continue into tomorrow. We will provide our next update at 7:00 AM PST, or sooner if additional information becomes available.

6. monitoring Mar 02, 2026, 09:01 AM UTC

   me-central-1 region is impacted more with two AZs out and the clusters in that region are unavailable. In addition to this, me-south-1 region is also experiencing an AZ outage, which causes degraded performance of clusters in me-south-1. We are closely tracking AWS's status. Impacted customers can track AWS status here https://health.aws.amazon.com/health/status

7. monitoring Mar 02, 2026, 05:50 PM UTC

   AWS me-central-1 region is impacted with two AZs out. Clusters in that region are currently unavailable. AWS me-south-1 region is also experiencing a single AZ outage, which causes degraded performance of clusters in that region. While no impact has been observed on GCP or Azure in those regions, customers with single-region deployments are advised to have their disaster recovery plans ready should the need to restore from a backup to another region be required. We are closely tracking AWS's status. Impacted customers can track AWS status here https://health.aws.amazon.com/health/status.

8. resolved Mar 11, 2026, 07:51 PM UTC

   Beginning March 1, 2026, a power outage caused by physical damage to AWS infrastructure affected multiple Availability Zones in the AWS me-central-1 (UAE) region, resulting in the unavailability of CockroachDB Cloud clusters in that region. A single Availability Zone in me-south-1 was also impacted, causing degraded performance for clusters in that region. While AWS has not yet fully restored power to all affected Availability Zones, Cockroach Labs has directly engaged all customers impacted by this incident, providing resolution guidance and hands-on remediation assistance, including cross-region data restoration where applicable. As remediation steps have been completed or provided to all directly impacted customers, we are resolving this incident from Cockroach Labs' perspective. Cluster creation in the affected regions remains restricted pending full AWS recovery. Customers with outstanding questions or concerns are encouraged to contact Cockroach Labs Support.

Read the full incident report →

Started Feb 09, 2026, 03:04 AM UTC· resolved Feb 09, 2026, 03:20 PM UTC

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 →

Started Feb 02, 2026, 04:56 PM UTC· resolved Feb 02, 2026, 07:46 PM UTC

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 →

Started Oct 31, 2025, 03:54 PM UTC· resolved Oct 31, 2025, 10:09 PM UTC

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 →

Started Oct 30, 2025, 02:50 PM UTC· resolved Oct 30, 2025, 04:05 PM UTC

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 →

Started Oct 20, 2025, 01:28 PM UTC· resolved Oct 21, 2025, 02:56 PM UTC

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 →

Started Sep 24, 2025, 12:31 PM UTC· resolved Sep 24, 2025, 04:00 PM UTC

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 →

Started Jul 29, 2025, 11:08 PM UTC· resolved Jul 29, 2025, 11:35 PM UTC

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 →

Started Jul 21, 2025, 09:39 PM UTC· resolved Jul 22, 2025, 04:22 AM UTC

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 →

Started Jul 03, 2025, 04:58 PM UTC· resolved Jul 03, 2025, 05:39 PM UTC

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 →

Started Jul 02, 2025, 05:42 PM UTC· resolved Jul 02, 2025, 08:46 PM UTC

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 →

Started Jun 27, 2025, 10:29 PM UTC· resolved Jun 27, 2025, 10:36 PM UTC

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 →

Started Jun 12, 2025, 06:22 PM UTC· resolved Jun 12, 2025, 09:31 PM UTC

1. identified Jun 12, 2025, 06:22 PM UTC

   We are aware of errors in the Google Cloud API which may impact cluster creation and edit operations for CockroachDB Cloud Advanced clusters in GCP. We will update this status page with more information as it becomes available.

2. identified Jun 12, 2025, 07:08 PM UTC

   In addition to cluster operations, backups to Google Cloud Storage, including managed backups from CockroachDB Cloud clusters on GCP, may be impacted.

3. monitoring Jun 12, 2025, 07:54 PM UTC

   Google has updated their public status page to indicate the underlying issue is resolved, and individual Google Cloud services are in the process of restoring full service. We are continuing to monitor the issue and impact to CockroachDB Cloud.

4. resolved Jun 12, 2025, 09:31 PM UTC

   Google has reported that mitigations have been applied and services are now recovering.

Read the full incident report →

Started Jun 04, 2025, 07:10 PM UTC· resolved Jun 04, 2025, 09:35 PM UTC

1. investigating Jun 04, 2025, 07:10 PM UTC

   We are currently investigating an issue that is preventing some metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters. Metrics data collection remains unaffected; however, we are seeing unexpected errors when retrieving metrics for display in the console. We are actively working to identify the root cause and restore full functionality. Further updates will be provided as our investigation continues.

2. identified Jun 04, 2025, 07:31 PM UTC

   We’ve identified the source of the issue that was preventing metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters. The underlying service has recovered, and metrics visualizations are now loading as expected. We are continuing to monitor the situation to ensure full stability.

3. monitoring Jun 04, 2025, 08:19 PM UTC

   Metrics visualizations are now loading as expected. We are continuing to monitor system behavior to ensure stability and will mark this incident as resolved once we confirm full recovery.

4. resolved Jun 04, 2025, 09:35 PM UTC

   The issue that was preventing metrics pages from loading in the Cockroach Cloud console for Basic and Standard tier clusters has been fully resolved. Metrics are now loading as expected, and we’ve received confirmation from our service provider that the underlying issue has been addressed. We will continue to monitor for any signs of recurrence, but no further impact is expected at this time. Thank you for your patience.

Read the full incident report →

Started Jun 01, 2025, 07:29 AM UTC· resolved Jun 01, 2025, 07:35 PM UTC

1. resolved Jun 02, 2025, 07:45 AM UTC

   Incident Start AWS experienced a brief network blip in the eu-west-1, eu-west-2, and eu-central-1 regions. Clusters in these regions were unavailable between June 1, 19:29–19:35 UTC. Incident End The network issue affecting clusters in the impacted AWS regions has been fully resolved *automatically* as of 19:35 UTC. All affected clusters are now operating normally. Please contact support if you have any concerns.

Read the full incident report →

Started Nov 19, 2024, 04:48 PM UTC· resolved Nov 19, 2024, 06:36 PM UTC

1. investigating Nov 19, 2024, 04:48 PM UTC

   We have received alerts indicating elevated error rates on isolated Standard and Basic clusters. The Engineering team is currently investigating the issue.

2. monitoring Nov 19, 2024, 05:06 PM UTC

   The root cause of the issue was identified and resolved. Engineering is monitoring the situation.

3. resolved Nov 19, 2024, 06:36 PM UTC

   The Engineering team has isolated and resolved the elevated error rate for all affected clusters.

Read the full incident report →