Flare RPC endpoints: free public URLs by latency
HTTP round-trip latency for the `eth_getBlockByNumber("latest", false)` method against every free, no-key public Flare EVM endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Ankr has the lowest median latency of the 3 free public Flare RPC endpoints measured, 71 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/flare-rpc. Chain ID 14. 3 public endpoints, no key: rpc.ankr.com, flare-api.flare.network, flare.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 →
Flare is an EVM-compatible L1 blockchain (chain 14) specialising in cross-chain data acquisition, featuring native enshrined oracles (FTSOv2 for price feeds, FDC for cross-chain attestation), no staking-for-security requirement, FLR as its gas token, and ~1.8 s block cadence. The 2026-08-04 audit confirms 3 clean keyless providers: the Flare Foundation official endpoint (flare-api.flare.network/ext/bc/C/rpc), dRPC (flare.drpc.org), Thirdweb (14.rpc.thirdweb.com), and Ankr (rpc.ankr.com/flare). Excluded: Alchemy (no Flare route), QuickNode (key required).
Methodology
Flare: 3 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Ankr leads at 71 ms; the chain-official endpoint measures 150 ms. We measure the round-trip latency of a single, identical JSON-RPC call (`eth_getBlockByNumber("latest", false)`) against every no-key public Flare endpoint that sustains continuous probing, 3 providers measured, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Flare-scaled staleness gap (20 blocks at Flare's ~2 s block time). The cross-chain view lives on the parent `rpc-capabilities` benchmark; this page is the Flare-scoped answer with per-region breakdowns as a first-class dimension.
- Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
- Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest", false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
- Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Flare-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to `chain="flare"`. Provider coverage: 3 no-key endpoints.
Results: 3 free public Flare RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Ankr | 71 ms | 121 ms | 218 ms | 100.00% (n=4320) |
| 2 | Flare Foundation | 150 ms | 449 ms | 598 ms | 99.91% (n=4309) |
| 3 | dRPC | 174 ms | 247 ms | 384 ms | 99.98% (n=4320) |
Public Flare RPC endpoints measured
Chain ID 14, currency FLR. The 3 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.
Ankrhttps://rpc.ankr.com/flare71 ms100.0%
Flare Foundationhttps://flare-api.flare.network/ext/bc/C/rpc150 ms99.9%
dRPChttps://flare.drpc.org174 ms100.0%
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://14.rpc.thirdweb.com1.5 % success over 24 h
Frequently asked
Which Flare RPCs work without an API key?
4 endpoints are probed on this chain: Flare Foundation (https://flare-api.flare.network/ext/bc/C/rpc), dRPC (https://flare.drpc.org), Thirdweb (https://14.rpc.thirdweb.com), and Ankr (https://rpc.ankr.com/flare). Every listed endpoint was live-verified with a `eth_getBlockByNumber` POST returning a parsable response before inclusion.
How is Flare RPC latency measured here, technically?
One identical `eth_getBlockByNumber("latest", false)` POST every 60 seconds against each provider from each of 3 regions, using the same plain HTTP client the rest of the RPC cluster uses. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus `quantile_over_time` over 24 hours. Responses are classified (`ok` / `http_err` / `jsonrpc_err` / `stale` / `timeout`) so an endpoint stuck on an old head or returning errors behind HTTP 200 is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities