Arbitrum public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://lb.routeme.sh/rpc/evm/4216153 ms0 blocksunder 1,000none
https://arbitrum-one-rpc.publicnode.com19 ms97 blocksunder 1,000none
https://arbitrum-one-mainnet.gateway.tatum.io21 ms22 blocksunder 1,000none
https://arb-one-mainnet.gateway.tatum.io25 ms38 blocksunder 1,000none
https://public-arb-mainnet.fastnode.io36 ms31 blocks10,000+none
https://arbitrum.drpc.org44 ms72 blocksunder 1,000none
https://rpc-arbitrum.blockmachine.io46 ms8 blocks1,000archive (1M+)
https://arbitrum-one-public.nodies.app56 ms81 blocksunder 1,000archive (1M+)
https://arb-one.api.pocket.network84 ms33 blocksunder 1,000archive (1M+)
https://arb1.arbitrum.io/rpc119 ms99 blocks10,000+archive (1M+)
https://rpc.nodeflare.app/arb/public120 ms53 blocks1,000recent only
https://arbitrum-one.public.blastapi.io152 ms78 blocksunder 1,000archive (1M+)
https://arbitrum-one.rpc.sentio.xyz171 ms31 blocks10,000+archive (1M+)
https://api.zan.top/arb-one172 ms73 blocksunder 1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/arbitrum (SwiftNodes, keyless: 2 req/s)194 ms19 blocks1,000archive (1M+)
https://public.1rpc.io/arb198 ms83 blocksunder 1,000archive (1M+)
https://arbitrum.meowrpc.com207 ms62 blocksunder 1,000archive (1M+)
https://xrpc.cl/arbitrum1639 ms69 blocks1,000recent 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

  • streams arbitrum-one-rpc.publicnode.com: first head after 134 ms
  • streams rpc.swiftnodes.io/ws/arbitrum (SwiftNodes): first head after 200 ms
  • streams arbitrum.drpc.org: first head after 236 ms
  • does not stream arbitrum.callstaticrpc.com: connection failed (connect)

Listed but not working

  • rpcfree.com/arbitrum-rpc: no answer (HTTP 200)
  • rpc.satelink.network/rpc/arbitrum: chainId: Payment required
  • rpc.ankr.com/arbitrum/c4cc6a8c87ec30258076de433ab2cf3d834228aae3fc4d76087873e4fea11635: chainId: message: API key disabled, json-rpc code: -32051, rest code: 403
  • arb-mainnet-public.unifra.io: chainId: fetch failed
  • rpc.arb1.arbitrum.gateway.fm: chainId: fetch failed
  • public.stackup.sh/api/v1/node/arbitrum-one: chainId: fetch failed
  • api.stateless.solutions/arbitrum-one/v1/demo: chainId: fetch failed
  • endpoints.omniatech.io/v1/arbitrum/one/public: no answer (HTTP 521)
  • arb1.lava.build: chainId: This endpoint has been discontinued.
  • rpc.owlracle.info/arb/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • arbitrum.therpc.io: chainId: fetch failed
  • rpc.poolz.finance/arbitrum: chainId: fetch failed
  • arbitrum.gateway.tenderly.co: chainId: rate limited
  • arb-rpc.keccak.io: chainId: auth error - api key required. This method needs an account — register free and get an API
  • api-arbitrum-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited
  • arbitrum.api.onfinality.io/public: eth_blockNumber failed

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