dRPC leads on both live benchmarks. dRPC wins on Arc RPC endpoints (40 ms vs 84 ms), Most requests a free RPC plan buys, across 13 providers (10.50M vs 191.7K). Data as of 2026-11-05 UTC.
Institutional node infrastructure across 50+ chains, normally key-gated. On Arc it also serves the keyless endpoint the chain's docs publish (rpc.blockdaemon.mainnet.arc.io), which is what this cohort measures.
Decentralized RPC mesh routing requests across third-party node providers with consensus checks. Free public tier plus higher-tier authenticated access.
Blockdaemon
Trails84 ms
dRPC
Leads40 ms
Per region
| Region | Blockdaemon | dRPC |
|---|---|---|
| US-East | 89 ms | 51 ms |
| EU-West | 9 ms | 53 ms |
| Singapore | 155 ms | 16 ms |
Blockdaemon
Trails191.7K
dRPC
Leads10.50M
Allowance, not latency and not reliability. A plan that buys the most requests is not thereby the fastest or the most correct; those are measured on the per-chain RPC pages. Published allowances, human-verified against each provider's own pricing page with the date it was read. A free plan is one that costs nothing and renews, so Quicknode's one-month trial is not here. Where a provider publishes a daily cap it is multiplied by 30.
Blockdaemon and dRPC are compared on 2 shared OpenChainBench benchmarks. dRPC leads on Arc RPC endpoints. See the live table on this page for every metric.
On the Arc RPC endpoints benchmark, dRPC leads at 40 ms versus Blockdaemon at 84 ms. Live measurement is updated continuously by the OpenChainBench harness.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing; panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.