Arbitrum Nova public RPC endpoints, tested

Every keyless Arbitrum Nova (chain ID 42170) 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. 5 of 10 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://docs-demo.nova-mainnet.quiknode.pro13 ms0 blocks10,000+archive (1M+)
https://arbitrum-nova-rpc.publicnode.com17 ms0 blocks10,000+recent only
https://arbitrum-nova.drpc.org22 ms0 blocksunder 1,000recent only
https://nova.arbitrum.io/rpc122 ms0 blocks1,000recent only
https://rpc.swiftnodes.io/rpc/arbitrum-nova (SwiftNodes, keyless: 2 req/s)123 ms0 blocks10,000+recent only

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

  • subscribed arbitrum-nova-rpc.publicnode.com: accepted; this chain produced no block during the 15 s window
  • subscribed arbitrum-nova.drpc.org: accepted; this chain produced no block during the 15 s window
  • does not stream rpc.swiftnodes.io/ws/arbitrum-nova (SwiftNodes): gateway: WebSocket not available for chain: arbitrum-nova

Listed but not working

  • arbitrum-nova.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • rpc.nodeflare.app/nova/public: chainId: unknown_chain
  • arb-nova-mainnet.gateway.tatum.io: chainId: rate limited
  • arbitrum-nova.gateway.tenderly.co: chainId: rate limited
  • lb.routeme.sh/rpc/evm/42170: eth_blockNumber failed

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