PublicNode vs PulseChain Foundation

PublicNode leads on the only live benchmark. PublicNode wins on PulseChain RPC endpoints (45 ms vs 129 ms).

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

PulseChain RPC endpoints: free public URLs by latency

RPCs

PublicNode

Leads

45 ms

p99
314 ms
rank
#1
samples
4,316

PulseChain Foundation

Trails

129 ms

p99
356 ms
rank
#3
samples
4,318

Per region

RegionPublicNodePulseChain Foundation
US-East18 ms126 ms
EU-West19 ms55 ms
Singapore97 ms206 ms
RPC latency
PublicNoden/aPulseChain Foundationn/a

Frequently asked questions

PublicNode vs PulseChain Foundation: which one is better?

PublicNode and PulseChain Foundation are compared on 1 shared OpenChainBench benchmarks. PublicNode leads on PulseChain RPC endpoints. See the live table on this page for every metric.

Which is faster, PublicNode or PulseChain Foundation?

On the PulseChain RPC endpoints benchmark, PublicNode leads at 45 ms versus PulseChain Foundation at 129 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the PublicNode vs PulseChain Foundation 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.