Fantom public RPC endpoints, tested
Every keyless Fantom (chain ID 250) 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. 12 of 22 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://fantom-mainnet.gateway.tatum.io | 28 ms | 2 blocks | under 1,000 | none |
| https://rpc.fantom.network | 37 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://rpc3.fantom.network | 37 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://fantom.drpc.org | 43 ms | 3 blocks | under 1,000 | archive (1M+) |
| https://rpc.swiftnodes.io/rpc/fantom (SwiftNodes, keyless: 2 req/s) | 57 ms | 1 blocks | under 1,000 | archive (1M+) |
| https://rpcapi.fantom.network | 64 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://rpc2.fantom.network | 64 ms | 3 blocks | 10,000+ | archive (1M+) |
| https://lb.routeme.sh/rpc/evm/250 | 70 ms | 0 blocks | under 1,000 | none |
| https://fantom.api.pocket.network | 84 ms | 2 blocks | 10,000+ | archive (1M+) |
| https://fantom.api.onfinality.io/public | 155 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://api.zan.top/ftm-mainnet | 175 ms | 2 blocks | under 1,000 | archive (1M+) |
| https://public.1rpc.io/ftm | 496 ms | 1 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
- streams
fantom.drpc.org: first head after 5723 ms - does not stream
fantom-rpc.publicnode.com: connection failed (connect) - does not stream
fantom.callstaticrpc.com: connection failed (connect) - does not stream
rpc.swiftnodes.io/ws/fantom(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
rpc.ftm.tools: chainId: message: API key not found, json-rpc code: -32050, rest code: 401fantom-rpc.publicnode.com: no answer (HTTP 404)fantom-public.nodies.app: no answer (HTTP 403)fantom-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API insterpc.fantom.gateway.fm: chainId: fetch failedendpoints.omniatech.io/v1/fantom/mainnet/public: no answer (HTTP 521)fantom-json-rpc.stakely.io: chainId: fetch failedrpc.owlracle.info/ftm/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)fantom.therpc.io: chainId: fetch failedpublic-ftm-mainnet.fastnode.io: chainId: fetch failed
Test any endpoint yourself with the RPC tester. Our Fantom endpoint, limits and status: Fantom RPC, uptime history.