Fastest free Hydration RPC, live no-key endpoint latency
HTTP round-trip latency for chain_getHeader against every free, no-key public Hydration Polkadot parachain endpoint, audited every 60 seconds from 3 regions.
TL;DR. As of , Hydration posts the lowest rpc latency at 19 ms (p50, 24h) on Fastest free Hydration RPC, live no-key endpoint latency. Source: OpenChainBench, https://openchainbench.com/benchmarks/hydration-rpc.
Companion page
Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →
Hydration (formerly HydraDX) is an Omnipool-based DEX parachain on Polkadot enabling single-sided liquidity provision across assets. HDX is the native token. It produces one block every 6 seconds via the Polkadot relay and exposes a Substrate JSON-RPC interface. Public keyless endpoints are available from Hydration official and Dwellir. Every provider was live-verified with consecutive chain_getHeader probes at launch.
Methodology
Per-chain member of the RPC latency cluster, extended to Hydration. We measure the round-trip latency of a single Substrate JSON-RPC call (chain_getHeader) against every available public Hydration parachain node that sustains continuous probing: 2 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 Polkadot-scaled staleness gap (40 blocks, around 4 min at 6 s/block). The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Hydration-scoped answer with per-region breakdowns.
Frequently asked
What is the fastest free Hydration RPC right now?
Hydration currently leads at 19 ms (Hydration block number p50 over the last 24h), measured against 2 providers probed every 60 seconds from us-east, eu-west and Singapore. The leaderboard re-sorts continuously against fresh Prometheus samples.
Which Hydration RPC endpoints work without an API key?
2 endpoints sustain continuous keyless probing at launch: Hydration official (rpc.hydradx.cloud) and Dwellir (hydration-rpc.n.dwellir.com). Every listed endpoint was live-verified with a chain_getHeader call returning a parsable block number before inclusion.
Does the fastest Hydration 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 Hydration RPC latency measured here, technically?
One chain_getHeader Substrate JSON-RPC POST 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities