Nodies vs PublicNode

PublicNode leads on all 6 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (108 ms vs 140 ms), Ethereum RPC endpoints (73 ms vs 141 ms), Arbitrum RPC endpoints (70 ms vs 140 ms), Base RPC endpoints (73 ms vs 137 ms). Data as of 2026-10-02 UTC.

Read methodology Last measured Window: rolling 24h8 shared benchmarks, 6 measured on both sides
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.

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

Nodies

Trails

140 ms

p99
256 ms
rank
#7
samples
25,909

PublicNode

Leads

108 ms

p99
556 ms
rank
#3
samples
306,232

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumNodies20 ms117 ms285 ms141 ms
PublicNode19 ms23 ms177 ms73 ms
ArbitrumNodies19 ms118 ms282 ms140 ms
PublicNode15 ms23 ms174 ms70 ms
OptimismNodies20 ms117 ms285 ms141 ms
PublicNode14 ms23 ms173 ms70 ms
BaseNodies19 ms111 ms280 ms137 ms
PublicNode17 ms26 ms177 ms73 ms
RPC latency
Nodiesn/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

Nodies

Trails

141 ms

p99
239 ms
rank
#4
samples
4,325

PublicNode

Leads

70 ms

p99
676 ms
rank
#1
samples
4,310

Per region

RegionNodiesPublicNode
US-East20 ms14 ms
EU-West117 ms23 ms
Singapore285 ms173 ms
RPC latency
Nodiesn/aPublicNoden/a

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

RPCs

Nodies

Trails

165

p99
0
rank
#7
samples
494

PublicNode

Leads

106

p99
4
rank
#5
samples
568

Per chain

ChainNodiesPublicNode
Ethereum13
Reliability incidents
Nodiesn/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

Nodies vs PublicNode: which one is better?

Nodies and PublicNode are compared on 8 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, Nodies or PublicNode?

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

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