Ankr leads on all 6 live benchmarks. Ankr wins on Fastest free Kava RPC, live no-key EVM endpoint latency (42 ms vs 245 ms), Fastest free Swellchain RPC, live no-key EVM endpoint latency (7 ms vs 171 ms), Fastest free Flare RPC, live no-key EVM endpoint latency (44 ms vs 239 ms), Fastest free Core Chain RPC, live no-key EVM endpoint latency (6 ms vs 168 ms).
Multi-chain RPC service covering 65+ chains on the freemium tier. One API key across chains; some networks are premium-gated.
Decentralized RPC mesh routing requests across third-party node providers with consensus checks. Free public tier plus higher-tier authenticated access.
Ankr
Leads42 ms
dRPC
Trails245 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 40 ms | 246 ms |
| EU-West | 43 ms | 245 ms |
| Singapore | 43 ms | 246 ms |
Ankr
Leads7 ms
dRPC
Trails171 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 6 ms | 173 ms |
| EU-West | 7 ms | 168 ms |
| Singapore | 7 ms | 172 ms |
Ankr
Leads44 ms
dRPC
Trails239 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 45 ms | 238 ms |
| EU-West | 41 ms | 239 ms |
| Singapore | 47 ms | 239 ms |
Ankr
Leads6 ms
dRPC
Trails168 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 6 ms | 167 ms |
| EU-West | 6 ms | 169 ms |
| Singapore | 6 ms | 168 ms |
Ankr
Leads7 ms
dRPC
Trails293 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 7 ms | 295 ms |
| EU-West | 7 ms | 290 ms |
| Singapore | 6 ms | 296 ms |
Ankr
Leads5 ms
dRPC
Trails223 ms
Per region
| Region | Ankr | dRPC |
|---|---|---|
| US-East | 5 ms | 215 ms |
| EU-West | 6 ms | 232 ms |
| Singapore | 6 ms | 213 ms |
Ankr and dRPC are compared on 6 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 42 ms versus dRPC at 245 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.