1rpc vs Tenderly

Side by side OpenChainBench measurements. Identical layout, no editorial verdict, the live data leads. Each panel surfaces the aggregate plus the chain and region breakdowns when the underlying bench exposes them, straight from the Prometheus queries that drive the parent benchmark pages.

Read methodology Last measured Wed, 01 Jul 2026 15:08:11 UTCWindow: rolling 24h1 shared benchmark

1rpc

Privacy-preserving public RPC by Automata Network. Strips client metadata before forwarding to upstream node operators; load-balanced across providers.

Tenderly

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 7 more EVM chains

RPCs

1rpc

Trails

138 ms

p99: 8.00 s
rank: #11
samples: 69,122

Tenderly

Leads

121 ms

p99: 777 ms
rank: #8
samples: 77,758

Per chain · per region

Chain	Provider	US-East	EU-West	Singapore	Aggregate
Ethereum	1rpc	33 ms	119 ms	263 ms	138 ms
Ethereum	Tenderly	8 ms	15 ms	235 ms	86 ms
Polygon	1rpc	32 ms	121 ms	264 ms	139 ms
Polygon	Tenderly	103 ms	22 ms	332 ms	152 ms
Arbitrum	1rpc	33 ms	118 ms	261 ms	137 ms
Arbitrum	Tenderly	9 ms	17 ms	237 ms	88 ms
Optimism	1rpc	35 ms	119 ms	263 ms	139 ms
Optimism	Tenderly	9 ms	18 ms	237 ms	88 ms
Avalanche	1rpc	32 ms	120 ms	263 ms	138 ms
Avalanche	Tenderly	99 ms	18 ms	327 ms	148 ms
Linea	1rpc	32 ms	121 ms	264 ms	139 ms
Linea	Tenderly	97 ms	16 ms	325 ms	146 ms
Scroll	1rpc	33 ms	118 ms	263 ms	138 ms
Scroll	Tenderly	97 ms	16 ms	325 ms	146 ms
Mantle	1rpc	32 ms	121 ms	263 ms	139 ms
Mantle	Tenderly	98 ms	18 ms	326 ms	147 ms

How this pair was selected

A pair is published when all four conditions hold. Both providers run in the same OpenChainBench benchmark for at least seven consecutive days. Each provider has at least 1000 samples in the measurement window. The head to head query has observable third party search demand. Both providers have a public /products/[slug] page on OCB. The full pair ledger is versioned in the public repo so the methodology is externally verifiable.