RPCsUpdated

Vana RPC endpoints: free public URLs by 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 is the only free public Vana RPC endpoint measured, at 55 ms (p50, 24h, 3 regions). 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

Vana: 1 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Vana Foundation leads at 55 ms; the chain-official endpoint measures 55 ms. 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.

  • 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.
  • 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 Vana-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to `chain="vana"`. Provider coverage today: 1 no-key endpoints (Vana Foundation).

Results: 1 free public Vana RPC endpoint ranked by p50 latency (24h, 3 regions)

Vana RPC endpoints: free public URLs by latency: RPC latency per provider (p50, 24h).
№Providersp50p90p99Success
1Vana FoundationVana Foundation's official public RPC55 ms59 ms60 ms100.00% (n=4321)

Frequently asked

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.

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