Fastest free Nervos CKB RPC, live no-key endpoint latency
HTTP round-trip latency for get_tip_block_number against every available public Nervos CKB node, audited every 60 seconds from 3 regions.
TL;DR. As of , CKBapp leads rpc latency at 54 ms (p50, 24h) on Fastest free Nervos CKB RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/ckb-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Nervos CKB (Common Knowledge Base) is a proof-of-work Layer 1 blockchain using the NC-MAX consensus protocol, a variant of Nakamoto consensus with improved selfish-mining resistance. CKB targets roughly one block every 10 seconds with probabilistic finality. Public JSON-RPC endpoints are available without an API key from the Nervos Foundation and CKBapp. Every provider was live-verified with consecutive get_tip_block_number probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Nervos CKB. We measure the round-trip latency of a single JSON-RPC call (get_tip_block_number) against every available public CKB node that sustains continuous probing: 2 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a CKB-scaled staleness gap (30 blocks, around 5 min at 10 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the CKB-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Nervos CKB RPC right now?
CKBapp currently leads at 54 ms (CKB block number p50 over the last 24h), measured against 2 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Nervos CKB RPC endpoints work without an API key?
2 endpoints sustain continuous keyless probing at launch: the Nervos Foundation node (mainnet.ckb.dev/rpc) and CKBapp (mainnet.ckbapp.dev/rpc). Every listed endpoint was live-verified with a get_tip_block_number call returning a parsable hex block number before inclusion.
Does the fastest CKB RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin.
How is Nervos CKB RPC latency measured here, technically?
One get_tip_block_number JSON-RPC call 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. 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities