Flare public RPC endpoints, tested
Every keyless Flare (chain ID 14) 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 13 HTTP endpoints were working.
Working HTTP endpoints
| Endpoint | Latency | Behind best | eth_getLogs | State |
|---|---|---|---|---|
| https://flare.drpc.org | 25 ms | 0 blocks | under 1,000 | none |
| https://flare-api.flare.network/ext/C/rpc | 27 ms | 13 blocks | under 1,000 | none |
| https://rpc.ankr.com/flare | 105 ms | 11 blocks | 10,000+ | archive (1M+) |
| https://rpc.au.cc/flare | 310 ms | 7 blocks | 10,000+ | none |
| https://rpc.swiftnodes.io/rpc/flare (SwiftNodes, keyless: 2 req/s) | 1185 ms | 5 blocks | under 1,000 | none |
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/flare(SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes
Listed but not working
flare-bundler.etherspot.io: no answer (HTTP 410)flare.enosys.global/ext/C/rpc: chainId: fetch failed01-gravelines-003-01.rpc.tatum.io/ext/bc/C/rpc: chainId: rate limited01-vinthill-003-02.rpc.tatum.io/ext/bc/C/rpc: chainId: rate limitedflare.solidifi.app/ext/C/rpc: chainId: timeoutlb.routeme.sh/rpc/evm/14: chainId: rate limitedflare-mainnet.gateway.tatum.io: chainId: rate limitedflare.rpc.thirdweb.com: eth_blockNumber failed
Test any endpoint yourself with the RPC tester. Our Flare endpoint, limits and status: Flare RPC, uptime history.