CheckUpstream measured CockroachDB at 100.000% availability across 2826 independent checks (global · api). 4 incidents were recorded in the past 12 months; the most recent resolved 27 days ago after 20 hours. Status signals are polled from CockroachDB's official Atlassian Statuspage status page, alongside independent probes and community reports.
30 days measured availability how this is computed
100.000%
global · api · n=2826 · p95 338ms (30d)
Share of our own checks against CockroachDB endpoints that returned CockroachDB's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 1 incident · 30 of 30 days with none posted · 0m of declared impact
Fewer incidents in the last 30 days than 44% of 232 tracked services.
Share of each window with no impact declared by CockroachDB
7d
100.000%
30d
100.000%
90d
100.000%
180d
99.679%
1y
99.842%
Does CockroachDB actually matter to you?
A CockroachDB outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Aug 4, 23:46 UTC · resolved in 20h 4m · Resolved
Jul 12, 20:08 UTC · resolved in 1h 21m · Resolved
Jun 9, 21:26 UTC · resolved in 43m · Resolved
Live CockroachDB status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/cockroachdb)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
CockroachDB is currently Operational. CheckUpstream tracks CockroachDB in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is CockroachDB down" view? See the CockroachDB Live status page.
May 8, 02:13 UTC · resolved in 19h 47m · Resolved
CockroachDB's last resolved incident started 27 days ago and lasted 20h 4m (a partial outage).
CockroachDB's 30-day measured availability is 100.000%, from CheckUpstream's own probes against CockroachDB endpoints. It is the share of checks that returned the expected response, not a figure taken from CockroachDB's status page.
Sign up to CheckUpstream and add CockroachDB to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll CockroachDB's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.