Telos EVM public RPC endpoints, tested
Every keyless Telos EVM (chain ID 40) 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 6 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://rpc.telos.net | 28 ms | 0 blocks | 10,000+ | archive (1M+) |
| https://telos.drpc.org | 24 ms | 23 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/telos (SwiftNodes, keyless: 2 req/s) | 52 ms | 12 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
telos.drpc.org: subscribe rejected: method is not available on free plan, please upgrade to paid plan - does not stream
rpc.swiftnodes.io/ws/telos(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.ankr.com/telos: chainId: message: API key is not allowed to access blockchain, json-rpc code: -32052, rest code: 403public.1rpc.io/telos/evm: chainId: timeoutlb.routeme.sh/rpc/evm/40: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Telos EVM endpoint, limits and status: Telos EVM RPC, uptime history.