HAQQ public RPC endpoints, tested
Every keyless HAQQ (chain ID 11235) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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. 5 of 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://haqq-evm.publicnode.com | 19 ms | 0 blocks | 10,000+ | none |
| https://haqq.drpc.org | 28 ms | 0 blocks | under 1,000 | recent only |
| https://rpc.eth.haqq.network | 30 ms | 0 blocks | 10,000+ | recent only |
| https://haqq-evm-rpc.publicnode.com | 32 ms | 0 blocks | 10,000+ | none |
| https://rpc.swiftnodes.io/rpc/haqq (SwiftNodes, keyless: 2 req/s) | 229 ms | 0 blocks | 10,000+ | none |
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
haqq.drpc.org: first head after 98 ms - subscribed
haqq-evm-rpc.publicnode.com: accepted; this chain produced no block during the 15 s window - subscribed
haqq-evm.publicnode.com: accepted; this chain produced no block during the 15 s window - does not stream
evm-ws.haqq.sh: connection failed (connect) - subscribed
rpc.swiftnodes.io/ws/haqq(SwiftNodes): accepted; this chain produced no block during the 15 s window
Listed but not working
lb.routeme.sh/rpc/evm/11235: chainId: rate limitedevm.haqq.sh: chainId: timeouthaqq-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our HAQQ endpoint, limits and status: HAQQ RPC, uptime history.