Astar public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://evm.astar.network18 ms0 blocks1,000archive (1M+)
https://astar.api.onfinality.io/public100 ms0 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/astar (SwiftNodes, keyless: 2 req/s)374 ms1 blocks1,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

  • streams astar.api.onfinality.io/public-ws: first head after 3636 ms
  • streams rpc.swiftnodes.io/ws/astar (SwiftNodes): first head after 9039 ms
  • does not stream astar-rpc.dwellir.com: connection failed (connect)

Listed but not working

  • astar.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • getblock.io/nodes/bsc: no answer (HTTP 405)
  • public.1rpc.io/astr: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
  • astar-rpc.dwellir.com: chainId: fetch failed
  • lb.routeme.sh/rpc/evm/592: chainId: rate limited
  • rpc.astar.network:8545: chainId: timeout
  • astar.public.curie.radiumblock.co/http: chainId: timeout
  • astar.public.curie.radiumblock.co/ws: chainId: timeout

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