Fastest free Waves RPC, live no-key endpoint latency
HTTP round-trip latency for GET /blocks/last against every available public Waves node, audited every 60 seconds from 3 regions.
TL;DR. As of , Waves Exchange Node leads rpc latency at 194 ms (p50, 24h) on Fastest free Waves RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/waves-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Waves is a proof-of-stake blockchain optimised for decentralised finance and token creation, producing one block approximately every 60 seconds. The chain exposes a REST API at /blocks/last returning the latest committed block height as a plain integer. Public REST endpoints are available without an API key from the Waves Foundation, Waves.Exchange and nodes.waves.exchange. Every provider was live-verified with consecutive block probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Waves. We measure the round-trip latency of a single REST call (GET /blocks/last) against every available public Waves node that sustains continuous probing: 3 providers at launch, every 60 seconds, from us-east, eu-west and Singapore. The harness classifies every response (ok / http_err / jsonrpc_err / stale / timeout) with a Waves-scaled staleness gap (5 blocks, around 5 min at 60 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Waves-scoped answer with per-region breakdowns as a first-class dimension.
Frequently asked
What is the fastest free Waves RPC right now?
Waves Exchange Node currently leads at 194 ms (Waves block height p50 over the last 24h), measured against 3 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Waves RPC endpoints work without an API key?
3 endpoints sustain continuous keyless probing at launch: Waves Foundation nodes (nodes.wavesnodes.com), Waves.Exchange (nodes.wx.network) and WavesExchange (nodes.waves.exchange). Every listed endpoint was live-verified with a blocks/last call returning a parsable height before inclusion.
Does the fastest Waves 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 Waves RPC latency measured here, technically?
One GET /blocks/last REST call 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