Lens Chain public RPC endpoints, tested
Every keyless Lens Chain (chain ID 232) 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. 4 of 5 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.lens.xyz | 21 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://lens.drpc.org | 25 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/232 | 31 ms | 0 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/lens (SwiftNodes, keyless: 2 req/s) | 61 ms | 1 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
lens.drpc.org: first head after 16714 ms - does not stream
rpc.swiftnodes.io/ws/lens(SwiftNodes): gateway: WebSocket not available for chain: lens
Listed but not working
light-icy-dinghy.lens-mainnet.quiknode.pro: chainId: fetch failed
Test any endpoint yourself with the RPC tester. Our Lens Chain endpoint, limits and status: Lens Chain RPC, uptime history.