Arc public RPC endpoints, tested
Every keyless Arc (chain ID 5042) 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. 9 of 9 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://arc-rpc.publicnode.com | 14 ms | 0 blocks | 1,000 | none |
| https://arc.drpc.org | 21 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://arc-rpc.blockreq.com/v1/rpc/public | 36 ms | 2 blocks | 1,000 | recent only |
| https://rpc.mainnet.arc.io | 16 ms | 14 blocks | 1,000 | archive (1M+) |
| https://rpc.blockdaemon.mainnet.arc.io | 17 ms | 9 blocks | 10,000+ | recent only |
| https://rpc.drpc.mainnet.arc.io | 17 ms | 9 blocks | under 1,000 | archive (1M+) |
| https://rpc.quicknode.mainnet.arc.io | 18 ms | 8 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/arc (SwiftNodes, keyless: 2 req/s) | 67 ms | 11 blocks | 1,000 | archive (1M+) |
| https://rpc.beamrpc.com | 118 ms | 4 blocks | under 1,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
rpc.beamrpc.com: first head after 139 ms - streams
arc.drpc.org: first head after 211 ms - streams
arc-rpc.publicnode.com: first head after 359 ms - does not stream
rpc.swiftnodes.io/ws/arc(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Test any endpoint yourself with the RPC tester. Our Arc endpoint, limits and status: Arc RPC, uptime history.