MeowRPC vs PublicNode

MeowRPC leads on 1 of 4 shared benchmarks, PublicNode on 3. MeowRPC wins on Most reliable free public RPC, correctness incidents across 7 EVM chains (91 vs 106). PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (107 ms vs 186 ms), Ethereum RPC endpoints (73 ms vs 174 ms), Arbitrum RPC endpoints (70 ms vs 198 ms). Data as of 2026-10-02 UTC.

Read methodology Last measured Window: rolling 24h4 shared benchmarks
MeowRPC logo
MeowRPC

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

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

MeowRPC

Trails

186 ms

p99
421 ms
rank
#10
samples
8,635

PublicNode

Leads

107 ms

p99
560 ms
rank
#3
samples
306,235

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumMeowRPC180 ms87 ms255 ms174 ms
PublicNode19 ms23 ms177 ms73 ms
ArbitrumMeowRPC206 ms114 ms274 ms198 ms
PublicNode15 ms23 ms174 ms70 ms
RPC latency
MeowRPCn/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

MeowRPC

Leads

91

p99
6
rank
—
samples
176

PublicNode

Trails

106

p99
4
rank
#5
samples
568

Per chain

ChainMeowRPCPublicNode
Ethereum473
Arbitrum4442
Reliability incidents
MeowRPCn/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

MeowRPC vs PublicNode: which one is better?

MeowRPC and PublicNode are compared on 4 shared OpenChainBench benchmarks. MeowRPC leads on Most reliable free public RPC, correctness incidents across 7 EVM chains. 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 on reliability incidents, MeowRPC or PublicNode?

On the Most reliable free public RPC, correctness incidents across 7 EVM chains benchmark, MeowRPC leads at 91 versus PublicNode at 106. Live measurement is updated continuously by the OpenChainBench harness.

Which is faster on rpc latency, MeowRPC or PublicNode?

On the Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains benchmark, PublicNode leads at 107 ms versus MeowRPC at 186 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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.