LavenderFive vs PublicNode

PublicNode leads on all 8 live benchmarks. PublicNode wins on Osmosis RPC endpoints (81 ms vs 175 ms), Cosmos Hub RPC endpoints (90 ms vs 175 ms), Injective RPC endpoints (84 ms vs 175 ms), dYdX Chain RPC endpoints (91 ms vs 176 ms). Data as of 2026-10-23 UTC.

Read methodology Last measured Window: rolling 24h8 shared benchmarks
LavenderFive logo
LavenderFive

Cosmos validator running multi-chain no-key RPC endpoints under rpc.lavenderfive.com/<chain> and lcd.lavenderfive.com/<chain>. Covers Osmosis, Cosmos Hub, Neutron, Injective and 20+ other Cosmos SDK chains.

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

Osmosis RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

175 ms

p99
560 ms
rank
#4
samples
4,322

PublicNode

Leads

81 ms

p99
516 ms
rank
#1
samples
4,321

Per region

RegionLavenderFivePublicNode
US-East149 ms37 ms
EU-West75 ms28 ms
Singapore300 ms178 ms
RPC latency
LavenderFiven/aPublicNoden/a

Cosmos Hub RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

175 ms

p99
549 ms
rank
#4
samples
4,329

PublicNode

Leads

90 ms

p99
595 ms
rank
#1
samples
4,342

Per region

RegionLavenderFivePublicNode
US-East150 ms60 ms
EU-West76 ms31 ms
Singapore300 ms178 ms
RPC latency
LavenderFiven/aPublicNoden/a

Injective RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

175 ms

p99
544 ms
rank
#2
samples
4,336

PublicNode

Leads

84 ms

p99
602 ms
rank
#1
samples
4,337

Per region

RegionLavenderFivePublicNode
US-East149 ms35 ms
EU-West76 ms36 ms
Singapore300 ms183 ms
RPC latency
LavenderFiven/aPublicNoden/a

dYdX Chain RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

176 ms

p99
559 ms
rank
#3
samples
4,328

PublicNode

Leads

91 ms

p99
586 ms
rank
#1
samples
4,329

Per region

RegionLavenderFivePublicNode
US-East150 ms54 ms
EU-West76 ms35 ms
Singapore301 ms184 ms
RPC latency
LavenderFiven/aPublicNoden/a

Celestia RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

175 ms

p99
428 ms
rank
#3
samples
4,332

PublicNode

Leads

94 ms

p99
353 ms
rank
#1
samples
4,335

Per region

RegionLavenderFivePublicNode
US-East149 ms52 ms
EU-West75 ms41 ms
Singapore299 ms188 ms
RPC latency
LavenderFiven/aPublicNoden/a

Axelar RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

175 ms

p99
544 ms
rank
#3
samples
4,329

PublicNode

Leads

109 ms

p99
694 ms
rank
#1
samples
4,326

Per region

RegionLavenderFivePublicNode
US-East151 ms85 ms
EU-West74 ms48 ms
Singapore299 ms193 ms
RPC latency
LavenderFiven/aPublicNoden/a

Terra RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

145 ms

p99
622 ms
rank
#3
samples
4,335

PublicNode

Leads

93 ms

p99
651 ms
rank
#1
samples
4,331

Per region

RegionLavenderFivePublicNode
US-East121 ms45 ms
EU-West43 ms40 ms
Singapore272 ms193 ms
RPC latency
LavenderFiven/aPublicNoden/a

Babylon RPC endpoints: free public URLs by latency

RPCs

LavenderFive

Trails

173 ms

p99
560 ms
rank
#3
samples
4,331

PublicNode

Leads

126 ms

p99
696 ms
rank
#2
samples
4,327

Per region

RegionLavenderFivePublicNode
US-East148 ms157 ms
EU-West73 ms36 ms
Singapore299 ms186 ms
RPC latency
LavenderFiven/aPublicNoden/a

Frequently asked questions

LavenderFive vs PublicNode: which one is better?

LavenderFive and PublicNode are compared on 8 shared OpenChainBench benchmarks. PublicNode leads on Osmosis RPC endpoints. See the live table on this page for every metric.

Which is faster, LavenderFive or PublicNode?

On the Osmosis RPC endpoints benchmark, PublicNode leads at 81 ms versus LavenderFive at 175 ms. Live measurement is updated continuously by the OpenChainBench harness.

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