PulseChain public RPC endpoints, tested
Every keyless PulseChain (chain ID 369) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 4 of 4 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc-pulsechain.g4mm4.io | 35 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.pulsechain.com | 39 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://pulsechain-rpc.publicnode.com | 40 ms | 0 blocks | 10,000+ | recent only |
| https://rpc.swiftnodes.io/rpc/pulsechain (SwiftNodes, keyless: 2 req/s) | 75 ms | 0 blocks | 10,000+ | archive (1M+) |
Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.
WebSocket endpoints
- streams
pulsechain-rpc.publicnode.com: first head after 3402 ms - does not stream
rpc.swiftnodes.io/ws/pulsechain(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Test any endpoint yourself with the RPC tester. Our PulseChain endpoint, limits and status: PulseChain RPC, uptime history.