Syscoin public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc.syscoin.org20 ms0 blocks10,000+archive (1M+)
https://syscoin-evm.publicnode.com26 ms0 blocks10,000+recent only
https://rpc.swiftnodes.io/rpc/syscoin (SwiftNodes, keyless: 2 req/s)63 ms0 blocks1,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

  • 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
  • does not stream rpc.swiftnodes.io/ws/syscoin (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

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
  • lb.routeme.sh/rpc/evm/57: chainId: rate limited
  • 57.rpc.thirdweb.com: eth_blockNumber failed

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