Syscoin public RPC endpoints, tested

Every keyless Syscoin (chain ID 57) 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. 5 of 7 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.syscoin.org19 ms0 blocks10,000+recent only
https://syscoin-evm.publicnode.com56 ms0 blocks10,000+recent only
https://lb.routeme.sh/rpc/evm/5773 ms0 blocks1,000none
https://rpc.swiftnodes.io/rpc/syscoin (SwiftNodes, keyless: 2 req/s)303 ms0 blocks10,000+recent only
https://57.rpc.thirdweb.com768 ms0 blocksunder 1,000recent only

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 rpc.swiftnodes.io/ws/syscoin (SwiftNodes): first head after 14856 ms
  • subscribed rpc.syscoin.org/wss: accepted; this chain produced no block during the 15 s window
  • subscribed syscoin-evm.publicnode.com: accepted; this chain produced no block during the 15 s window

Listed but not working

  • syscoin.public-rpc.com: chainId: Unauthorized: You must authenticate your request with an API key. Create an account on http
  • rpc.ankr.com/syscoin: chainId: Unauthorized: You must authenticate your request with an API key. Create an account on http

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