Fantom RPC endpoints: free public URLs by latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Fantom EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Fantom Foundation has the lowest median latency of the 2 free public Fantom RPC endpoints measured, 121 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/fantom-rpc. Chain ID 250. 2 public endpoints, no key: rpcapi.fantom.network, fantom.drpc.org. Full URLs with their 24h median are listed below.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Fantom Opera (chain 250) is a DAG-based EVM-compatible L1 using Lachesis aBFT consensus, delivering ~1-2 second finality with FTM as the gas token. 2 keyless endpoints are probed continuously: the Fantom Foundation official gateway (rpcapi.fantom.network), dRPC (fantom.drpc.org), Ankr (rpc.ankr.com/fantom), Thirdweb (250.rpc.thirdweb.com), and Blast API (fantom-mainnet.public.blastapi.io).
Methodology
Fantom: 2 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Fantom Foundation leads at 121 ms; the chain-official endpoint measures 121 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Fantom endpoint that sustains continuous probing, 2 providers live today, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) so the leaderboard rewards sustained availability rather than fast error messages. The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Fantom-scoped answer with per-region breakdowns as a first-class dimension.
Results: 2 free public Fantom RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Fantom Foundation | 121 ms | 123 ms | 126 ms | 100.00% |
| 2 | dRPC | 143 ms | 174 ms | 253 ms | 99.65% |
Public Fantom RPC endpoints measured
Chain ID 250, currency FTM. The 2 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Private providers (API key) are never listed with a URL.
Fantom Foundationhttps://rpcapi.fantom.network121 ms100.0%
dRPChttps://fantom.drpc.org143 ms99.7%
Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.
Declared, but not answering our probes
This endpoint is named in the spec and probed on the same schedule as the rest, and answers too rarely to carry a median. Below 5 % success we leave it out of the table rather than publish a latency drawn from a handful of replies. A provider can serve a browser and refuse a datacenter, so this says what a server deployment would meet, not what the endpoint is capable of.
- Thirdweb
https://250.rpc.thirdweb.com0.6 % success over 24 h
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities