Fastest free Flow RPC, live no-key endpoint latency
HTTP round-trip latency for the Flow Cadence REST endpoint (GET /v1/blocks?height=sealed) against every available public Flow node, audited every 60 seconds from 3 regions.
TL;DR. As of , Flow Foundation leads rpc latency at 90 ms (p50, 24h) on Fastest free Flow RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/flow-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Flow is a proof-of-stake L1 blockchain developed by Dapper Labs using a multi-role node architecture (Collector, Consensus, Execution, Verification) and the Cadence smart contract language. The Cadence chain commits roughly one block every 1 to 2 seconds with immediate deterministic finality. Public REST access nodes are operated by the Flow Foundation and accept GET /v1/blocks?height=sealed without an API key. Every provider was live-verified with consecutive sealed-block REST probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Flow. We measure the round-trip latency of a single REST GET to /v1/blocks?height=sealed against every available public Flow node that sustains continuous probing: 2 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / stale / timeout) with a Flow-scaled staleness gap (240 blocks, around 5 min). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Flow-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Flow RPC right now?
Flow Foundation currently leads at 90 ms (Flow sealed block height p50 over the last 24h), measured against 2 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Flow RPC endpoints work without an API key?
2 endpoints sustain continuous keyless probing at launch: the Flow Foundation REST node (rest-mainnet.onflow.org) and the Flow access node REST endpoint (access.mainnet.nodes.onflow.org). Every listed endpoint was live-verified with a GET /v1/blocks?height=sealed returning a parsable height before inclusion.
Does the fastest Flow RPC change by region?
Often. Public infra concentrates in specific regions; a gateway that wins from Amsterdam can lose from Singapore by multiples. The region tabs at the top of the page re-scope every number to a single origin.
How is Flow RPC latency measured here, technically?
One REST GET to /v1/blocks?height=sealed every 60 seconds against each provider from each of 3 regions. Wall-clock round-trip is recorded at millisecond precision; p50/p90/p99 are computed via Prometheus quantile_over_time over 24 hours. Best-effort measurements; p50 is the median, p90 the 90th percentile and p99 the 99th percentile of latency samples collected over the last 24 hours.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities