Arc RPC endpoints: free public URLs and private API-key providers by latency
RPCsQuicknode
Trails60 ms
- rank
- #5
- samples
- 37provisional
dRPC
Leads40 ms
- p99
- 168 ms
- rank
- #1
- samples
- 4,320
RPC latency
Quicknoden/adRPCn/a
Quicknode vs dRPC
dRPC leads on both live benchmarks. dRPC wins on Arc RPC endpoints (40 ms vs 60 ms), Cheapest RPC provider, priced per workload across 19 providers ($49 vs $848). Data as of 2026-11-05 UTC.
Quicknode
Keyed RPC infrastructure across 30+ chains. Endpoint-scoped API tokens; free and paid plans are served from the same shared fleet, dedicated clusters on higher tiers.
dRPC
Decentralized RPC mesh routing requests across third-party node providers with consensus checks. Free public tier plus higher-tier authenticated access.
Side by side measurements
Cheapest RPC provider, priced per workload across 19 providers
RPCsQuicknode
Trails$848
- rank
- —
- samples
- 4provisional
dRPC
Leads$49
- rank
- #4
- samples
- 4provisional
Monthly cost, dapp mix at 10M requests
Quicknoden/adRPCn/a
Published prices, not invoices. Each figure is human-verified against the provider's own pricing page or API and carries the date it was read; the harness re-hashes 20 of those pages on a loop to catch an upstream edit. A 30-day month and flat traffic are assumed, the most generous reading. NOWNodes prices in EUR. A provider absent from a cell is not missing data: it has no plan that can serve that workload, usually a cap or a throughput ceiling rather than the price.
Frequently asked questions
Quicknode vs dRPC: which one is better?
Quicknode 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.
Which is faster, Quicknode or dRPC?
On the Arc RPC endpoints benchmark, dRPC leads at 40 ms versus Quicknode at 60 ms (provisional). Live measurement is updated continuously by the OpenChainBench harness.
How is the Quicknode vs dRPC comparison measured?
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.
How this pair was selected
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.