Ethereum Classic public RPC endpoints, tested
Every keyless Ethereum Classic (chain ID 61) 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. 6 of 10 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://ethereum-classic-mainnet.gateway.tatum.io | 24 ms | 0 blocks | under 1,000 | none |
| https://geth-at.etc-network.info | 28 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://etc.etcdesktop.com | 31 ms | 1 blocks | 10,000+ | none |
| https://0xrpc.io/etc | 31 ms | 1 blocks | 10,000+ | none |
| https://rpc.etcmc.xyz | 34 ms | 1 blocks | 1,000 | none |
| https://rpc.swiftnodes.io/rpc/etc (SwiftNodes, keyless: 2 req/s) | 95 ms | 0 blocks | 10,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
- does not stream
0xrpc.io/etc: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/etc(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
etc.rivet.link: chainId: fetch failedbesu-at.etc-network.info: no answer (HTTP 404)etc.mytokenpocket.vip: chainId: timeoutlb.routeme.sh/rpc/evm/61: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Ethereum Classic endpoint, limits and status: Ethereum Classic RPC, uptime history.