Cosmos Directory vs PublicNode

PublicNode leads on both live benchmarks. PublicNode wins on Sentinel DVPN RPC endpoints (84 ms vs 196 ms), Fetch.ai RPC endpoints (82 ms vs 199 ms). Data as of 2026-10-12 UTC.

Read methodology Last measured Window: rolling 24h2 shared benchmarks
Cosmos Directory logo
Cosmos Directory

Cosmos Directory public RPC proxy. Aggregates Tendermint RPC endpoints across the Cosmos ecosystem, no API key required.

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

Sentinel DVPN RPC endpoints: free public URLs by latency

RPCs

Cosmos Directory

Trails

196 ms

p99
678 ms
rank
#3
samples
4,321

PublicNode

Leads

84 ms

p99
380 ms
rank
#1
samples
4,318

Per region

RegionCosmos DirectoryPublicNode
US-East224 ms28 ms
EU-West93 ms30 ms
Singapore273 ms193 ms
RPC latency
Cosmos Directoryn/aPublicNoden/a

Fetch.ai RPC endpoints: free public URLs by latency

RPCs

Cosmos Directory

Trails

199 ms

p99
891 ms
rank
#3
samples
4,314

PublicNode

Leads

82 ms

p99
498 ms
rank
#1
samples
4,319

Per region

RegionCosmos DirectoryPublicNode
US-East219 ms27 ms
EU-West97 ms36 ms
Singapore282 ms184 ms
RPC latency
Cosmos Directoryn/aPublicNoden/a

Frequently asked questions

Cosmos Directory vs PublicNode: which one is better?

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

Which is faster, Cosmos Directory or PublicNode?

On the Sentinel DVPN RPC endpoints benchmark, PublicNode leads at 84 ms versus Cosmos Directory at 196 ms. Live measurement is updated continuously by the OpenChainBench harness.

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