Ankr leads on all 4 live benchmarks. Ankr wins on Fastest free Kava RPC, live no-key EVM endpoint latency (33 ms vs 623 ms), Fastest free Swellchain RPC, live no-key EVM endpoint latency (7 ms vs 678 ms), Fastest free Flare RPC, live no-key EVM endpoint latency (44 ms vs 641 ms), Fastest free Core Chain RPC, live no-key EVM endpoint latency (6 ms vs 635 ms).
Multi-chain RPC service covering 65+ chains on the freemium tier. One API key across chains; some networks are premium-gated.
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).
Ankr
Leads33 ms
thirdweb
Trails623 ms
Per region
| Region | Ankr | thirdweb |
|---|---|---|
| US-East | 12 ms | 614 ms |
| EU-West | 43 ms | 631 ms |
| Singapore | 43 ms | 623 ms |
Ankr
Leads7 ms
thirdweb
Trails678 ms
Per region
| Region | Ankr | thirdweb |
|---|---|---|
| US-East | 6 ms | 685 ms |
| EU-West | 7 ms | 673 ms |
| Singapore | 7 ms | 675 ms |
Ankr
Leads44 ms
thirdweb
Trails641 ms
Per region
| Region | Ankr | thirdweb |
|---|---|---|
| US-East | 44 ms | 639 ms |
| EU-West | 40 ms | 637 ms |
| Singapore | 49 ms | 648 ms |
Ankr
Leads6 ms
thirdweb
Trails635 ms
Per region
| Region | Ankr | thirdweb |
|---|---|---|
| US-East | 6 ms | 645 ms |
| EU-West | 6 ms | 628 ms |
| Singapore | 6 ms | 631 ms |
Ankr
No data in window
thirdweb
Trails755 ms
Ankr and thirdweb are compared on 5 shared OpenChainBench benchmarks. Ankr leads on Fastest free Kava RPC, live no-key EVM endpoint latency. See the live table on this page for every metric.
On the Fastest free Kava RPC, live no-key EVM endpoint latency benchmark, Ankr leads at 33 ms versus thirdweb at 623 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.
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.