peaq public RPC endpoints, tested
Every keyless peaq (chain ID 3338) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-11: 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 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://quicknode3.peaq.xyz | 17 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://quicknode2.peaq.xyz | 20 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://quicknode1.peaq.xyz | 32 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/peaq (SwiftNodes, keyless: 2 req/s) | 74 ms | 1 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
- does not stream
rpc.swiftnodes.io/ws/peaq(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
lb.routeme.sh/rpc/evm/3338: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our peaq endpoint, limits and status: peaq RPC, uptime history.