dRPC vs Nodies

dRPC leads on 4 of 6 shared benchmarks, Nodies on 2. dRPC wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (214 ms vs 226 ms), Fastest free Ethereum RPC, live no-key endpoint latency (123 ms vs 187 ms), Fastest free Base RPC, live no-key endpoint latency (167 ms vs 268 ms), Fastest free Optimism RPC, live no-key endpoint latency (165 ms vs 271 ms). Nodies wins on Fastest free Arbitrum RPC, live no-key endpoint latency (179 ms vs 356 ms), Most reliable free public RPC, correctness incidents across 7 EVM chains (164 vs 193).

Read methodology Last measured Window: rolling 24h8 shared benchmarks
dRPC logo
dRPC

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

Nodies logo
Nodies

Nodies is the surviving public-RPC frontend for POKT Network's decentralized infrastructure. Per-chain subdomains like `eth-pokt.nodies.app`, `polygon-pokt.nodies.app`, `arb-pokt.nodies.app`. Covers most major EVM chains no-key.

Side by side measurements

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

RPCs

dRPC

Leads

214 ms

p99
580 ms
rank
#4
samples
263,087

Nodies

Trails

226 ms

p99
395 ms
rank
#5
samples
25,904

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumdRPC53 ms163 ms162 ms126 ms
Nodies185 ms186 ms189 ms187 ms
ArbitrumdRPC359 ms357 ms353 ms356 ms
Nodies178 ms178 ms179 ms178 ms
OptimismdRPC164 ms166 ms164 ms165 ms
Nodies271 ms272 ms270 ms271 ms
BasedRPC168 ms168 ms167 ms167 ms
Nodies267 ms269 ms268 ms268 ms

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.

Most reliable free public RPC, correctness incidents across 7 EVM chains

RPCs

dRPC

Trails

193

p99
26
rank
#5
samples
576

Nodies

Leads

164

p99
0.250
rank
#4
samples
496

A zero row means no incident was caught in the window, not a proof of correctness. Most providers post zero most days; this bench exists for the days they do not, and for the errors: a blocked eth_getLogs or a balance read gated behind a paid key at 40 blocks of depth counts as an incident because it is one from the caller's seat.

Rolling 24h · Reliability incidentsRaw JSON

Frequently asked questions

dRPC vs Nodies: which one is better?

dRPC and Nodies are compared on 8 shared OpenChainBench benchmarks. dRPC leads on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains. Nodies leads on Fastest free Arbitrum RPC, live no-key endpoint latency. See the live table on this page for every metric.

Which is faster, dRPC or Nodies?

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

Which is faster, dRPC or Nodies?

On the Fastest free Arbitrum RPC, live no-key endpoint latency benchmark, Nodies leads at 179 ms versus dRPC at 356 ms. Live measurement is updated continuously by the OpenChainBench harness.

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

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.