MeowRPC vs PublicNode

PublicNode leads on all 4 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (197 ms vs 271 ms), Fastest free Ethereum RPC, live no-key endpoint latency (101 ms vs 264 ms), Fastest free Arbitrum RPC, live no-key endpoint latency (90 ms vs 277 ms), Most reliable free public RPC, correctness incidents across 7 EVM chains (45 vs 84).

Read methodology Last measured Tue, 18 Aug 2026 00:29:39 UTCWindow: rolling 24h4 shared benchmarks

MeowRPC

Free public RPC service covering Ethereum, Base, Arbitrum, Optimism and other EVM chains. No registration required, modest rate limits per IP.

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

MeowRPC

Trails

271 ms

p99: 723 ms
rank: #8
samples: 8,632

PublicNode

Leads

197 ms

p99: 851 ms
rank: #3
samples: 267,574

Per chain · per region

Chain	Provider	US-East	EU-West	Singapore	Aggregate
Ethereum	MeowRPC	268 ms	262 ms	262 ms	264 ms
Ethereum	PublicNode	100 ms	101 ms	101 ms	101 ms
Arbitrum	MeowRPC	276 ms	276 ms	279 ms	277 ms
Arbitrum	PublicNode	91 ms	87 ms	93 ms	90 ms

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.

Fastest free Ethereum RPC, live no-key endpoint latency

RPCs

MeowRPC

Trails

264 ms

p99: 521 ms
rank: #5
samples: 4,316

PublicNode

Leads

101 ms

p99: 418 ms
rank: #1
samples: 4,316

Per region

Region	MeowRPC	PublicNode
US-East	267 ms	100 ms
EU-West	262 ms	101 ms
Singapore	262 ms	102 ms

Fastest free Arbitrum RPC, live no-key endpoint latency

RPCs

MeowRPC

Trails

277 ms

p99: 926 ms
rank: #6
samples: 4,315

PublicNode

Leads

90 ms

p99: 495 ms
rank: #1
samples: 4,315

Per region

Region	MeowRPC	PublicNode
US-East	276 ms	91 ms
EU-West	276 ms	87 ms
Singapore	279 ms	93 ms

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

RPCs

MeowRPC

Trails

p99: 20
rank: #3
samples: 168

PublicNode

Leads

p99: 52.7K
rank: #2
samples: 576

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.

Frequently asked questions

MeowRPC vs PublicNode: which one is better?

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

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

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