RPCsLive

Flow RPC endpoints: free public URLs by 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 Access Node has the lowest median latency of the 2 free public Flow RPC endpoints measured, 28 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/flow-rpc. 2 public endpoints, no key: access.mainnet.nodes.onflow.org, rest-mainnet.onflow.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 →

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

Flow: 2 free public RPC endpoints answering HTTP GET /v1/blocks?height=sealed every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Flow Access Node leads at 28 ms. 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 live today, 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.

Results: 2 free public Flow RPC endpoints ranked by p50 latency (24h, 3 regions)

Flow RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Flow Access Node28 ms58 ms105 ms100.00%
2Flow Foundation29 ms59 ms106 ms100.00%

Public Flow RPC endpoints measured

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.

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.

Frequently asked

Which Flow RPC endpoints work without an API key?

2 endpoints are probed on this chain: 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.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities