dRPC vs NOWNodes 2026: 4 live benchmarks compared

Name: dRPC vs NOWNodes OpenChainBench measurements
Creator: OpenChainBench
License: https://creativecommons.org/licenses/by/4.0/

OpenChainBench

dRPC vs NOWNodes

dRPC leads on all 4 live benchmarks. dRPC wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (201 ms vs 216 ms), Ethereum RPC endpoints (33 ms vs 130 ms), Bitcoin RPC endpoints (128 ms vs 290 ms), Cheapest RPC provider, priced per workload across 19 providers ($49 vs $102.20). Data as of 2026-10-25 UTC.

Read methodology Last measured Sun, 25 Oct 2026 03:55:50 UTCWindow: rolling 24h4 shared benchmarks

dRPC

Decentralized RPC mesh routing requests across third-party node providers with consensus checks. Free public tier plus higher-tier authenticated access.

NOWNodes

Multi-chain node provider covering 110+ blockchains. Key-based REST and WebSocket RPC plus block explorers, with keyless public endpoints on a handful of chains (Ethereum, BNB, Bitcoin) rate-limited to 5 requests per second.

Side by side measurements

Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (plus Solana and Polkadot)

RPCs

Headline: All chains

dRPC

Leads

201 ms

p99: 571 ms
rank: #10
samples: 319,483

NOWNodes

Trails

216 ms

p99: 549 ms
rank: #11
samples: 17,270

Per chain · per region

Chain	Provider	US-East	EU-West	Singapore	Aggregate
Ethereum	dRPC	36 ms	33 ms	28 ms	32 ms
Ethereum	NOWNodes	132 ms	46 ms	211 ms	130 ms

RPC latency

dRPCn/aNOWNodesn/a

Latency is conditional on success: the harness times only calls returning a valid fresh block, so a mostly-failing endpoint can post a fast p50. Rows below 50 percent success are degraded; unresponsive probes pin below the table. The All chains aggregate favours single-chain foundation endpoints (Base, Binance, Arbitrum, Optimism, Avalanche officials) since they rank on one chain only; use a chain tab for honest comparison. Dead endpoints (cloudflare-eth POST returns -32603) are excluded.

Ethereum RPC endpoints: free public URLs and private API-key providers by latency

RPCs

dRPC

Leads

33 ms

p99: 152 ms
rank: #1
samples: 4,311

NOWNodes

Trails

130 ms

p99: 422 ms
rank: #4
samples: 4,314

Per region

Region	dRPC	NOWNodes
US-East	36 ms	132 ms
EU-West	33 ms	46 ms
Singapore	28 ms	211 ms

RPC latency

dRPCn/aNOWNodesn/a

Bitcoin RPC endpoints: free public URLs by latency

RPCs

dRPC

Leads

128 ms

p99: 212 ms
rank: #2
samples: 4,314

NOWNodes

Trails

290 ms

p99: 572 ms
rank: #3
samples: 4,321

Per region

Region	dRPC	NOWNodes
US-East	151 ms	166 ms
EU-West	51 ms	110 ms
Singapore	180 ms	594 ms

RPC latency

dRPCn/aNOWNodesn/a

Cheapest RPC provider, priced per workload across 19 providers

RPCs

Provider	Monthly cost, dapp mix at 10M requests	Effective cost per 1M requests	Billing units per request
dRPCprovisional	$49	$4.90	20
NOWNodesprovisional	$102.20	$10.22	1

View

dRPCn/aNOWNodesn/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 25 of those artifacts 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

dRPC vs NOWNodes: which one is better?

dRPC and NOWNodes are compared on 4 shared OpenChainBench benchmarks. dRPC leads on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains. See the live table on this page for every metric.

Which is faster, dRPC or NOWNodes?

On the Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains benchmark, dRPC leads at 201 ms versus NOWNodes at 216 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the dRPC vs NOWNodes 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.