Vendor record
CockroachDB
Checked
Front door check counts and CockroachDB’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented CockroachDB endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- cockroachlabs.cloud
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every CockroachDB product, region or your app worked.
How we count front door checksCockroachDB says
Incident posts from CockroachDB’s status page, with its titles, impact levels and times. They say what CockroachDB chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
7
incidents CockroachDB posted, last 1 year
Median recorded duration: 4h 13m. From 7 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Stock out issues in GCP us-central1
MinorCockroachDB’s postStarted, per CockroachDB
Closed in our record(22h 18m)
Connection attempts failing for multiple Basic tenants in GCP South America (southamerica-east1).
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(1h 31m)
Cloud Latency, Delays, Connection Issues
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(4h 13m)
Cluster connectivity and execution issues
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(20h 4m)
Cluster Creation Failure
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(1h 21m)
2 older records
Unable to accept invites
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(43m)
Degraded performance in one AWS us-east-1 availability zone
MajorCockroachDB’s postStarted, per CockroachDB
Closed in our record(19h 47m)
Your code, your dependencies
See which of your code paths call CockroachDB
Connect GitHub or GitLab to find where your public or private repository uses CockroachDB. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add CockroachDB status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is CockroachDB currently down?
CockroachDB's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did CockroachDB last have an outage?
The most recent closed incident record began 9 days ago and spans 22h 18m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for CockroachDB?
No. CheckUpstream checks CockroachDB’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor CockroachDB in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track CockroachDB?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.