Lisk public RPC endpoints, tested
Every keyless Lisk (chain ID 1135) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 3 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lisk.drpc.org | 17 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.api.lisk.com | 25 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/lisk (SwiftNodes, keyless: 2 req/s) | 138 ms | 3 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
lisk.drpc.org: first head after 896 ms - does not stream
rpc.swiftnodes.io/ws/lisk(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
lb.routeme.sh/rpc/evm/1135: chainId: rate limitedlisk.gateway.tenderly.co: chainId: rate limitedapi-lisk-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limitedlisk-mainnet.gateway.tatum.io: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Lisk endpoint, limits and status: Lisk RPC, uptime history.