Flashbots Protect vs PublicNode

PublicNode leads on both live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (239 ms vs 707 ms), Most reliable free public RPC, correctness incidents across 7 EVM chains (64 vs 84).

Read methodology Last measured Window: rolling 24h2 shared benchmarks
Flashbots Protect logo
Flashbots Protect

Flashbots Protect RPC sends transactions through a private mempool, shielding them from sandwich attacks. Read calls go to a standard Ethereum node behind the proxy.

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

Flashbots Protect

Trails

707 ms

p99
1.02 s
rank
#12
samples
4,318

PublicNode

Leads

239 ms

p99
2.05 s
rank
#4
samples
276,084

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumFlashbots Protect728 ms722 ms672 ms707 ms
PublicNode148 ms112 ms106 ms122 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.

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

RPCs

Flashbots Protect

Trails

84

rank
samples
84provisional

PublicNode

Leads

64

p99
57.1K
rank
#3
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.

Rolling 24h · Reliability incidentsRaw JSON

Frequently asked questions

Flashbots Protect vs PublicNode: which one is better?

Flashbots Protect and PublicNode are compared on 2 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, Flashbots Protect or PublicNode?

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

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