Cockroach Labs 中断历史

1. 2026年9月1日 UTC 15:39investigating

   Google Cloud正在经历网络中断, 影响着Cockroach Cloud的客户。 Cockroach Cloud 客户可能会遇到更长时间、延误或连接问题。 我们的小组了解并充分参与了这一事件。 已知当前影响 : 东一号

2. 2026年9月1日 UTC 16:04investigating

   我们仍然在监测局势,在过去15分钟中看到一些改善,但是没有完全解决。 已知当前影响 : europe-west-4-b 欧统局

3. 2026年9月1日 UTC 16:13monitoring

   Google现在报告说,我们中央一级和东部一级都解决了,但欧洲西部4-b仍然受到积极的影响。 在过去15分钟里,我们的内部小组正在确认我们中部和东部地区没有进一步的错误。 已知当前影响 : 欧洲西部4-b

4. 2026年9月1日 UTC 16:37monitoring

   我们得知Google正在报告我们-中央1-b也受到了影响并正在经历退化。 在网络一级缓解努力之后,基本的网络基础设施已完全恢复。 整个Cloud的Google产品工程团队目前正在验证单个服务的恢复状态.

5. 2026年9月1日 UTC 19:45resolved

   谷歌的影响现已报告为已完全解决。 内部小组已经确认了这份报告。 所有服务恢复。 需要帮助时,请联系支援部门办理罚单.

自动翻译自官方事件更新。

1. 2026年8月4日 UTC 23:46investigating

   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. 2026年8月4日 UTC 23:47investigating

   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. 2026年8月4日 UTC 23:52investigating

   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. 2026年8月5日 UTC 03:55monitoring

   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. 2026年8月5日 UTC 19:50resolved

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

1. 2026年7月12日 UTC 20:08investigating

   We are currently aware of and investigating a cluster creation failure. Teams are engaged and actively working to mitigate as quickly as possible.

2. 2026年7月12日 UTC 21:24resolved

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

1. 2026年6月9日 UTC 21:26identified

   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. 2026年6月9日 UTC 22:02resolved

   Fix deployment is complete, tested and verified.

1. 2026年5月8日 UTC 02:13monitoring

   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. 2026年5月8日 UTC 03:24monitoring

   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. 2026年5月8日 UTC 08:25monitoring

   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. 2026年5月8日 UTC 21:53resolved

   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.

1. 2026年3月18日 UTC 15:23investigating

   Social logins for customers using personal/non-SSO Microsoft accounts is currently unavailable. Our teams are aware and currently investigating.

2. 2026年3月18日 UTC 16:02resolved

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

1. 2026年3月1日 UTC 15:11monitoring

   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. 2026年3月1日 UTC 20:43monitoring

   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. 2026年3月1日 UTC 23:09monitoring

   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. 2026年3月2日 UTC 01:51monitoring

   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. 2026年3月2日 UTC 02:47monitoring

   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. 2026年3月2日 UTC 09:01monitoring

   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. 2026年3月2日 UTC 17:50monitoring

   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. 2026年3月11日 UTC 19:51resolved

   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.

1. 2026年2月9日 UTC 03:04investigating

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

2. 2026年2月9日 UTC 04:15monitoring

   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. 2026年2月9日 UTC 15:20resolved

   Standard and Basic clusters continue to function normally.

1. 2026年2月2日 UTC 16:56identified

   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. 2026年2月2日 UTC 17:57identified

   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. 2026年2月2日 UTC 19:31identified

   We are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern.

4. 2026年2月2日 UTC 19:46resolved

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

1. 2025年10月31日 UTC 15:54investigating

   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. 2025年10月31日 UTC 16:21investigating

   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. 2025年10月31日 UTC 18:22identified

   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. 2025年10月31日 UTC 18:59identified

   We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time.

5. 2025年10月31日 UTC 19:58identified

   We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time.

6. 2025年10月31日 UTC 20:18monitoring

   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. 2025年10月31日 UTC 22:09resolved

   All cluster operations are working normally.

1. 2025年10月30日 UTC 14:50investigating

   We are investigating errors that cause creation for Advanced clusters to take longer than usual. Standard and Basic cluster creation is operating normally.

2. 2025年10月30日 UTC 15:25monitoring

   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. 2025年10月30日 UTC 16:05resolved

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

1. 2025年10月20日 UTC 13:28identified

   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. 2025年10月20日 UTC 22:52monitoring

   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. 2025年10月21日 UTC 14:56resolved

   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.

1. 2025年9月24日 UTC 12:31identified

   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. 2025年9月24日 UTC 16:00resolved

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

1. 2025年7月29日 UTC 23:08investigating

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

2. 2025年7月29日 UTC 23:17monitoring

   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. 2025年7月29日 UTC 23:35resolved

   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.

1. 2025年7月21日 UTC 21:39identified

   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. 2025年7月22日 UTC 04:22resolved

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

1. 2025年7月3日 UTC 16:58investigating

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

2. 2025年7月3日 UTC 17:39resolved

   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.

1. 2025年7月2日 UTC 17:42investigating

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

2. 2025年7月2日 UTC 18:50identified

   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. 2025年7月2日 UTC 19:32monitoring

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

4. 2025年7月2日 UTC 20:46resolved

   All cluster operations are succeeding normally at this time.

1. 2025年6月27日 UTC 22:29identified

   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. 2025年6月27日 UTC 22:36resolved

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

1. 2025年6月12日 UTC 18:22identified

   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. 2025年6月12日 UTC 19:08identified

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

3. 2025年6月12日 UTC 19:54monitoring

   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. 2025年6月12日 UTC 21:31resolved

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

1. 2025年6月4日 UTC 19:10investigating

   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. 2025年6月4日 UTC 19:31identified

   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. 2025年6月4日 UTC 20:19monitoring

   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. 2025年6月4日 UTC 21:35resolved

   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.