Ink public RPC endpoints, tested
Every keyless Ink (chain ID 57073) 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. 6 of 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/57073 | 24 ms | 0 blocks | under 1,000 | none |
| https://rpc-gel.inkonchain.com | 19 ms | 26 blocks | 10,000+ | archive (1M+) |
| https://ink.drpc.org | 26 ms | 21 blocks | under 1,000 | archive (1M+) |
| https://rpc-qnd.inkonchain.com | 27 ms | 22 blocks | 10,000+ | archive (1M+) |
| https://ink.api.pocket.network | 70 ms | 19 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/ink (SwiftNodes, keyless: 2 req/s) | 99 ms | 5 blocks | 10,000+ | recent only |
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
rpc.swiftnodes.io/ws/ink(SwiftNodes): first head after 0 ms - streams
rpc-qnd.inkonchain.com: first head after 806 ms - does not stream
rpc-gel.inkonchain.com: connection failed (connect) - does not stream
ink.drpc.org: subscribe rejected: Unsupported subscription: newHeads
Listed but not working
ink-public.nodies.app: no answer (HTTP 403)rpc.nodeflare.app/ink/public: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Ink endpoint, limits and status: Ink RPC, uptime history.