Linea public RPC endpoints, tested

Every keyless Linea (chain ID 59144) 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. 8 of 14 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://linea-rpc.publicnode.com	17 ms	1 blocks	under 1,000	none
https://linea.drpc.org	28 ms	1 blocks	under 1,000	archive (1M+)
https://lb.routeme.sh/rpc/evm/59144	29 ms	1 blocks	under 1,000	none
https://api-linea-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c	45 ms	0 blocks	under 1,000	recent only
https://linea.api.pocket.network	81 ms	1 blocks	10,000+	recent only
https://rpc.linea.build	125 ms	1 blocks	10,000+	archive (1M+)
https://linea.rpc.sentio.xyz	170 ms	1 blocks	10,000+	archive (1M+)
https://rpc.swiftnodes.io/rpc/linea (SwiftNodes, keyless: 2 req/s)	263 ms	0 blocks	under 1,000	none

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/linea (SwiftNodes): first head after 3690 ms
does not stream rpc.linea.build: connection failed (connect)
does not stream linea-rpc.publicnode.com: subscribed, no head in 15 s

Listed but not working

rpc.nodeflare.app/linea/public: chainId: unknown_chain
public.1rpc.io/linea: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
linea.decubate.com: chainId: fetch failed
rpc.owlracle.info/linea/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
linea.therpc.io: chainId: fetch failed
rpc.poolz.finance/linea: chainId: fetch failed

Test any endpoint yourself with the RPC tester. Our Linea endpoint, limits and status: Linea RPC, uptime history.