Waves RPC endpoints: free public URLs by 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 has the lowest median latency of the 3 free public Waves RPC endpoints measured, 125 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/waves-rpc. 3 public endpoints, no key: nodes.wx.network, nodes.waves.exchange, nodes.wavesnodes.com. 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 →
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
Waves: 3 free public RPC endpoints answering `GET /blocks/last` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Waves.Exchange leads at 125 ms. 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 live today, 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.
Results: 3 free public Waves RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | Waves.Exchange | 125 ms | 153 ms | 288 ms | 100.00% |
| 2 | Waves Exchange Node | 126 ms | 151 ms | 360 ms | 100.00% |
| 3 | Waves Foundation | 135 ms | 228 ms | 405 ms | 100.00% |
Public Waves RPC endpoints measured
The 3 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.
Waves.Exchangehttps://nodes.wx.network125 ms100.0%- Waves Exchange Node
https://nodes.waves.exchange126 ms100.0% - Waves Foundation
https://nodes.wavesnodes.com135 ms100.0%
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 Waves RPC endpoints work without an API key?
3 endpoints are probed on this chain: 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities