Abstract public RPC endpoints, tested
Every keyless Abstract (chain ID 2741) 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 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://abstract.api.onfinality.io/public | 106 ms | 0 blocks | 10,000+ | none |
| https://abstract.drpc.org | 20 ms | 28 blocks | under 1,000 | archive (1M+) |
| https://abstract-mainnet.gateway.tatum.io | 24 ms | 17 blocks | under 1,000 | archive (1M+) |
| https://api.mainnet.abs.xyz | 26 ms | 20 blocks | 10,000+ | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/2741 | 34 ms | 15 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/abstract (SwiftNodes, keyless: 2 req/s) | 42 ms | 6 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
abstract.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/abstract(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 Abstract endpoint, limits and status: Abstract RPC, uptime history.