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-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. 5 of 11 HTTP endpoints were working.

Working HTTP endpoints

Endpoint	Latency	eth_getLogs	State
https://docs-demo.nova-mainnet.quiknode.pro	18 ms	10,000+	archive (1M+)
https://arbitrum-nova-rpc.publicnode.com	21 ms	10,000+	recent only
https://arbitrum-nova.drpc.org	36 ms	under 1,000	recent only
https://rpc.swiftnodes.io/rpc/arbitrum-nova (SwiftNodes, keyless: 2 req/s)	45 ms	under 1,000	archive (1M+)
https://nova.arbitrum.io/rpc	115 ms	1,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): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

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
lb.routeme.sh/rpc/evm/42170: chainId: rate limited
rpc.nodeflare.app/nova/public: chainId: rate limited
rpc.driftguard.live/nova: no answer (HTTP 502)
arb-nova-mainnet.gateway.tatum.io: chainId: rate limited
arbitrum-nova.gateway.tenderly.co: chainId: rate limited

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