TAC public RPC endpoints, tested
Every keyless TAC (chain ID 239) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-10-04: 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. 4 of 7 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.ankr.com/tac | 19 ms | 1 blocks | 10,000+ | archive (1M+) |
| https://tac.drpc.org | 26 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/tac (SwiftNodes, keyless: 2 req/s) | 58 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://rpc.tac.build | 103 ms | 1 blocks | 10,000+ | archive (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
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
ws.rpc.tac.build: chainId: fetch failedtac.therpc.io: chainId: fetch failedlb.routeme.sh/rpc/evm/239: chainId: rate limited
Test any endpoint yourself with the RPC tester. Our TAC endpoint, limits and status: TAC RPC, uptime history.