Arbitrum vs Tenderly Gateway

Split decision: Arbitrum leads on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains (278 ms vs 307 ms); Tenderly Gateway leads on Fastest free Arbitrum RPC, live no-key endpoint latency (239 ms vs 278 ms).

Read methodology Last measured Window: rolling 24h3 shared benchmarks
Arbitrum logo
Arbitrum

Optimistic rollup built on Nitro stack with a fast-finality sequencer. Sub-second block times (~250 ms) via a 250 ms default block interval, far below the 2 s OP Stack convention. 7-day fraud-proof window for L1 finality.

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

Arbitrum

Leads

278 ms

p99
2.37 s
rank
#7
samples
4,319

Tenderly Gateway

Trails

307 ms

p99
385 ms
rank
#9
samples
125,194

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

Arbitrum

Trails

2

rank
#2
samples
82provisional

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

Arbitrum vs Tenderly Gateway: which one is better?

Arbitrum and Tenderly Gateway are compared on 3 shared OpenChainBench benchmarks. Arbitrum leads on Fastest free public RPC for Ethereum, BNB, Polygon and 23 more chains. Tenderly Gateway leads on Fastest free Arbitrum RPC, live no-key endpoint latency. See the live table on this page for every metric.

Which is faster, Arbitrum or Tenderly Gateway?

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

Which is faster, Arbitrum or Tenderly Gateway?

On the Fastest free Arbitrum RPC, live no-key endpoint latency benchmark, Tenderly Gateway leads at 239 ms versus Arbitrum at 278 ms. Live measurement is updated continuously by the OpenChainBench harness.

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

Related comparisons

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.