PublicNode vs RpcNode

PublicNode leads on all 7 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (88 ms vs 305 ms), Ethereum RPC endpoints (85 ms vs 166 ms), Avalanche RPC endpoints (82 ms vs 349 ms), BNB Chain RPC endpoints (82 ms vs 337 ms). Data as of 2026-11-19 UTC.

Read methodology Last measured Window: rolling 24h7 shared benchmarks
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

Headline: All chains

PublicNode

Leads

88 ms

p99
273 ms
rank
#3
samples
224,573

RpcNode

Trails

305 ms

p99
1.21 s
rank
#12
samples
17,985
RPC latency
PublicNoden/aRpcNoden/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.

Frequently asked questions

PublicNode vs RpcNode: which one is better?

PublicNode and RpcNode are compared on 7 shared OpenChainBench benchmarks. 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, PublicNode or RpcNode?

On the Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains benchmark, PublicNode leads at 88 ms versus RpcNode at 305 ms. Live measurement is updated continuously by the OpenChainBench harness.

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