Fastest free Vana RPC, live no-key endpoint latency
HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Vana RPC endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Vana Foundation leads rpc latency at 179 ms (p50, 24h) on Fastest free Vana RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/vana-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Vana (chain 1480) is an EVM-compatible L1 designed for data liquidity networks (DLNs) where users tokenize and monetize personal data through Data DAOs. VANA is the native gas token. The Vana Foundation's rpc.vana.org provides keyless access probed every 60 seconds from three regions.
Methodology
Per-chain member of the RPC latency cluster, extended to Vana. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Vana endpoint that sustains continuous probing, 1 provider at launch, 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 Vana-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Vana RPC right now?
Vana Foundation currently leads at 179 ms (`eth_getBlockByNumber` p50 over the last 24h), measured against 1 no-key provider probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Vana RPCs work without an API key?
1 endpoint sustains continuous keyless probing at launch: Vana Foundation. Every listed endpoint was live-verified before inclusion.
Does the fastest Vana RPC change by region?
Often. The region tabs at the top of the page re-scope every number to a single origin; pick the one closest to where your requests originate.
How is Vana RPC latency measured here?
One identical JSON-RPC POST (`eth_getBlockByNumber`) every 60 seconds against each provider from each of 3 regions. Responses are classified so an endpoint stuck on an old head or returning errors is never ranked as fastest.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities