Tron (EVM) public RPC endpoints, tested
Every keyless Tron (EVM) (chain ID 728126428) 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. 6 of 9 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/728126428 | 57 ms | 0 blocks | under 1,000 | none |
| https://rpc.swiftnodes.io/rpc/tron-evm (SwiftNodes, keyless: 2 req/s) | 63 ms | 2 blocks | 1,000 | none |
| https://api.trongrid.io/jsonrpc | 11 ms | 8 blocks | 1,000 | none |
| https://tron.drpc.org | 25 ms | 9 blocks | under 1,000 | none |
| https://tron.api.pocket.network | 49 ms | 5 blocks | 1,000 | none |
| https://tron.rpc.sentio.xyz | 160 ms | 5 blocks | 1,000 | none |
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
tron.drpc.org: subscribe rejected: method is not available - does not stream
rpc.swiftnodes.io/ws/tron-evm(SwiftNodes): gateway: WebSocket not available for chain: tron-evm
Listed but not working
rpc.ankr.com/tron_jsonrpc: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403tron.therpc.io/jsonrpc: chainId: fetch failedtron-mainnet.gateway.tatum.io: no answer (HTTP 404)
Test any endpoint yourself with the RPC tester. Our Tron (EVM) endpoint, limits and status: Tron (EVM) RPC, uptime history.