Hyperliquid public RPC endpoints, tested
Every keyless Hyperliquid (chain ID 999) 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. 5 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/999 | 256 ms | 0 blocks | under 1,000 | none |
| https://rpc.nodeflare.app/hl/public | 37 ms | 6 blocks | 1,000 | recent only |
| https://rpc.swiftnodes.io/rpc/hyperliquid (SwiftNodes, keyless: 2 req/s) | 48 ms | 5 blocks | 1,000 | archive (1M+) |
| https://hyperevm.rpc.sentio.xyz | 167 ms | 16 blocks | 10,000+ | archive (1M+) |
| https://gwan-ssl.wandevs.org:46891 | 172 ms | 2820610 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/hyperliquid(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 Hyperliquid endpoint, limits and status: Hyperliquid RPC, uptime history.