ecostake vs PublicNode

PublicNode leads on both live benchmarks. PublicNode wins on Cosmos Hub RPC endpoints (58 ms vs 139 ms), Akash Network RPC endpoints (65 ms vs 183 ms). Data as of 2026-11-02 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
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

Cosmos Hub RPC endpoints: free public URLs by latency

RPCs

ecostake

Trails

139 ms

p99
197 ms
rank
#2
samples
4,311

PublicNode

Leads

58 ms

p99
309 ms
rank
#1
samples
4,324

Per region

RegionecostakePublicNode
US-East125 ms36 ms
EU-West35 ms31 ms
Singapore257 ms107 ms
RPC latency
ecostaken/aPublicNoden/a

Akash Network RPC endpoints: free public URLs by latency

RPCs

ecostake

Trails

183 ms

p99
398 ms
rank
#3
samples
4,310

PublicNode

Leads

65 ms

p99
245 ms
rank
#1
samples
4,318

Per region

RegionecostakePublicNode
US-East164 ms34 ms
EU-West81 ms45 ms
Singapore303 ms116 ms
RPC latency
ecostaken/aPublicNoden/a

Frequently asked questions

ecostake vs PublicNode: which one is better?

ecostake and PublicNode are compared on 2 shared OpenChainBench benchmarks. PublicNode leads on Cosmos Hub RPC endpoints. See the live table on this page for every metric.

Which is faster, ecostake or PublicNode?

On the Cosmos Hub RPC endpoints benchmark, PublicNode leads at 58 ms versus ecostake at 139 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the ecostake 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.