Fastest free PulseChain RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public PulseChain EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , PublicNode leads rpc latency at 95 ms (p50, 24h) on Fastest free PulseChain RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/pulsechain-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
PulseChain (chain 369) is a full-state Ethereum fork launched in 2023 with PLS as the gas token. It maintains EVM compatibility and has a large retail user base. Three keyless endpoints are probed continuously: PublicNode (pulsechain-rpc.publicnode.com), PulseChain official (rpc.pulsechain.com), and G4MM4 (rpc-pulsechain.g4mm4.io).
Methodology
Per-chain member of the RPC latency cluster, extended to PulseChain. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public PulseChain endpoint that sustains continuous probing, 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the PulseChain-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free PulseChain RPC right now?
PublicNode currently leads at 95 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 3 no-key providers probed every 60 seconds from us-east, eu-west and Singapore.
Which PulseChain RPCs work without an API key?
3 endpoints sustain continuous keyless probing: PublicNode, PulseChain official, and G4MM4. Every endpoint was live-verified before inclusion.
Does the fastest PulseChain RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin.
How is PulseChain RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities