1RPC vs thirdweb

1RPC leads on both live benchmarks. 1RPC wins on Mode RPC endpoints (217 ms vs 451 ms), Manta Pacific RPC endpoints (202 ms vs 455 ms). Data as of 2026-10-22 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
1RPC logo
1RPC

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

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

Mode RPC endpoints: free public URLs by latency

RPCs

1RPC

Leads

217 ms

p99
3.87 s
rank
—
samples
4,324

thirdweb

Trails

451 ms

p99
1.16 s
rank
—
samples
4,333

Per region

Region1RPCthirdweb
US-East155 ms265 ms
EU-West161 ms505 ms
Singapore334 ms583 ms
RPC latency
1RPCn/athirdwebn/a

Frequently asked questions

1RPC vs thirdweb: which one is better?

1RPC and thirdweb are compared on 2 shared OpenChainBench benchmarks. 1RPC leads on Mode RPC endpoints. See the live table on this page for every metric.

Which is faster, 1RPC or thirdweb?

On the Mode RPC endpoints benchmark, 1RPC leads at 217 ms versus thirdweb at 451 ms. Live measurement is updated continuously by the OpenChainBench harness.

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