Unichain public RPC endpoints, tested
Every keyless Unichain (chain ID 130) 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. 7 of 12 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.swiftnodes.io/rpc/unichain (SwiftNodes, keyless: 2 req/s) | 94 ms | 3 blocks | 1,000 | none |
| https://api-unichain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c | 136 ms | 0 blocks | under 1,000 | none |
| https://unichain-rpc.publicnode.com | 28 ms | 26 blocks | 1,000 | none |
| https://unichain.drpc.org | 65 ms | 18 blocks | under 1,000 | archive (1M+) |
| https://mainnet.unichain.org | 114 ms | 31 blocks | 10,000+ | archive (1M+) |
| https://rpc.nodeflare.app/unichain/public | 131 ms | 14 blocks | 1,000 | recent only |
| https://unichain-mainnet.rpc.sentio.xyz | 170 ms | 11 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
rpc.swiftnodes.io/ws/unichain(SwiftNodes): first head after 316 ms - streams
unichain-rpc.publicnode.com: first head after 331 ms - streams
unichain.drpc.org: first head after 383 ms
Listed but not working
unichain.therpc.io: chainId: fetch failedrpc.poolz.finance/unichain: chainId: fetch failedunichain.api.onfinality.io/public: chainId: rate limitedunichain-mainnet.gateway.tatum.io: chainId: rate limitedlb.routeme.sh/rpc/evm/130: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Unichain endpoint, limits and status: Unichain RPC, uptime history.