Arbitrum public RPC endpoints, tested

Every keyless Arbitrum (chain ID 42161) 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. 19 of 27 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc-arbitrum.blockmachine.io47 ms0 blocks1,000archive (1M+)
https://public-arb-mainnet.fastnode.io19 ms22 blocks10,000+none
https://arbitrum-one-mainnet.gateway.tatum.io19 ms8 blocksunder 1,000none
https://arbitrum.drpc.org22 ms53 blocksunder 1,000none
https://arb-one-mainnet.gateway.tatum.io28 ms33 blocksunder 1,000recent only
https://rpc.swiftnodes.io/rpc/arbitrum (SwiftNodes, keyless: 2 req/s)30 ms16 blocks10,000+archive (1M+)
https://arbitrum-one-rpc.publicnode.com31 ms147 blocksunder 1,000none
https://arbitrum-one-rpc.blockreq.com/v1/rpc/public36 ms138 blocks1,000recent only
https://arb-one.api.pocket.network70 ms32 blocks1,000archive (1M+)
https://lb.routeme.sh/rpc/evm/4216171 ms79 blocksunder 1,000none
https://rpc.nodeflare.app/arb/public104 ms73 blocks1,000recent only
https://arbitrum-one-public.nodies.app108 ms86 blocksunder 1,000archive (1M+)
https://arbitrum-one.public.blastapi.io108 ms77 blocksunder 1,000archive (1M+)
https://arb1.arbitrum.io/rpc113 ms150 blocks10,000+recent only
https://rpc.hostdefi.com/api/rpc/arbitrum158 ms110 blocksunder 1,000none
https://arbitrum.meowrpc.com168 ms71 blocksunder 1,000none
https://api.zan.top/arb-one168 ms66 blocksunder 1,000archive (1M+)
https://arbitrum-one.rpc.sentio.xyz169 ms19 blocks10,000+archive (1M+)
https://xrpc.cl/arbitrum779 ms124 blocks10,000+none

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 arbitrum.drpc.org: first head after 23 ms
  • does not stream arbitrum-one-rpc.publicnode.com: timeout (subscribe)
  • does not stream arbitrum.callstaticrpc.com: connection failed (connect)
  • does not stream rpc.swiftnodes.io/ws/arbitrum (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • rpcfree.com/arbitrum-rpc: no answer (HTTP 200)
  • rpc.satelink.network/rpc/arbitrum: chainId: Payment required
  • public.1rpc.io/arb: chainId: timeout
  • api.stateless.solutions/arbitrum-one/v1/demo: chainId: fetch failed
  • rpc.owlracle.info/arb/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • arbitrum.gateway.tenderly.co: chainId: rate limited
  • arbitrum.api.onfinality.io/public: eth_blockNumber failed
  • api-arbitrum-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: eth_blockNumber failed

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