PublicNode vs Tenderly Gateway

PublicNode leads on all 20 live benchmarks. PublicNode wins on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (215 ms vs 307 ms), Fastest free Ethereum RPC, live no-key endpoint latency (133 ms vs 241 ms), Fastest free Arbitrum RPC, live no-key endpoint latency (90 ms vs 234 ms), Fastest free Base RPC, live no-key endpoint latency (129 ms vs 240 ms).

Read methodology Last measured Window: rolling 24h22 shared benchmarks
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.

Tenderly Gateway logo
Tenderly Gateway

Tenderly's public gateway exposes a no-key JSON-RPC endpoint per chain at `gateway.tenderly.co/public/<slug>`. Covers Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, Linea, Scroll and Mantle. The same Tenderly platform behind the keyed Web3 dev suite.

Side by side measurements

Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (plus Solana and Polkadot)

RPCs

PublicNode

Leads

215 ms

p99
1.22 s
rank
#3
samples
270,488

Tenderly Gateway

Trails

307 ms

p99
385 ms
rank
#9
samples
124,835

Per chain · per region

ChainProviderUS-EastEU-WestSingaporeAggregate
EthereumPublicNode111 ms144 ms146 ms134 ms
Tenderly Gateway240 ms241 ms242 ms241 ms
PolygonPublicNode98 ms93 ms95 ms96 ms
Tenderly Gateway326 ms327 ms327 ms327 ms
ArbitrumPublicNode93 ms88 ms91 ms90 ms
Tenderly Gateway234 ms234 ms234 ms234 ms
OptimismPublicNode94 ms89 ms88 ms90 ms
Tenderly Gateway234 ms234 ms235 ms234 ms
BasePublicNode108 ms143 ms142 ms131 ms
Tenderly Gateway240 ms240 ms240 ms240 ms
AvalanchePublicNode96 ms94 ms93 ms94 ms
Tenderly Gateway325 ms325 ms325 ms325 ms
LineaPublicNode92 ms87 ms93 ms90 ms
Tenderly Gateway322 ms322 ms323 ms322 ms
ScrollPublicNode94 ms90 ms91 ms92 ms
Tenderly Gateway322 ms322 ms322 ms322 ms
MantlePublicNode94 ms85 ms86 ms88 ms
Tenderly Gateway325 ms325 ms326 ms325 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

PublicNode

Trails

84

p99
54.0K
rank
#4
samples
574

Tenderly Gateway

No data in window

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

PublicNode vs Tenderly Gateway: which one is better?

PublicNode and Tenderly Gateway are compared on 22 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, PublicNode or Tenderly Gateway?

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

How is the PublicNode vs Tenderly Gateway 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.