Abstract public RPC endpoints, tested

Every keyless Abstract (chain ID 2741) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-22: 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 6 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://lb.routeme.sh/rpc/evm/274144 ms0 blocks1,000none
https://abstract.api.onfinality.io/public448 ms0 blocks10,000+recent only
https://api.mainnet.abs.xyz20 ms8 blocks10,000+archive (1M+)
https://abstract.drpc.org25 ms6 blocksunder 1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/abstract (SwiftNodes, keyless: 2 req/s)35 ms8 blocksunder 1,000archive (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

Listed but not working

  • abstract-mainnet.gateway.tatum.io: chainId: rate limited

Test any endpoint yourself with the RPC tester. Our Abstract endpoint, limits and status: Abstract RPC, uptime history.