OpenChainBench

dRPC vs PublicNode

dRPC leads on 6 of 33 shared benchmarks, PublicNode on 27. dRPC wins on Ethereum RPC endpoints (33 ms vs 73 ms), Arbitrum RPC endpoints (65 ms vs 70 ms), BNB Chain RPC endpoints (61 ms vs 72 ms), Polygon RPC endpoints (28 ms vs 1.81 s). PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (107 ms vs 199 ms), Base RPC endpoints (73 ms vs 82 ms), Optimism RPC endpoints (70 ms vs 81 ms), Avalanche RPC endpoints (69 ms vs 168 ms). Data as of 2026-10-02 UTC.

Read methodology Last measured Window: rolling 24h34 shared benchmarks, 33 measured on both sides
dRPC logo
dRPC

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

PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

Side by side measurements

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

RPCs

dRPC

Trails

199 ms

p99
523 ms
rank
#11
samples
305,892

PublicNode

Leads

107 ms

p99
563 ms
rank
#3
samples
306,236

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumdRPC31 ms26 ms41 ms33 ms
PublicNode19 ms23 ms177 ms73 ms
PolygondRPC42 ms26 ms15 ms28 ms
PublicNode20 ms4.62 s796 ms1.81 s
ArbitrumdRPC127 ms55 ms15 ms65 ms
PublicNode15 ms23 ms174 ms70 ms
OptimismdRPC39 ms29 ms175 ms81 ms
PublicNode14 ms23 ms173 ms70 ms
BasedRPC38 ms32 ms175 ms82 ms
PublicNode17 ms26 ms176 ms73 ms
BNB ChaindRPC135 ms32 ms17 ms61 ms
PublicNode17 ms24 ms174 ms72 ms
AvalanchedRPC93 ms172 ms239 ms168 ms
PublicNode14 ms21 ms172 ms69 ms
LineadRPC163 ms178 ms219 ms187 ms
PublicNode15 ms22 ms171 ms70 ms
ScrolldRPC161 ms173 ms226 ms187 ms
PublicNode16 ms22 ms171 ms70 ms
MantledRPC478 ms437 ms420 ms445 ms
PublicNode17 ms20 ms173 ms70 ms
RPC latency
dRPCn/aPublicNoden/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.

Optimism RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

81 ms

p99
189 ms
rank
#2
samples
4,323

PublicNode

Leads

70 ms

p99
676 ms
rank
#1
samples
4,310

Per region

RegiondRPCPublicNode
US-East39 ms14 ms
EU-West29 ms23 ms
Singapore175 ms173 ms
RPC latency
dRPCn/aPublicNoden/a

Avalanche RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

168 ms

p99
572 ms
rank
#4
samples
4,309

PublicNode

Leads

69 ms

p99
624 ms
rank
#1
samples
4,312

Per region

RegiondRPCPublicNode
US-East91 ms14 ms
EU-West172 ms21 ms
Singapore239 ms172 ms
RPC latency
dRPCn/aPublicNoden/a

Linea RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

187 ms

p99
806 ms
rank
#3
samples
4,307

PublicNode

Leads

70 ms

p99
336 ms
rank
#1
samples
4,303

Per region

RegiondRPCPublicNode
US-East163 ms15 ms
EU-West178 ms22 ms
Singapore219 ms171 ms
RPC latency
dRPCn/aPublicNoden/a

Scroll RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

187 ms

p99
618 ms
rank
#3
samples
4,323

PublicNode

Leads

70 ms

p99
203 ms
rank
#1
samples
4,316

Per region

RegiondRPCPublicNode
US-East161 ms16 ms
EU-West173 ms22 ms
Singapore226 ms171 ms
RPC latency
dRPCn/aPublicNoden/a

Mantle RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

445 ms

p99
933 ms
rank
#3
samples
4,301

PublicNode

Leads

70 ms

p99
247 ms
rank
#1
samples
4,329

Per region

RegiondRPCPublicNode
US-East478 ms17 ms
EU-West436 ms20 ms
Singapore419 ms173 ms
RPC latency
dRPCn/aPublicNoden/a

Sonic RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

182 ms

p99
660 ms
rank
#4
samples
4,300

PublicNode

Leads

69 ms

p99
235 ms
rank
#1
samples
4,297

Per region

RegiondRPCPublicNode
US-East162 ms15 ms
EU-West172 ms22 ms
Singapore212 ms171 ms
RPC latency
dRPCn/aPublicNoden/a

Gnosis RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

115 ms

p99
195 ms
rank
#3
samples
4,322

PublicNode

Leads

75 ms

p99
1.21 s
rank
#1
samples
4,313

Per region

RegiondRPCPublicNode
US-East134 ms19 ms
EU-West33 ms29 ms
Singapore178 ms178 ms
RPC latency
dRPCn/aPublicNoden/a

Celo RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

261 ms

p99
761 ms
rank
#4
samples
4,315

PublicNode

Leads

72 ms

p99
323 ms
rank
#1
samples
4,314

Per region

RegiondRPCPublicNode
US-East297 ms18 ms
EU-West220 ms23 ms
Singapore267 ms174 ms
RPC latency
dRPCn/aPublicNoden/a

Unichain RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

115 ms

p99
198 ms
rank
#3
samples
4,296

PublicNode

Leads

70 ms

p99
235 ms
rank
#1
samples
4,316

Per region

RegiondRPCPublicNode
US-East134 ms15 ms
EU-West33 ms22 ms
Singapore178 ms172 ms
RPC latency
dRPCn/aPublicNoden/a

Blast RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

187 ms

p99
1.14 s
rank
#4
samples
4,307

PublicNode

Leads

71 ms

p99
367 ms
rank
#2
samples
4,302

Per region

RegiondRPCPublicNode
US-East168 ms17 ms
EU-West177 ms24 ms
Singapore218 ms172 ms
RPC latency
dRPCn/aPublicNoden/a

The chain-official rpc.blast.io figure on this page reflects GCP co-location with our three probes, not a typical client path. Compare the gateways on the per-region tabs before choosing a primary.

Taiko RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

152 ms

p99
361 ms
rank
#4
samples
4,319

PublicNode

Leads

71 ms

p99
247 ms
rank
#1
samples
4,314

Per region

RegiondRPCPublicNode
US-East60 ms18 ms
EU-West155 ms21 ms
Singapore241 ms174 ms
RPC latency
dRPCn/aPublicNoden/a

Berachain RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

148 ms

p99
328 ms
rank
#3
samples
4,299

PublicNode

Leads

73 ms

p99
204 ms
rank
#2
samples
4,315

Per region

RegiondRPCPublicNode
US-East46 ms19 ms
EU-West157 ms26 ms
Singapore241 ms173 ms
RPC latency
dRPCn/aPublicNoden/a

Cronos RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

91 ms

p99
216 ms
rank
#3
samples
4,299

PublicNode

Leads

70 ms

p99
246 ms
rank
#2
samples
4,303

Per region

RegiondRPCPublicNode
US-East56 ms16 ms
EU-West37 ms20 ms
Singapore179 ms174 ms
RPC latency
dRPCn/aPublicNoden/a

Fraxtal RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

116 ms

p99
196 ms
rank
#4
samples
4,301

PublicNode

Leads

72 ms

p99
221 ms
rank
#2
samples
4,323

Per region

RegiondRPCPublicNode
US-East135 ms19 ms
EU-West35 ms21 ms
Singapore177 ms174 ms
RPC latency
dRPCn/aPublicNoden/a

Soneium RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

235 ms

p99
462 ms
rank
#4
samples
4,297

PublicNode

Leads

71 ms

p99
266 ms
rank
#2
samples
4,321

Per region

RegiondRPCPublicNode
US-East252 ms17 ms
EU-West250 ms22 ms
Singapore203 ms174 ms
RPC latency
dRPCn/aPublicNoden/a

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

RPCs

dRPC

Trails

157

p99
0.894
rank
#6
samples
570

PublicNode

Leads

104

p99
4
rank
#5
samples
570

Per chain

ChaindRPCPublicNode
Ethereum23
Arbitrum2442
BNB Chain491
Reliability incidents
dRPCn/aPublicNoden/a

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

opBNB RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

407 ms

p99
1.28 s
rank
#3
samples
4,308

PublicNode

Leads

72 ms

p99
258 ms
rank
#2
samples
4,316

Per region

RegiondRPCPublicNode
US-East418 ms17 ms
EU-West381 ms24 ms
Singapore420 ms176 ms
RPC latency
dRPCn/aPublicNoden/a

Kava RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

183 ms

p99
493 ms
rank
#4
samples
4,295

PublicNode

Leads

70 ms

p99
245 ms
rank
#2
samples
4,306

Per region

RegiondRPCPublicNode
US-East84 ms17 ms
EU-West201 ms21 ms
Singapore264 ms173 ms
RPC latency
dRPCn/aPublicNoden/a

Metis RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

153 ms

p99
338 ms
rank
#3
samples
4,295

PublicNode

Leads

71 ms

p99
244 ms
rank
#1
samples
4,329

Per region

RegiondRPCPublicNode
US-East52 ms17 ms
EU-West164 ms24 ms
Singapore242 ms173 ms
RPC latency
dRPCn/aPublicNoden/a

Kusama RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

448 ms

p99
660 ms
rank
#3
samples
4,319

PublicNode

Leads

76 ms

p99
302 ms
rank
#2
samples
4,315

Per region

RegiondRPCPublicNode
US-East538 ms23 ms
EU-West94 ms27 ms
Singapore712 ms177 ms
RPC latency
dRPCn/aPublicNoden/a

Bitcoin RPC endpoints: free public URLs by latency

RPCs

dRPC

Trails

138 ms

p99
234 ms
rank
#2
samples
4,300

PublicNode

Leads

70 ms

p99
199 ms
rank
#1
samples
4,323

Per region

RegiondRPCPublicNode
US-East173 ms18 ms
EU-West58 ms20 ms
Singapore183 ms172 ms
RPC latency
dRPCn/aPublicNoden/a

Frequently asked questions

dRPC vs PublicNode: which one is better?

dRPC and PublicNode are compared on 34 shared OpenChainBench benchmarks. dRPC leads on Ethereum RPC endpoints. PublicNode 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 on rpc latency, dRPC or PublicNode?

On the Ethereum RPC endpoints benchmark, dRPC leads at 33 ms versus PublicNode at 73 ms. Live measurement is updated continuously by the OpenChainBench harness.

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