OpenChainBench

Binance vs PublicNode

Binance leads on all 3 live benchmarks. Binance wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (33 ms vs 107 ms), BNB Chain RPC endpoints (33 ms vs 72 ms), Most reliable free public RPC, correctness incidents across 7 EVM chains (38 vs 106). Data as of 2026-10-02 UTC.

Read methodology Last measured Window: rolling 24h3 shared benchmarks
Binance logo
Binance

Binance appears twice on OpenChainBench: the official BNB Chain RPC endpoints it operates (`bsc-dataseed1.binance.org` and siblings, round-robin) and Binance Wallet, its self-custody Web3 wallet, whose in-app swap routes through one router contract on BNB Chain, Ethereum and Base and settles on on-chain pools.

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

Binance

Leads

33 ms

p99
171 ms
rank
#1
samples
4,316

PublicNode

Trails

107 ms

p99
560 ms
rank
#3
samples
306,235

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
BNB ChainBinance6 ms18 ms74 ms33 ms
PublicNode17 ms24 ms174 ms72 ms
RPC latency
Binancen/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.

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

RPCs

Binance

Leads

38

rank
—
samples
74provisional

PublicNode

Trails

106

p99
4
rank
#5
samples
568

Per chain

ChainBinancePublicNode
BNB Chain381
Reliability incidents
Binancen/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

Frequently asked questions

Binance vs PublicNode: which one is better?

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

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

How is the Binance 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.