Nervos CKB RPC endpoints: free public URLs by 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 , Nervos Foundation has the lowest median latency of the 2 free public Nervos CKB RPC endpoints measured, 160 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/ckb-rpc. 2 public endpoints, no key: mainnet.ckb.dev, mainnet.ckbapp.dev. 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 →
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
Nervos CKB: 2 free public RPC endpoints answering `get_tip_block_number` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Nervos Foundation leads at 160 ms. 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 live today, 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.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus avg(quantile_over_time(...)); per-region breakdowns are first-class on this page via the region tabs.
- Payload: {"jsonrpc":"2.0","id":<rotating>,"method":"get_tip_block_number","params":[]}. Plain HTTP POST. The result field is a hex-encoded block number string (0x prefix).
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Nervos CKB-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=ckb. Provider coverage today: 2 endpoints.
Results: 2 free public Nervos CKB RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Nervos FoundationNervos Foundation official CKB mainnet public RPC, keyless | 160 ms | 419 ms | 489 ms | 99.93% (n=4320) |
| 2 | CKBappCKBapp community CKB mainnet public RPC, keyless | 181 ms | 478 ms | 521 ms | 100.00% (n=4321) |
Public Nervos CKB RPC endpoints measured
The 2 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.
Nervos Foundationhttps://mainnet.ckb.dev/rpc160 ms99.9%
CKBapphttps://mainnet.ckbapp.dev/rpc181 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 Nervos CKB RPC endpoints work without an API key?
2 endpoints are probed on this chain: 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities