Fastest free Bitcoin Cash RPC, live no-key endpoint 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 , BiggestFan Node posts the lowest rpc latency at 220 ms (p50, 24h) on Fastest free Bitcoin Cash RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/bitcoin-cash-rpc.
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
Per-chain member of the RPC latency cluster, extended to Bitcoin Cash. We measure the round-trip latency of a block-height query against every available public Bitcoin Cash endpoint that sustains continuous probing: 3 providers at launch, 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.
Frequently asked
What is the fastest free Bitcoin Cash RPC right now?
BiggestFan Node currently leads at 220 ms (BCH block height p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Bitcoin Cash RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: 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.
Does the fastest Bitcoin Cash RPC change by region?
Often. Blockchair and Bitcore have fixed infrastructure, so their latency rankings can shift significantly depending on your geographic origin. The region tabs at the top of the page re-scope every number to a single origin.
How is Bitcoin Cash RPC latency measured here, technically?
One block-height probe every 60 seconds against each provider from each of 3 regions. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Each provider uses a REST GET; the harness reads the block height from a different JSON field per provider (data.best_block_height for Blockchair, height for Bitcore, blocks for BiggestFan). Best-effort measurements; p50 is the median, p90 the 90th percentile and p99 the 99th percentile of latency samples collected over the last 24 hours.
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