IoTeX public RPC endpoints, tested
Every keyless IoTeX (chain ID 4689) 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. 6 of 11 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://api-iotex-mainnet.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c | 36 ms | 0 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/iotex (SwiftNodes, keyless: 2 req/s) | 108 ms | 2 blocks | 1,000 | recent only |
| https://babel-api.fastblocks.io | 36 ms | 10 blocks | 1,000 | recent only |
| https://babel-api.mainnet.iotex.one | 37 ms | 11 blocks | 1,000 | recent only |
| https://babel-api.mainnet.iotex.io | 90 ms | 12 blocks | 1,000 | recent only |
| https://iotex.api.onfinality.io/public | 115 ms | 8 blocks | under 1,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/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 failedrpc.chainanalytics.org/iotex: chainId: fetch failedlb.routeme.sh/rpc/evm/4689: chainId: rate limitediotex-network.rpc.thirdweb.com: chainId: rate limitediotexrpc.com: chainId: timeout
Test any endpoint yourself with the RPC tester. Our IoTeX endpoint, limits and status: IoTeX RPC, uptime history.