Cockroach Labs の障害履歴

1. 2026年10月20日 7:53 UTCinvestigating

   GCP europe-west2-b および空室状況ゾーンは、現在問題が発生しています。 今後も状況を監視し、情報が増えれば状況をアップデートしていきます.

2. 2026年10月20日 11:48 UTCidentified

   GCPは、欧州西部2地域におけるこの崩壊を引き起こし、インパクトのあるサービスを緩和するために取り組んでいる、電力イベントを緩和しました。 移行確認後、更新いたします.

3. 2026年10月20日 12:57 UTCmonitoring

   GCP は、欧州地域におけるこの崩壊を引き起こし、ほとんどの GCP サービスが回復した、電力イベントを緩和しました。 今後もCRLサービスの影響を受け、解決前に正常な動作に戻ります.

4. 2026年10月20日 14:53 UTCresolved

   GCP は、欧州西部地域におけるこの崩壊を引き起こした電力イベントを緩和しました。 GCP および CRL サービスは、通常の動作に戻りました。 さらなるアクションは必要ありません.

公式のインシデント更新を自動翻訳しています。

1. 2026年10月6日 21:21 UTCinvestigating

   現在、GCP の us-central1 領域におけるインスタンスの在庫(容量の欠如)の問題を監視しています。 可能であれば、新しいクラスターを作成する際に、異なる領域を使用することをお勧めします。 クラスターの作成と編集は、最終的に容量が利用可能になると成功すると予想されます。 これらの容量の問題が解決されると、GCP はタイムラインを提供していませんが、今後もこのページを監視・更新していきます.

2. 2026年10月6日 21:22 UTCmonitoring

   当社は、これらの株式を継続的に監視し、更新情報を新しい情報として投稿します.

3. 2026年10月7日 19:33 UTCresolved

   私たちは、この問題を監視し続けています。ただし、Googleは解決したときにETAを提供できません。 今後も必要な能力を身につけていきたいと思っています。 お客様が、新しいクラスターをスピンすると、当社の中央部1で観察された容量の問題を回避するために、別の地域を選択することをお勧めします.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月17日 19:08 UTCinvestigating

   現在、GCP南米(サンパウロ/南アメリカ)でホストされているCockroachDBクラウド(Basic)クラスターがネットワーク接続の問題が発生しています。 調査を行い、更新を短時間で提供いたします

2. 2026年9月17日 20:39 UTCresolved

   この事件は解決しました。 GCP南米(サンパウロ/南アメリカ)でホストされているCockroachDBクラウド(基本)クラスターは、完全に復元されたネットワーク接続の問題を経験しました。 コネクティビティは正常に戻り、影響を受けたすべてのクラスターが期待通り動作しています。 ご迷惑をおかけいたしますが、何卒ご了承ください。 引き続き、問題が発生した場合は、サポートにお問い合わせください.

公式のインシデント更新を自動翻訳しています。

1. 2026年9月1日 15:39 UTCinvestigating

   Google Cloudは、Cockroachクラウド顧客に影響を与えるネットワークの停電を経験しています。 Cockroachクラウドのお客様は、レイテンシー、遅延、または接続の問題が高まる可能性があります。 当社のチームは、この事件を十分に認識し、関与しています。 既知の現在の影響: アジアイースト-1

2. 2026年9月1日 16:04 UTCinvestigating

   現状を監視し、過去15分を上回る改善点を把握しています。 既知の現在の影響: アジア東1、ヨーロッパ西4b

3. 2026年9月1日 16:13 UTCmonitoring

   Googleは今、私たち-central1とasia-east1が両方の解決であることを報告していますが、欧州-west4-bはまだ積極的に影響しています。 当社の社内チームは、当社の中央部1およびアジア東1地域において、過去15分でエラーが確認されていないことを確認しています。 既知の現在の影響: 欧州西4b

4. 2026年9月1日 16:37 UTCmonitoring

   Googleは、Googleが私たちを報告していることを学習しています central1-b また、劣化に影響を与え、経験しています。 ネットワークレベルの緩和の取り組みに続いて、基礎となるネットワークインフラは完全に回復しました。 クラウド上のGoogle製品エンジニアリングチームは、現在、個々のサービスの回復状況を検証しています.

5. 2026年9月1日 19:45 UTCresolved

   Googleの影響は完全に解決するように報告されています。 社内チームがこのレポートを確認しました。 全てのサービスが復元されます。 さらにヘルプが必要な場合は、サポートでチケットを受け取り、提出してください.

公式のインシデント更新を自動翻訳しています。

1. 2026年8月4日 23:46 UTCinvestigating

   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日 23:47 UTCinvestigating

   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日 23:52 UTCinvestigating

   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日 3:55 UTCmonitoring

   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日 19:50 UTCresolved

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

1. 2026年7月12日 20:08 UTCinvestigating

   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日 21:24 UTCresolved

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

1. 2026年6月9日 21:26 UTCidentified

   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日 22:02 UTCresolved

   Fix deployment is complete, tested and verified.

1. 2026年5月8日 2:13 UTCmonitoring

   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日 3:24 UTCmonitoring

   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日 8:25 UTCmonitoring

   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日 21:53 UTCresolved

   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日 15:23 UTCinvestigating

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

2. 2026年3月18日 16:02 UTCresolved

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

1. 2026年3月1日 15:11 UTCmonitoring

   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日 20:43 UTCmonitoring

   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日 23:09 UTCmonitoring

   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日 1:51 UTCmonitoring

   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日 2:47 UTCmonitoring

   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日 9:01 UTCmonitoring

   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日 17:50 UTCmonitoring

   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日 19:51 UTCresolved

   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日 3:04 UTCinvestigating

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

2. 2026年2月9日 4:15 UTCmonitoring

   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日 15:20 UTCresolved

   Standard and Basic clusters continue to function normally.

1. 2026年2月2日 16:56 UTCidentified

   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日 17:57 UTCidentified

   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日 19:31 UTCidentified

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

4. 2026年2月2日 19:46 UTCresolved

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

1. 2025年10月31日 15:54 UTCinvestigating

   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日 16:21 UTCinvestigating

   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日 18:22 UTCidentified

   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日 18:59 UTCidentified

   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日 19:58 UTCidentified

   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日 20:18 UTCmonitoring

   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日 22:09 UTCresolved

   All cluster operations are working normally.

1. 2025年10月30日 14:50 UTCinvestigating

   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日 15:25 UTCmonitoring

   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日 16:05 UTCresolved

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

1. 2025年10月20日 13:28 UTCidentified

   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日 22:52 UTCmonitoring

   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日 14:56 UTCresolved

   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日 12:31 UTCidentified

   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日 16:00 UTCresolved

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

1. 2025年7月29日 23:08 UTCinvestigating

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

2. 2025年7月29日 23:17 UTCmonitoring

   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日 23:35 UTCresolved

   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日 21:39 UTCidentified

   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日 4:22 UTCresolved

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

1. 2025年7月3日 16:58 UTCinvestigating

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

2. 2025年7月3日 17:39 UTCresolved

   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日 17:42 UTCinvestigating

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

2. 2025年7月2日 18:50 UTCidentified

   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日 19:32 UTCmonitoring

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

4. 2025年7月2日 20:46 UTCresolved

   All cluster operations are succeeding normally at this time.