Arbitrum public RPC endpoints, tested
Every keyless Arbitrum (chain ID 42161) 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. 14 of 29 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc-arbitrum.blockmachine.io | 47 ms | 0 blocks | under 1,000 | none |
| https://arbitrum-one.rpc.sentio.xyz | 179 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://api.blockvectra.com/v1/arb_mainnet/public | 18 ms | 54 blocks | under 1,000 | recent only |
| https://public-arb-mainnet.fastnode.io | 24 ms | 13 blocks | 10,000+ | none |
| https://arb-one.api.pocket.network | 30 ms | 15 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/arbitrum (SwiftNodes, keyless: 2 req/s) | 44 ms | 9 blocks | under 1,000 | archive (1M+) |
| https://arbitrum-one-rpc.blockreq.com/v1/rpc/public | 50 ms | 55 blocks | 1,000 | recent only |
| https://arbitrum-one-rpc.publicnode.com | 59 ms | 59 blocks | under 1,000 | none |
| https://arbitrum.meowrpc.com | 83 ms | 27 blocks | under 1,000 | none |
| https://arbitrum-one.public.blastapi.io | 104 ms | 42 blocks | under 1,000 | archive (1M+) |
| https://arbitrum.drpc.org | 111 ms | 32 blocks | under 1,000 | none |
| https://arbitrum-one-public.nodies.app | 114 ms | 43 blocks | under 1,000 | archive (1M+) |
| https://arb1.arbitrum.io/rpc | 159 ms | 62 blocks | 10,000+ | recent only |
| https://api.zan.top/arb-one | 179 ms | 27 blocks | under 1,000 | archive (1M+) |
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 145 ms - streams
arbitrum-one-rpc.publicnode.com: first head after 228 ms - 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: no answer (HTTP 404)rpc.hostdefi.com/api/rpc/arbitrum: no answer (HTTP 403)public.1rpc.io/arb: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unxrpc.cl/arbitrum: chainId: XRPC Cluster: Backend arbitrum node currently syncing and fallbacks busyapi.stateless.solutions/arbitrum-one/v1/demo: chainId: fetch failedrpc.owlracle.info/arb/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)lb.routeme.sh/rpc/evm/42161: chainId: rate limitedrpc.nodeflare.app/arb/public: chainId: rate limitedarbitrum.gateway.tenderly.co: chainId: rate limitedrpc.driftguard.live/arb: no answer (HTTP 502)api-arbitrum-mainnet-archive.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limitedarbitrum-one-mainnet.gateway.tatum.io: chainId: rate limitedarbitrum.api.onfinality.io/public: eth_blockNumber failedarb-one-mainnet.gateway.tatum.io: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Arbitrum endpoint, limits and status: Arbitrum RPC, uptime history.