Fastest free Cyber RPC, live no-key EVM endpoint latency
RPCsAltLayer
Leads174 ms
- p99
- 240 ms
- rank
- #2
- samples
- 1,218
Thirdweb
No data in window
Per region
| Region | AltLayer | Thirdweb |
|---|---|---|
| US-East | 173 ms | 620 ms |
| EU-West | 175 ms | 652 ms |
| Singapore | 173 ms | 614 ms |
AltLayer leads on 1 of 1 shared benchmarks, Thirdweb on 0. AltLayer wins on Fastest free Cyber RPC, live no-key EVM endpoint latency (174 ms vs 629 ms).
AltLayer is a restaked rollup infrastructure provider offering managed RPC nodes for OP Stack and Arbitrum chains. Their public endpoint (cyber.alt.technology) supports Cyber Network (chain 7560) without an API key.
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).
AltLayer
Leads174 ms
Thirdweb
No data in window
Per region
| Region | AltLayer | Thirdweb |
|---|---|---|
| US-East | 173 ms | 620 ms |
| EU-West | 175 ms | 652 ms |
| Singapore | 173 ms | 614 ms |
AltLayer and Thirdweb are compared on 1 shared OpenChainBench benchmarks. AltLayer leads on Fastest free Cyber RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
On the Fastest free Cyber RPC, live no-key EVM endpoint latency benchmark, AltLayer leads at 174 ms versus Thirdweb at 629 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.