Bitcoin Cash RPC endpoints: free public URLs by latency
HTTP round-trip latency for block-height queries against every available public Bitcoin Cash endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Bitcore (Bitpay) has the lowest median latency of the 3 free public Bitcoin Cash RPC endpoints measured, 123 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/bitcoin-cash-rpc. 3 public endpoints, no key: api.bitcore.io, rest1.biggestfan.net, api.blockchair.com. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Bitcoin Cash is a proof-of-work UTXO blockchain forked from Bitcoin in August 2017; it targets one block every 600 seconds using the SHA-256 algorithm. Unlike Bitcoin proper, Bitcoin Cash does not expose a standard JSON-RPC port without authentication on any public endpoint. Public block-height data is available without an API key from Blockchair (REST GET of its BCH stats endpoint), Bitcore by Bitpay (REST GET of its block/tip endpoint), and BiggestFan's public BCHN node (REST GET of its getBlockchainInfo endpoint). Each provider uses its own REST API shape, so the harness dispatches to a dedicated probe function per provider URL. Every provider was live-verified with consecutive block-height probes at launch.
Methodology
Bitcoin Cash: 3 free public RPC endpoints answering a block-tip REST call every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Bitcore (Bitpay) leads at 123 ms. We measure the round-trip latency of a block-height query against every available public Bitcoin Cash endpoint that sustains continuous probing: 3 providers live today, every 60 seconds, from us-east, eu-west and Singapore. Blockchair is probed via REST GET of its BCH stats endpoint (api.blockchair.com/bitcoin-cash/stats, data.best_block_height). Bitcore is probed via REST GET of its block/tip endpoint (api.bitcore.io/api/BCH/mainnet/block/tip, height field). BiggestFan is probed via REST GET of the BCHN node getBlockchainInfo endpoint (rest1.biggestfan.net/v2/blockchain/getBlockchainInfo, blocks field). The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Bitcoin-Cash-scaled staleness gap (2 blocks, around 20 min at 600 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Bitcoin Cash-scoped answer with per-region breakdowns as a first-class dimension.
Results: 3 free public Bitcoin Cash RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Bitcore (Bitpay) | 123 ms | 155 ms | 510 ms | 99.44% |
| 2 | BiggestFan Node | 132 ms | 156 ms | 563 ms | 99.40% |
| 3 | Blockchair | 143 ms | 162 ms | 190 ms | 100.00% |
Public Bitcoin Cash RPC endpoints measured
The 3 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
Bitcore (Bitpay)https://api.bitcore.io/api/BCH/mainnet/block/tip123 ms99.4%
BiggestFan Nodehttps://rest1.biggestfan.net/v2/blockchain/getBlockchainInfo132 ms99.4%
Blockchairhttps://api.blockchair.com/bitcoin-cash/stats143 ms100.0%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Frequently asked
Which Bitcoin Cash RPC endpoints work without an API key?
3 endpoints are probed on this chain: Blockchair (api.blockchair.com/bitcoin-cash/stats, REST GET), Bitcore by Bitpay (api.bitcore.io/api/BCH/mainnet/block/tip, REST GET) and BiggestFan BCHN node (rest1.biggestfan.net/v2/blockchain/getBlockchainInfo, REST GET). Every listed endpoint was live-verified with a block-height probe returning a parsable result before inclusion.
Why do Bitcoin Cash providers use REST APIs instead of JSON-RPC?
Bitcoin Cash nodes do support Bitcoin-compatible JSON-RPC, but no public provider exposes that interface without authentication on a keyless endpoint. Blockchair and Bitcore expose proprietary REST APIs; BiggestFan runs a BCHN full node and wraps its output in a REST endpoint. All three return a parsable block height in their response, which is what the harness reads.
What is Bitcoin Cash staleness measured as on this benchmark?
A response is classified as stale when the returned block height is more than 2 blocks behind the cross-provider maximum. At BCH's 600-second target block time, 2 blocks corresponds to about 20 minutes, providing reasonable tolerance for normal block-time variance without masking genuine sync lag.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities