Loading status…
CockroachDB Cloud status · Data & Backend · checked (2s ago)
Also searched as CockroachDB, Cockroach Labs.
No — CockroachDB Cloud is not down. All CockroachDB Cloud systems are reported operational.
According to CockroachDB Cloud's official status page, CockroachDB Cloud was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, CockroachDB Cloud's feed reported no outage in 99.96% of our checks.
Everything above is read from CockroachDB Cloud's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported CockroachDB Cloud in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
CockroachDB Cloud is the managed version of Cockroach Labs' distributed SQL database — Postgres-compatible, replicated across nodes and regions, sold as serverless (now Basic and Standard) and dedicated clusters. Applications use it as their primary transactional store.
The status page reports per cloud provider and region, and separates the clusters themselves from the console and the API. Serverless and dedicated tiers are reported separately because they run on different infrastructure. Self-hosted CockroachDB, which many users run, is not covered here at all.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where CockroachDB Cloud's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days CockroachDB Cloud was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of CockroachDB Cloud's status endpoint.
CockroachDB Cloud has published 14 incidents in the last 12 months, newest first. Only what CockroachDB Cloud posted itself — not every problem users hit.
resolved · Sep 17, 07:08 PM (2d ago)
resolved · Sep 1, 03:36 PM (18d ago)
resolved · Aug 4, 11:46 PM (46d ago)
resolved · Jul 12, 08:08 PM (69d ago)
resolved · Jun 9, 09:26 PM (102d ago)
resolved · May 8, 02:13 AM (135d ago)
resolved · Mar 18, 03:23 PM (185d ago)
resolved · Mar 1, 03:11 PM (202d ago)
resolved · Feb 9, 03:04 AM (223d ago)
resolved · Feb 2, 04:56 PM (229d ago)
resolved · Oct 31, 03:54 PM (323d ago)
resolved · Oct 30, 02:50 PM (324d ago)
resolved · Oct 20, 01:28 PM (334d ago)
resolved · Sep 24, 12:31 PM (360d ago)
Retryable transaction errors are normal in a distributed database under contention and are your application's to handle, not an outage. Request-unit exhaustion on the serverless tiers throttles a cluster to a crawl with nothing posted anywhere. A cluster that has been idle can also take time to spin back up on the lower tiers.
CockroachDB Cloud is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.
