Hydration RPC endpoints: free public URLs by 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 has the lowest median latency of the 2 free public Hydration RPC endpoints measured, 154 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/hydration-rpc. 2 public endpoints, no key: rpc.hydradx.cloud, hydration-rpc.n.dwellir.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 →
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
Hydration: 2 free public RPC endpoints answering `chain_getHeader` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. Hydration leads at 154 ms; the chain-official endpoint measures 154 ms. 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 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 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.
- 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":"chain_getHeader","params":[]}. Plain HTTP POST. Substrate JSON-RPC.
- 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 Hydration-scoped view of the same harness, with the same exclusion rules.
- Chain scope: every query on this page is pinned to chain=hydration. Provider coverage today: 2 endpoints (Hydration official, Dwellir).
Results: 2 free public Hydration RPC endpoints ranked by p50 latency (24h, 3 regions)
| № | Providers | p50 | p90 | p99 | Success |
|---|---|---|---|---|---|
| 1 | HydrationHydration official public RPC (rpc.hydradx.cloud), keyless | 154 ms | 179 ms | 504 ms | 99.79% (n=4316) |
| 2 | DwellirDwellir public Hydration RPC (hydration-rpc.n.dwellir.com), keyless | 155 ms | 271 ms | 388 ms | 100.00% (n=4321) |
Public Hydration RPC endpoints measured
The 2 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.
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 Hydration RPC endpoints work without an API key?
2 endpoints are probed on this chain: 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.
Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities