Arc public RPC endpoints, tested
Every keyless Arc (chain ID 5042) 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. 7 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://arc.drpc.org | 48 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.beamrpc.com | 110 ms | 2 blocks | 1,000 | archive (1M+) |
| https://rpc.blockdaemon.mainnet.arc.io | 19 ms | 7 blocks | 10,000+ | recent only |
| https://rpc.drpc.mainnet.arc.io | 25 ms | 7 blocks | under 1,000 | archive (1M+) |
| https://rpc.quicknode.mainnet.arc.io | 44 ms | 4 blocks | 1,000 | archive (1M+) |
| https://rpc.mainnet.arc.io | 45 ms | 13 blocks | 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/arc (SwiftNodes, keyless: 2 req/s) | 253 ms | 10 blocks | 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
arc.drpc.org: first head after 504 ms - streams
rpc.beamrpc.com: first head after 510 ms - does not stream
rpc.swiftnodes.io/ws/arc(SwiftNodes): timeout (subscribe)
Test any endpoint yourself with the RPC tester. Our Arc endpoint, limits and status: Arc RPC, uptime history.