TAC public RPC endpoints, tested

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

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc-public.tac.build130 ms0 blocks1,000archive (1M+)
https://rpc.swiftnodes.io/rpc/tac (SwiftNodes, keyless: 2 req/s)109 ms4 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

  • streams rpc-public.tac.build: first head after 970 ms
  • does not stream rpc.swiftnodes.io/ws/tac (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • rpc.ankr.com/tac: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403
  • lb.routeme.sh/rpc/evm/239: chainId: rate limited
  • tac.drpc.org: chainId: rate limited

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