Tenderly Gateway vs thirdweb

Tenderly Gateway leads on all 6 live benchmarks. Tenderly Gateway wins on Ronin RPC endpoints (105 ms vs 541 ms), Immutable zkEVM RPC endpoints (140 ms vs 525 ms), ApeChain RPC endpoints (151 ms vs 481 ms), Lisk RPC endpoints (104 ms vs 699 ms). Data as of 2026-10-25 UTC.

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

thirdweb logo
thirdweb

ThirdWeb operates a keyless public RPC gateway at `<chainid>.rpc.thirdweb.com` covering 2000+ EVM chains via chain-id routing. Free tier is rate-limited per IP with no signup; paid tiers unlock higher throughput and dedicated endpoints. Used keyless across 13 chains on the RPC latency cluster (arbitrum, ethereum, polygon, optimism, base, bnb, avalanche, linea, worldchain, kaia, ink, opbnb + more).

Side by side measurements

Ronin RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

105 ms

p99
121 ms
rank
#1
samples
4,305

thirdweb

Trails

541 ms

p99
980 ms
rank
—
samples
4,321

Per region

RegionTenderly Gatewaythirdweb
US-East28 ms339 ms
EU-West27 ms601 ms
Singapore260 ms682 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

Immutable zkEVM RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

140 ms

p99
158 ms
rank
#2
samples
4,305

thirdweb

Trails

525 ms

p99
625 ms
rank
—
samples
4,318

Per region

RegionTenderly Gatewaythirdweb
US-East28 ms342 ms
EU-West135 ms574 ms
Singapore256 ms663 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

ApeChain RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

151 ms

p99
219 ms
rank
#2
samples
4,316

thirdweb

Trails

481 ms

p99
827 ms
rank
—
samples
4,311

Per region

RegionTenderly Gatewaythirdweb
US-East97 ms293 ms
EU-West24 ms553 ms
Singapore330 ms592 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

Lisk RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

104 ms

p99
117 ms
rank
#2
samples
4,321

thirdweb

Trails

699 ms

p99
1.19 s
rank
—
samples
4,310

Per region

RegionTenderly Gatewaythirdweb
US-East27 ms580 ms
EU-West27 ms709 ms
Singapore259 ms807 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

BOB RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

152 ms

p99
178 ms
rank
#2
samples
4,321

thirdweb

Trails

482 ms

p99
627 ms
rank
—
samples
4,320

Per region

RegionTenderly Gatewaythirdweb
US-East99 ms273 ms
EU-West27 ms559 ms
Singapore331 ms616 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

Katana RPC endpoints: free public URLs by latency

RPCs

Tenderly Gateway

Leads

122 ms

p99
142 ms
rank
#1
samples
4,326

thirdweb

Trails

475 ms

p99
688 ms
rank
—
samples
4,314

Per region

RegionTenderly Gatewaythirdweb
US-East8 ms278 ms
EU-West115 ms527 ms
Singapore241 ms620 ms
RPC latency
Tenderly Gatewayn/athirdwebn/a

Frequently asked questions

Tenderly Gateway vs thirdweb: which one is better?

Tenderly Gateway and thirdweb are compared on 6 shared OpenChainBench benchmarks. Tenderly Gateway leads on Ronin RPC endpoints. See the live table on this page for every metric.

Which is faster, Tenderly Gateway or thirdweb?

On the Ronin RPC endpoints benchmark, Tenderly Gateway leads at 105 ms versus thirdweb at 541 ms. Live measurement is updated continuously by the OpenChainBench harness.

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