Nodies vs PublicNode

PublicNode leads on all 5 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (83 ms vs 138 ms), Ethereum RPC endpoints (79 ms vs 141 ms), Arbitrum RPC endpoints (81 ms vs 138 ms), Base RPC endpoints (78 ms vs 135 ms). Data as of 2026-11-16 UTC.

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

Headline: All chains

Nodies

Trails

138 ms

p99
205 ms
rank
#7
samples
17,278

PublicNode

Leads

83 ms

p99
254 ms
rank
#3
samples
224,607

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumNodies20 ms121 ms281 ms141 ms
PublicNode29 ms30 ms177 ms79 ms
ArbitrumNodies19 ms117 ms277 ms138 ms
PublicNode36 ms29 ms176 ms81 ms
OptimismNodies19 ms120 ms281 ms140 ms
PublicNode16 ms23 ms179 ms73 ms
BaseNodies29 ms97 ms279 ms135 ms
PublicNode28 ms29 ms177 ms78 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

140 ms

p99
176 ms
rank
#6
samples
4,321

PublicNode

Leads

73 ms

p99
165 ms
rank
#1
samples
4,320

Per region

RegionNodiesPublicNode
US-East19 ms16 ms
EU-West120 ms23 ms
Singapore281 ms179 ms
RPC latency
Nodiesn/aPublicNoden/a

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

RPCs

Headline: All chains

Nodies

No data in window

PublicNode

Trails

1

p99
0
rank
#5
samples
576
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 6 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 83 ms versus Nodies at 138 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.