Core public RPC endpoints, tested
Every keyless Core (chain ID 1116) 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. 5 of 8 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://core.drpc.org | 28 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://rpc.coredao.org | 107 ms | 2 blocks | 10,000+ | none |
| https://rpc.swiftnodes.io/rpc/core (SwiftNodes, keyless: 2 req/s) | 157 ms | 2 blocks | under 1,000 | recent only |
| https://rpc.ankr.com/core | 159 ms | 1 blocks | 1,000 | archive (1M+) |
| https://api.zan.top/core-mainnet | 180 ms | 0 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
core.drpc.org: first head after 187 ms - streams
ws.coredao.org: first head after 1957 ms - does not stream
rpc.swiftnodes.io/ws/core(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc-core.icecreamswap.com: no answer (HTTP 525)public.1rpc.io/core: chainId: You've reached the usage limit for your current plan. To continue with higher limits and unlb.routeme.sh/rpc/evm/1116: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our Core endpoint, limits and status: Core RPC, uptime history.