Fastest free Mode RPC, live no-key EVM endpoint latency
RPCsMode Labs
Leads176 ms
- p99
- 399 ms
- rank
- #1
- samples
- 3,748
Thirdweb
No data in window
Per region
| Region | Mode Labs | Thirdweb |
|---|---|---|
| US-East | 175 ms | 556 ms |
| EU-West | 176 ms | 562 ms |
| Singapore | 176 ms | 583 ms |
Mode Labs leads on 1 of 1 shared benchmarks, Thirdweb on 0. Mode Labs wins on Fastest free Mode RPC, live no-key EVM endpoint latency (176 ms vs 564 ms).
Mode Labs' official public RPC (mainnet.mode.network) for the OP Stack L2 in the Base / Superchain ecosystem (chain 34443). Standard EVM JSON-RPC, keyless, rate-limited per IP.
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).
Mode Labs
Leads176 ms
Thirdweb
No data in window
Per region
| Region | Mode Labs | Thirdweb |
|---|---|---|
| US-East | 175 ms | 556 ms |
| EU-West | 176 ms | 562 ms |
| Singapore | 176 ms | 583 ms |
Mode Labs and Thirdweb are compared on 1 shared OpenChainBench benchmarks. Mode Labs leads on Fastest free Mode RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
On the Fastest free Mode RPC, live no-key EVM endpoint latency benchmark, Mode Labs leads at 176 ms versus Thirdweb at 564 ms. Live measurement is updated continuously by the OpenChainBench harness.
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.
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.