ABCore public RPC endpoints, tested
Every keyless ABCore (chain ID 36888) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 3 of 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.core.ab.org | 252 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://rpc1.core.ab.org | 253 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/abcore (SwiftNodes, keyless: 2 req/s) | 768 ms | 2 blocks | 10,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
- does not stream
rpc.swiftnodes.io/ws/abcore(SwiftNodes): gateway: WebSocket not available for chain: abcore
Test any endpoint yourself with the RPC tester. Our ABCore endpoint, limits and status: ABCore RPC, uptime history.