IoTeX public RPC endpoints, tested
Every keyless IoTeX (chain ID 4689) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: 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. 5 of 10 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://babel-api.mainnet.iotex.one | 48 ms | 1 blocks | 1,000 | recent only |
| https://babel-api.mainnet.iotex.io | 63 ms | 3 blocks | 1,000 | recent only |
| https://babel-api.fastblocks.io | 156 ms | 0 blocks | 1,000 | recent only |
| https://iotex.api.onfinality.io/public | 111 ms | 687784 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/iotex (SwiftNodes, keyless: 2 req/s) | 463 ms | 5 blocks | under 1,000 | recent only |
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/iotex(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.depinscan.io/iotex: chainId: fetch failediotexrpc.com: chainId: fetch failedapi-iotex-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limitedlb.routeme.sh/rpc/evm/4689: eth_blockNumber failediotex-network.rpc.thirdweb.com: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our IoTeX endpoint, limits and status: IoTeX RPC, uptime history.