Is CockroachDB Down?

No — CockroachDB is up

Reachable from 7 of 8 checked regions — 1 region could not reach it

Average response time: 140ms

Last checked 30 minutes ago · checks run every 6 hours

Official status page: https://status.cockroachlabs.cloud

CockroachDB uptime

99.50%

Last 7 days

99.65%

Last 30 days

99.65%

Last 90 days

160ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 28 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams

146ms

DNS 0ms TCP 5ms TLS 12ms TTFB 131ms

arn

178ms

DNS 1ms TCP 9ms TLS 10ms TTFB 156ms

bom

304ms

DNS 0ms TCP 2ms TLS 6ms TTFB 296ms

cdg

117ms

DNS 0ms TCP 2ms TLS 16ms TTFB 115ms

dfw

60ms

DNS 0ms TCP 2ms TLS 8ms TTFB 58ms

ewr

56ms

DNS 2ms TCP 7ms TLS 12ms TTFB 49ms

fra

123ms

DNS 1ms TCP 6ms TLS 6ms TTFB 121ms

gru

Request failed: Get "https://cockroachlabs.cloud": dial tcp: lookup cockroachlabs.cloud on [fdaa::3]:53: server misbehaving

What CockroachDB does

CockroachDB Cloud is a managed distributed SQL database that spreads data across nodes and regions so it can survive losing any one of them. Cockroach Labs offers it in Basic, Standard and Advanced tiers. Teams pick it specifically for resilience, which makes an incident affecting the managed service a different question from the database's own fault tolerance.

What an outage looks like

Applications see connection failures, or transaction retries that never succeed. Queries return retryable errors under contention far more often than usual. The Cloud Console fails to load or shows stale cluster state. Sign-in to the console fails on its own, because authentication runs through a separate identity provider that the status page tracks region by region.

What to do about it

Check status.cockroachlabs.cloud, which lists Basic and Standard, Advanced, the Cloud Console and its Auth0 identity provider as separate components, so a failed console login rarely means the cluster is down. Retryable transaction errors are expected in distributed SQL and should already sit behind a retry loop; during an incident, back off rather than retrying tightly.

Is it down for everyone, or just you?

If this page says CockroachDB is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

CockroachDB outage FAQ

I cannot sign in to the console. Is my cluster down?

Usually not. Console sign-in runs through Auth0, which Cockroach Labs tracks as its own component and reports per region. An authentication failure there leaves clusters serving application traffic normally. Confirm by connecting to the database directly with a SQL client rather than judging cluster health by whether the web console will let you in.

Why am I seeing retry errors I do not normally see?

CockroachDB uses serializable transactions, so conflicting transactions are aborted with a retryable error rather than allowed to produce an inconsistent result. That is normal behaviour an application handles with a retry loop. During an incident, contention and latency rise together, so the rate climbs sharply. Retrying without backoff makes the problem worse rather than better.

Does one region failing take the whole database down?

That depends on how the cluster was configured. A multi-region cluster is designed to survive losing a region, staying available at higher latency. A single-region cluster has no such protection. Resilience here is a property of the deployment rather than of the product, so check the topology before assuming a regional incident is survivable.

Which tier's component should I read?

The one your cluster runs on. Basic and Standard share a component and Advanced has its own, so an incident can affect one and not the other. Reading the wrong line produces both false alarms and false reassurance, and the tier is shown in the Cloud Console next to the cluster name.

How we measure this

We request CockroachDB's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where CockroachDB publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when CockroachDB goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required