Unichain public RPC endpoints, tested

Every keyless Unichain (chain ID 130) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: 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. 10 of 12 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://api-unichain-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c265 ms0 blocksunder 1,000none
https://rpc.swiftnodes.io/rpc/unichain (SwiftNodes, keyless: 2 req/s)7 ms6 blocksunder 1,000archive (1M+)
https://unichain-rpc.publicnode.com37 ms30 blocks1,000none
https://unichain.drpc.org90 ms23 blocksunder 1,000archive (1M+)
https://unichain-rpc.blockreq.com/v1/rpc/public114 ms28 blocks1,000recent only
https://mainnet.unichain.org117 ms32 blocks1,000archive (1M+)
https://unichain.api.onfinality.io/public173 ms22 blocksunder 1,000none
https://unichain-mainnet.rpc.sentio.xyz183 ms9 blocksunder 1,000archive (1M+)
https://rpc.nodeflare.app/unichain/public185 ms15 blocks10,000+none
https://lb.routeme.sh/rpc/evm/130419 ms10 blocks1,000none

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 424 ms
  • streams unichain-rpc.publicnode.com: first head after 899 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: no answer (HTTP 200)
  • unichain-mainnet.gateway.tatum.io: chainId: rate limited

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