Ankr leads on 1 of 3 shared benchmarks, PublicNode on 2. Ankr wins on Fastest free Kava RPC, live no-key EVM endpoint latency (39 ms vs 46 ms). PublicNode wins on Fastest free Story RPC, live no-key EVM endpoint latency (51 ms vs 93 ms), Fastest free Chiliz Chain RPC, live no-key endpoint latency (48 ms vs 73 ms).
Multi-chain RPC service covering 65+ chains on the freemium tier. One API key across chains; some networks are premium-gated.
Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.
Ankr
Leads39 ms
PublicNode
Trails46 ms
Per region
| Region | Ankr | PublicNode |
|---|---|---|
| US-East | 12 ms | 17 ms |
| EU-West | 94 ms | 26 ms |
| Singapore | 11 ms | 96 ms |
Ankr
Trails93 ms
PublicNode
Leads51 ms
Per region
| Region | Ankr | PublicNode |
|---|---|---|
| US-East | 9 ms | 22 ms |
| EU-West | 91 ms | 29 ms |
| Singapore | 179 ms | 102 ms |
Ankr
Trails73 ms
PublicNode
Leads48 ms
Per region
| Region | Ankr | PublicNode |
|---|---|---|
| US-East | 10 ms | 18 ms |
| EU-West | 17 ms | 27 ms |
| Singapore | 192 ms | 98 ms |
Ankr and PublicNode are compared on 3 shared OpenChainBench benchmarks. Ankr leads on Fastest free Kava RPC, live no-key EVM endpoint latency. PublicNode leads on Fastest free Story 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 39 ms versus PublicNode at 46 ms. Live measurement is updated continuously by the OpenChainBench harness.
On the Fastest free Story RPC, live no-key EVM endpoint latency benchmark, PublicNode leads at 51 ms versus Ankr at 93 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.