Cockroach Labs kesinti geçmişi

1. 20 Ekim 2026 07:53 UTCinvestigating

   GCP europe-west2-b ve kullanılabilirlik alanı şu anda sorunlar yaşıyor. Bu durumu izlemeye ve daha fazla bilgiye sahip olduğumuz bir kez güncelleme statüsünü izlemeye devam edeceğiz.

2. 20 Ekim 2026 11:48 UTCidentified

   GCP, Avrupa-batı2 bölgesinde bu kesintiye neden olan güç olayını hafifletti ve etkilenen hizmetler üzerinde çalışıyor. Bir kez mitigation onayımız olacak.

3. 20 Ekim 2026 12:57 UTCmonitoring

   GCP, Avrupa-batı2 bölgesinde bu kesintiye neden olan güç olayını ve çoğu GCP hizmetlerini azalttı. CRL hizmetlerinin çözülmesinden önce normal operasyona geri dönmesine devam edeceğiz.

4. 20 Ekim 2026 14:53 UTCresolved

   GCP, Avrupa-batı2 bölgesinde bu kesintiye neden olan güç etkinliğini azalttı. Tüm GCP ve CRL hizmetleri normal operasyona geri döndü. Daha fazla eylem gerekli değildir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 6 Ekim 2026 21:21 UTCinvestigating

   Şu anda GCP'deki örnekler için stokları izliyoruz. Mümkünse, müşteriler yeni kümeler oluştururken farklı bir bölgeyi kullanmaya tavsiye edilir. Set yaratımlarının ve düzenlemelerin sonunda kapasitenin mevcut olması gerektiği bekleniyor. GCP, bu kapasite sorunlarının çözüleceği bir zaman için zaman çizelgesi sağlamadı, ancak bu sayfayı daha fazla öğrendiğimiz gibi izlemeye ve güncellemeye devam edeceğiz.

2. 6 Ekim 2026 21:22 UTCmonitoring

   Bu stokları izlemeye devam ediyoruz ve yeni bilgi geldiğinde güncellemeler yayınlayacağız.

3. 7 Ekim 2026 19:33 UTCresolved

   Bu konuyu izlemeye devam ediyoruz; ancak Google çözüleceği zaman ETA sağlayamaz. Gerekli kapasite elde etmek için onlarla çalışmaya devam edeceğiz. Müşteriler hala yeni kümeleri ortaya çıkarmak için başka bir bölgeyi seçmek için tavsiye edilirler. kapasite problemlerini bize merkezi1 ile gözlemler.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Eylül 2026 19:08 UTCinvestigating

   CockroachDB Bulut (Temel) GCP Güney Amerika'da barındırılan kümeler (São Paulo / Güney Amerika-doğu1) şu anda ağ bağlantı sorunları yaşıyor. Biz araştırıyoruz ve kısa bir süre içinde bir güncelleme yapacağız

2. 17 Eylül 2026 20:39 UTCresolved

   Bu olay çözüldü. CockroachDB Cloud (Basic) kümeleri GCP South America (São Paulo / Güney Amerika-east1) tam olarak restore edilmiş ağ bağlantı sorunları yaşadı. Connectivity normale döndü ve etkilenen tüm kümeler beklendiği gibi çalışıyor. Bunun sebep olabileceği herhangi bir kesintiden özür dileriz. Herhangi bir sorunu yaşamaya devam ederseniz lütfen iletişim desteği ile iletişime geçin.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 1 Eylül 2026 15:39 UTCinvestigating

   Google Cloud, Cockroach Cloud müşterileri etkileyen ağ kesintilerini deneyimliyor. Cockroach Cloud müşterileri gecikmiş gecikme, gecikmeler veya bağlantı sorunları yaşayabilir. Takımlarımız bu olayda haberdar ve tamamen meşgul. Bilinen mevcut Etkileri: Us-merkez-1, asia-east-1

2. 1 Eylül 2026 16:04 UTCinvestigating

   Hala durumu takip ediyoruz, son 15 dakika içinde bazı iyileşme görüyoruz, ancak tam olarak çözülmedi. Bilinen mevcut Etkileri: Us-merkez1, asia-east1, Avrupa-batı4-b

3. 1 Eylül 2026 16:13 UTCmonitoring

   Google şimdi bize merkezi1 ve asia-east1'in her ikisi de çözüldüğünü bildiriyor, ancak Avrupa-batı4-b hala aktif olarak etkileniyor. İç takımlarımız son 15 dakikada bizim merkezi1 ve asia-east1 bölgeleri için daha fazla hata teyit ediyor. Bilinen mevcut Etkileri: Avrupa-batı4-b

4. 1 Eylül 2026 16:37 UTCmonitoring

   Google'ın bizi-merkez1-b'i rapor ettiğini ve bozulmadığını öğreniyoruz. Ağ seviyesi mitigation çabaları sonrasında, temel ağ altyapısı tamamen restore edilmiştir. Buluttaki Google Ürün Mühendisliği takımları şu anda bireysel hizmetlerin kurtarma statüsünü geçerlidir.

5. 1 Eylül 2026 19:45 UTCresolved

   Google etkileri şimdi tamamen çözülebilir olarak rapor edilir. İç takımlar bu raporu doğruladı. Tüm hizmetler restore edilir. Daha fazla yardıma ihtiyacınız var, lütfen dışarı çık ve Destek ile bir bilet gönder.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 4 Ağustos 2026 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. 4 Ağustos 2026 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. 4 Ağustos 2026 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. 5 Ağustos 2026 03: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. 5 Ağustos 2026 19:50 UTCresolved

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

1. 12 Temmuz 2026 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. 12 Temmuz 2026 21:24 UTCresolved

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

1. 9 Haziran 2026 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. 9 Haziran 2026 22:02 UTCresolved

   Fix deployment is complete, tested and verified.

1. 8 Mayıs 2026 02: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. 8 Mayıs 2026 03: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. 8 Mayıs 2026 08: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. 8 Mayıs 2026 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. 18 Mart 2026 15:23 UTCinvestigating

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

2. 18 Mart 2026 16:02 UTCresolved

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

1. 1 Mart 2026 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. 1 Mart 2026 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. 1 Mart 2026 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. 2 Mart 2026 01: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. 2 Mart 2026 02: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. 2 Mart 2026 09: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. 2 Mart 2026 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. 11 Mart 2026 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. 9 Şubat 2026 03:04 UTCinvestigating

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

2. 9 Şubat 2026 04: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. 9 Şubat 2026 15:20 UTCresolved

   Standard and Basic clusters continue to function normally.

1. 2 Şubat 2026 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. 2 Şubat 2026 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. 2 Şubat 2026 19:31 UTCidentified

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

4. 2 Şubat 2026 19:46 UTCresolved

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

1. 31 Ekim 2025 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. 31 Ekim 2025 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. 31 Ekim 2025 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. 31 Ekim 2025 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. 31 Ekim 2025 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. 31 Ekim 2025 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. 31 Ekim 2025 22:09 UTCresolved

   All cluster operations are working normally.

1. 30 Ekim 2025 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. 30 Ekim 2025 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. 30 Ekim 2025 16:05 UTCresolved

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

1. 20 Ekim 2025 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. 20 Ekim 2025 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. 21 Ekim 2025 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. 24 Eylül 2025 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. 24 Eylül 2025 16:00 UTCresolved

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

1. 29 Temmuz 2025 23:08 UTCinvestigating

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

2. 29 Temmuz 2025 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. 29 Temmuz 2025 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. 21 Temmuz 2025 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. 22 Temmuz 2025 04:22 UTCresolved

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

1. 3 Temmuz 2025 16:58 UTCinvestigating

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

2. 3 Temmuz 2025 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. 2 Temmuz 2025 17:42 UTCinvestigating

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

2. 2 Temmuz 2025 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. 2 Temmuz 2025 19:32 UTCmonitoring

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

4. 2 Temmuz 2025 20:46 UTCresolved

   All cluster operations are succeeding normally at this time.