Tempo public RPC endpoints, tested
Every keyless Tempo (chain ID 4217) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-09-24: 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 3 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://lb.routeme.sh/rpc/evm/4217 | 45 ms | 0 blocks | under 1,000 | none |
| https://rpc.mainnet.tempo.xyz | 132 ms | 30 blocks | 10,000+ | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/tempo (SwiftNodes, keyless: 2 req/s) | 212 ms | 7 blocks | under 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
- streams
rpc.swiftnodes.io/ws/tempo(SwiftNodes): first head after 382 ms - streams
rpc.mainnet.tempo.xyz: first head after 390 ms
Test any endpoint yourself with the RPC tester. Our Tempo endpoint, limits and status: Tempo RPC, uptime history.