We started checking CockroachDB on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when CockroachDB reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what CockroachDB's own status page declared. Below it, any public chatter we saw about CockroachDB and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what CockroachDB's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about CockroachDB in the last 24 hours, which is not evidence that nothing is wrong.
CockroachDB's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is CockroachDB's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention CockroachDB next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
439
US-West
99.71%
343
Europe
100.00%
311
Asia-Pacific
100.00%
189
Their declared record
CockroachDB's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Oct 20, 2026, 7:53 AM UTC to Oct 20, 2026, 2:53 PM UTC (7h)resolved
their latest update (Oct 20, 2026, 2: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.
Stock out issues in GCP us-central1Minor incident
Oct 6, 2026, 9:21 PM UTC to Oct 7, 2026, 7:33 PM UTC (22h 12m)resolved
their latest update (Oct 7, 2026, 7: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 ca…
Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).Partial outage
Sep 17, 2026, 7:08 PM UTC to Sep 17, 2026, 8:39 PM UTC (1h 31m)resolved
their latest update (Sep 17, 2026, 8: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 …
Sep 1, 2026, 3:36 PM UTC to Sep 1, 2026, 7:45 PM UTC (4h 9m)resolved
their latest update (Sep 1, 2026, 7: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.
Cluster connectivity and execution issuesPartial outage
Aug 4, 2026, 11:46 PM UTC to Aug 5, 2026, 7:50 PM UTC (20h 4m)resolved
their latest update (Aug 5, 2026, 7:50 PM UTC): Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.
Cluster Creation FailurePartial outage
Jul 12, 2026, 8:08 PM UTC to Jul 12, 2026, 9:24 PM UTC (1h 17m)resolved
their latest update (Jul 12, 2026, 9:24 PM UTC): The cluster creation issue has been restored. Issue is resolved.
Unable to accept invitesMinor incident
Jun 9, 2026, 9:26 PM UTC to Jun 9, 2026, 10:02 PM UTC (36 min)resolved
their latest update (Jun 9, 2026, 10:02 PM UTC): Fix deployment is complete, tested and verified.
Degraded performance in one AWS us-east-1 availability zonePartial outage
May 8, 2026, 2:13 AM UTC to May 8, 2026, 9:53 PM UTC (19h 40m)resolved
their latest update (May 8, 2026, 9: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.
Cloud Console Social Login Auth UnavailablePartial outage
Mar 18, 2026, 3:23 PM UTC to Mar 18, 2026, 4:02 PM UTC (39 min)resolved
their latest update (Mar 18, 2026, 4:02 PM UTC): Social login for Microsoft accounts is now available. Please reach out to support if you continue to experience issues.
Cluster unavailability and degraded cluster operations in AWS me-central...Minor incident
Mar 1, 2026, 3:11 PM UTC to Mar 11, 2026, 7:51 PM UTC (10d 4h)resolved
their latest update (Mar 11, 2026, 7: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-…
Showing the 10 most recent of 50 incidents CockroachDB has declared in the history we hold.
These entries are CockroachDB's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
CockroachDB's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.