Ankr vs PublicNode

Ankr leads on 2 of 3 shared benchmarks, PublicNode on 1. Ankr wins on Kava RPC endpoints (39 ms vs 61 ms), Story RPC endpoints (36 ms vs 72 ms). PublicNode wins on Chiliz Chain RPC endpoints (60 ms vs 72 ms). Data as of 2026-11-02 UTC.

Read methodology Last measured Window: rolling 24h3 shared benchmarks
Ankr logo
Ankr

Multi-chain RPC service covering 65+ chains on the freemium tier. One API key across chains; some networks are premium-gated.

PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

Side by side measurements

Kava RPC endpoints: free public URLs by latency

RPCs

Ankr

Leads

39 ms

p99
103 ms
rank
#1
samples
4,315

PublicNode

Trails

61 ms

p99
253 ms
rank
#2
samples
4,314

Per region

RegionAnkrPublicNode
US-East12 ms28 ms
EU-West96 ms35 ms
Singapore9 ms119 ms
RPC latency
Ankrn/aPublicNoden/a

Story RPC endpoints: free public URLs by latency

RPCs

Ankr

Leads

36 ms

p99
121 ms
rank
#1
samples
4,323

PublicNode

Trails

72 ms

p99
366 ms
rank
#3
samples
4,315

Per region

RegionAnkrPublicNode
US-East9 ms46 ms
EU-West93 ms43 ms
Singapore6 ms124 ms
RPC latency
Ankrn/aPublicNoden/a

Frequently asked questions

Ankr vs PublicNode: which one is better?

Ankr and PublicNode are compared on 3 shared OpenChainBench benchmarks. Ankr leads on Kava RPC endpoints. PublicNode leads on Chiliz Chain RPC endpoints. See the live table on this page for every metric.

Which is faster on rpc latency, Ankr or PublicNode?

On the Kava RPC endpoints benchmark, Ankr leads at 39 ms versus PublicNode at 61 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the Ankr vs PublicNode comparison measured?

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.

How this pair was selected

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.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.