Hyperliquid public RPC endpoints, tested
Every keyless Hyperliquid (chain ID 999) 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. 4 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.nodeflare.app/hl/public | 49 ms | 0 blocks | 1,000 | none |
| https://gwan-ssl.wandevs.org:46891 | 166 ms | 1645940 blocks | 10,000+ | archive (1M+) |
| https://hyperevm.rpc.sentio.xyz | 170 ms | 10 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/hyperliquid (SwiftNodes, keyless: 2 req/s) | 182 ms | 6 blocks | 1,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): gateway: WebSocket not available for chain: hyperliquid
Listed but not working
lb.routeme.sh/rpc/evm/999: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Hyperliquid endpoint, limits and status: Hyperliquid RPC, uptime history.