Databases / Distributed SQL / CockroachDB Cloud

CockroachDB Cloud

OPERATIONAL

Since Aug 2023 · 50 incidents · status.cockroachlabs.cloud · checked just now

CompareStatus page
GradeBLast 90 days
BPRODA+SHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a Sev 1 the provider posted itself. A best case.
100.000%Grade B
IncidentsEverything posted on the status page except scheduled maintenance.
50 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
7h 00m
LongestLongest single incident, start to resolved.
22h 12m
Since lastTime since the last counted incident was resolved.
2d 3h

By area

BProduction
5INCIDENTS
2d 6hAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Oct 6, 2026 · 22h 12mStock out issues in GCP us-central1
SEV 2Aug 4, 2026 · 20h 04mCluster connectivity and execution issues
SEV 2Oct 20, 2026 · 7h 00mgcp-eu-west2-b-availability-zone-issues
Most hit
CockroachDB Basic/Standard4
CockroachDB Advanced2
CockroachDB Cloud - CockroachDB Basic/Standard2
CockroachDB Cloud - CockroachDB Advanced2
Worse. 7 in the last 6 months, 3 in the 6 before.
A+Shipping
1INCIDENTS
7h 00mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Oct 20, 2026 · 7h 00mgcp-eu-west2-b-availability-zone-issues
Most hit
CockroachDB Basic/Standard1
CockroachDB Advanced1
CockroachDB Cloud - CockroachDB Basic/Standard1
CockroachDB Cloud - CockroachDB Advanced1
Worse. 2 in the last 6 months, 1 in the 6 before.
CleanSev 3–4Sev 1–2No data

What it costs

One small production database, per month10 GB of data, about 1 GB of RAM on all month, 10M queries a month, one region, no replicas, commercial use. Cheapest plan that runs it.
Billed in request unitsBasic bills request units and Standard bills provisioned vCPUs; neither maps cleanly to this workload.

www.cockroachlabs.com · checked Oct 22, 2026 · Wrong price?

Trend, last 12 months

Worse. 8 in the last 6 months, 4 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down5
Sev 3 · Can't shipCan't deploy, build or manage it0
Sev 4 · PapercutDocs, status page, slow dashboard0

When it breaks

Start times, last 12 months, UTC.

What breaks

CockroachDB Basic/Standard7 incidents
CockroachDB Advanced6 incidents
CockroachDB Cloud - CockroachDB Basic/Standard2 incidents
CockroachDB Cloud - CockroachDB Advanced2 incidents
Cloud Console2 incidents
CockroachDB Cloud Console2 incidents

Communication

Updates eachStatus page updates per incident, on average.
4.3Last 12 months
Update gapMedian time between status page updates during an incident.
1h 11mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 12Sev 1–2

Incident history

Oct 20, 20267h 00mSEV 2
gcp-eu-west2-b-availability-zone-issuesA power event at GCP europe-west2-b disrupted CockroachDB Cloud services in that zone from about 07:53 to 14:53 UTC on 20 October 2026. The provider said GCP mitigated the power event and services returned to normal. No data loss was reported.AI-graded · one location · CockroachDB Basic/Standard +3
Why this grade
  1. RULES · SEV 1
    Sev 1 because CockroachDB Basic/Standard had a partial outage
  2. CLAUDE · SEV 2 · LOCAL · MEDIUM CONFIDENCE
    A GCP power event in one europe-west2 zone disrupted CockroachDB Cloud clusters there for about seven hours; other zones and regions were not described as affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
4 updates
  1. 07:53 UTC · investigating
    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. 11:48 UTC · identified
    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. 12:57 UTC · monitoring
    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. 14:53 UTC · resolved
    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.
Source
Oct 6, 202622h 12mSEV 2
Stock out issues in GCP us-central1Sev 2 because CockroachDB Advanced had degraded performanceCockroachDB Advanced +3
3 updates
  1. 21:21 UTC · investigating
    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. 21:22 UTC · monitoring
    We are continuing to monitor these stockouts and will post updates as new information comes in.
  3. 19:33 UTC · resolved
    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.
Source
Sep 17, 20261h 31mSEV 2
Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).Network connectivity issues prevented connections to multiple CockroachDB Cloud Basic clusters in GCP São Paulo (southamerica-east1) from 19:08 to 20:39 UTC on 2026-09-17. Connectivity was restored; the text gives no specific cause.AI-graded · regional · CockroachDB Basic/Standard +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because CockroachDB Basic/Standard had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Connection attempts failed for multiple Basic tenants in GCP southamerica-east1 for about 90 minutes; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
2 updates
  1. 19:08 UTC · investigating
    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. 20:39 UTC · resolved
    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.
Source
Sep 1, 20264h 09mSEV 2
Cloud Latency, Delays, Connection IssuesA Google Cloud networking outage caused heightened latency, delays and connection issues for CockroachDB Basic and Standard clusters in us-central1, asia-east1 and europe-west4-b. us-central1 and asia-east1 recovered early; europe-west4-b was still impacted until the provider was declared resolved after about four hours. No data loss was reported.AI-graded · regional · CockroachDB Basic/Standard
Why this grade
  1. RULES · SEV 1
    Sev 1 because CockroachDB Basic/Standard had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Basic and Standard clusters saw elevated latency, delays and connection failures in a few Google Cloud regions for about four hours.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
6 updates
  1. 15:36 UTC · investigating
    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. 15:39 UTC · investigating
    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. 16:04 UTC · investigating
    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. 16:13 UTC · monitoring
    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. 16:37 UTC · monitoring
    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. 19:45 UTC · resolved
    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.
Source
Aug 4, 202620h 04mSEV 2
Cluster connectivity and execution issuesSome Basic and Standard CockroachDB clusters in eu-west1 were unable to connect or execute queries starting August 4 at 23:46 UTC. The provider reported mitigation by 03:55 UTC on August 5 and marked the incident resolved at 19:50 UTC after monitoring. The root cause was still under investigation at the last update.AI-graded · regional · CockroachDB Basic/Standard
Why this grade
  1. RULES · SEV 1
    Sev 1 because CockroachDB Basic/Standard had a partial outage
  2. CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
    Some Basic and Standard clusters in eu-west1 could not connect or run queries for about four hours; other regions were not reported affected.
  3. Claude Haiku 5.5 · prompt v5 · Oct 22, 2026 · Raw record
5 updates
  1. 23:46 UTC · investigating
    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. 23:47 UTC · investigating
    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. 23:52 UTC · investigating
    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. 03:55 UTC · monitoring
    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. 19:50 UTC · resolved
    Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.
Source
Jul 12, 20261h 17mSEV 1
Cluster Creation FailureSev 1 because CockroachDB Basic/Standard had a partial outageCockroachDB Basic/Standard
2 updates
  1. 20:08 UTC · investigating
    We are currently aware of and investigating a cluster creation failure. Teams are engaged and actively working to mitigate as quickly as possible.
  2. 21:24 UTC · resolved
    The cluster creation issue has been restored. Issue is resolved.
Source
Jun 9, 202636mSEV 3
Unable to accept invitesSev 3 because Cloud Console had a partial outageCloud Console +1
2 updates
  1. 21:26 UTC · identified
    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. 22:02 UTC · resolved
    Fix deployment is complete, tested and verified.
Source
May 8, 202619h 40mSEV 1
Degraded performance in one AWS us-east-1 availability zoneSev 1 because CockroachDB Advanced had a partial outageCockroachDB Advanced
4 updates
  1. 02:13 UTC · monitoring
    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. 03:24 UTC · monitoring
    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. 08:25 UTC · monitoring
    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. 21:53 UTC · resolved
    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.
Source
Mar 18, 202639mSEV 3
Cloud Console Social Login Auth UnavailableSev 3 because Cloud Console had a partial outageCloud Console +1
2 updates
  1. 15:23 UTC · investigating
    Social logins for customers using personal/non-SSO Microsoft accounts is currently unavailable. Our teams are aware and currently investigating.
  2. 16:02 UTC · resolved
    Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.
Source
Mar 1, 202610d 4hSEV 1
Cluster unavailability and degraded cluster operations in AWS me-central...Sev 1 because CockroachDB Advanced had a major outageCockroachDB Advanced
8 updates
  1. 15:11 UTC · monitoring
    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. 20:43 UTC · monitoring
    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. 23:09 UTC · monitoring
    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. 01:51 UTC · monitoring
    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. 02:47 UTC · monitoring
    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. 09:01 UTC · monitoring
    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. 17:50 UTC · monitoring
    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. 19:51 UTC · resolved
    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.
Source
Feb 9, 202612h 16mSEV 1
Connectivity issues to Standard and Basic clusters on AWSSev 1 because CockroachDB Basic/Standard had a major outageCockroachDB Basic/Standard
3 updates
  1. 03:04 UTC · investigating
    We are investigating connectivity issues to Standard and Basic clusters on AWS.
  2. 04:15 UTC · monitoring
    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. 15:20 UTC · resolved
    Standard and Basic clusters continue to function normally.
Source
Feb 2, 20262h 50mSEV 1
Advanced cluster creation on AWS taking longer than expectedSev 1 because CockroachDB Advanced had a partial outageCockroachDB Advanced
4 updates
  1. 16:56 UTC · identified
    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. 17:57 UTC · identified
    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. 19:31 UTC · identified
    We are continuing to work on the fix for this issue. Next update will be at 15:00 US/Eastern.
  4. 19:46 UTC · resolved
    We have deployed and verified a fix. Advanced clusters should now create within normal time frames.
Source
Oct 31, 20256h 16mSEV 1
Standard and Basic cluster creation on AWS delayedSev 1 because CockroachDB Basic/Standard had a major outageCockroachDB Basic/Standard
7 updates
  1. 15:54 UTC · investigating
    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. 16:21 UTC · investigating
    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. 18:22 UTC · identified
    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. 18:59 UTC · identified
    We are continuing to work on a fix for this issue. Next update will be by 4:00 PM US/Eastern time.
  5. 19:58 UTC · identified
    We are continuing to work on a fix for this issue. Next update will be by 4:30 PM US/Eastern time.
  6. 20:18 UTC · monitoring
    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. 22:09 UTC · resolved
    All cluster operations are working normally.
Source
Oct 30, 20251h 16mSEV 1
Advanced Cluster Creation DelayedSev 1 because CockroachDB Advanced had a partial outageCockroachDB Advanced
3 updates
  1. 14:50 UTC · investigating
    We are investigating errors that cause creation for Advanced clusters to take longer than usual. Standard and Basic cluster creation is operating normally.
  2. 15:25 UTC · monitoring
    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. 16:05 UTC · resolved
    Cluster creation is operating normally, and all delayed clusters have finished creation.
Source
Oct 20, 202525h 28mSEV 3
AWS us-east-1 outage impacting cluster operations and backupsSev 3 from the incident title (no components listed)
3 updates
  1. 13:28 UTC · identified
    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. 22:52 UTC · monitoring
    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. 14:56 UTC · resolved
    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.
Source
Sep 24, 20253h 29mSEV 1
Google Kubernetes incident impacting cluster operations in GCP.Sev 1 because CockroachDB Advanced had a partial outageCockroachDB Advanced
2 updates
  1. 12:31 UTC · identified
    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. 16:00 UTC · resolved
    Google has reported the issue has been resolved and we've verified cluster operations are functional.
Source

Peers, 90 days

Compare
UpstashGrade A+100.00% up4 incidentsMTTR 0m~$22.25/moPlanetScaleGrade A99.99% up5 incidentsMTTR 26m$10/moCockroachDB CloudGrade B100.00% up5 incidentsMTTR 7h 00m–/moMongoDB AtlasGrade C100.00% up18 incidentsMTTR 2h 35m$56.94/moSupabaseGrade F100.00% up26 incidentsMTTR 2h 02m$25.25/mo

README badge

CockroachDB Cloud's live grade, for your README.

CockroachDB Cloud grade badge
[![cockroachdb on downagain.dev](https://downagain.dev/badge/cockroachdb.svg)](https://downagain.dev/p/cockroachdb)