Ink public RPC endpoints, tested
Every keyless Ink (chain ID 57073) 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. 7 of 9 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/57073 | 28 ms | 0 blocks | under 1,000 | none |
| https://rpc-qnd.inkonchain.com | 13 ms | 15 blocks | 10,000+ | archive (1M+) |
| https://rpc-gel.inkonchain.com | 18 ms | 16 blocks | 1,000 | archive (1M+) |
| https://ink-rpc.publicnode.com | 21 ms | 10 blocks | 10,000+ | archive (1M+) |
| https://ink.drpc.org | 28 ms | 12 blocks | under 1,000 | archive (1M+) |
| https://ink.api.pocket.network | 43 ms | 10 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/ink (SwiftNodes, keyless: 2 req/s) | 53 ms | 6 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
- streams
ink.drpc.org: first head after 435 ms - streams
ink-rpc.publicnode.com: first head after 835 ms - streams
rpc-qnd.inkonchain.com: first head after 972 ms - does not stream
rpc-gel.inkonchain.com: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/ink(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
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.