Unichain public RPC endpoints, tested

Every keyless Unichain (chain ID 130) 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. 8 of 12 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	Behind best	eth_getLogs	State
https://api-unichain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c	42 ms	0 blocks	under 1,000	recent only
https://unichain-rpc.publicnode.com	27 ms	33 blocks	10,000+	none
https://unichain-rpc.blockreq.com/v1/rpc/public	30 ms	31 blocks	1,000	recent only
https://unichain.drpc.org	38 ms	26 blocks	under 1,000	archive (1M+)
https://rpc.swiftnodes.io/rpc/unichain (SwiftNodes, keyless: 2 req/s)	45 ms	6 blocks	10,000+	archive (1M+)
https://rpc.nodeflare.app/unichain/public	69 ms	21 blocks	1,000	recent only
https://mainnet.unichain.org	110 ms	36 blocks	10,000+	archive (1M+)
https://unichain-mainnet.rpc.sentio.xyz	173 ms	16 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 unichain.drpc.org: first head after 49 ms
streams unichain-rpc.publicnode.com: first head after 259 ms
does not stream rpc.swiftnodes.io/ws/unichain (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

unichain.therpc.io: chainId: fetch failed
unichain-mainnet.gateway.tatum.io: chainId: rate limited
lb.routeme.sh/rpc/evm/130: eth_blockNumber failed
unichain.api.onfinality.io/public: eth_blockNumber failed

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