Celo (Forno) vs Tenderly Gateway

Celo (Forno) leads on the only live benchmark. Celo (Forno) wins on Fastest free Celo RPC, live no-key endpoint latency (199 ms vs 329 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
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 Celo RPC, live no-key endpoint latency

RPCs

Celo (Forno)

Leads

199 ms

p99
564 ms
rank
#1
samples
4,317

Tenderly Gateway

Trails

329 ms

p99
370 ms
rank
#4
samples
4,313

Per region

RegionCelo (Forno)Tenderly Gateway
US-East199 ms330 ms
EU-West198 ms330 ms
Singapore199 ms329 ms

Frequently asked questions

Celo (Forno) vs Tenderly Gateway: which one is better?

Celo (Forno) and Tenderly Gateway are compared on 1 shared OpenChainBench benchmarks. Celo (Forno) leads on Fastest free Celo RPC, live no-key endpoint latency. See the live table on this page for every metric.

Which is faster, Celo (Forno) or Tenderly Gateway?

On the Fastest free Celo RPC, live no-key endpoint latency benchmark, Celo (Forno) leads at 199 ms versus Tenderly Gateway at 329 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the Celo (Forno) 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.