What we measure

Hyperliquid: WebSocket round-trip to api.hyperliquid.xyz via AWS CloudFront, plus direct TCP latency to Hyperliquid validator nodes in Tokyo (AZ1, AZ2, AZ4) and real order-to-fill timing.

Solana: QUIC handshake latency to every voting Solana mainnet validator (~760 nodes), real-time leader-rotation tracking, stake-weighted best-co-location rankings, and Jito Block Engine paths across all 8 regional endpoints (Amsterdam, Frankfurt, London, Dublin, New York, Salt Lake City, Tokyo, Singapore).

SUI: TCP+TLS handshake latency to every active SUI mainnet validator with Mysticeti consensus. Reports time-to-quorum (latency to accumulate signatures from 2/3 of stake-weighted voting power) and time-to-90% supermajority — the metrics that actually bound transaction finality on a DAG-BFT chain.

Centralized exchanges (CEX): WebSocket and FIX latency to Binance, Coinbase, Kraken, OKX, Bybit, Bitmex, Deribit across spot, perpetuals, expiry futures, and options venues. Cross-exchange comparison mode picks the closest venue for a given product from any probe.

Prediction markets: REST round-trip to Polymarket (clob.polymarket.com, origin AWS eu-west-2 London) and Kalshi (api.elections.kalshi.com, origin AWS us-east-2 Ohio).

HFT oracle gateways: Pyth Lazer (Tokyo bare metal), Stork JP (AWS Tokyo), Switchboard Crossbar (GCP eu-west4), Chainlink Data Streams (Cloudflare US). Co-location guide for trading on oracle-dependent prices.

Why infrastructure location matters

For trading firms racing to be first into a price move, physical distance to exchange matching engines and blockchain validators dominates total latency. A server in the wrong city can lose by tens to hundreds of milliseconds — enough to lose every arbitrage and MEV opportunity to better-located competitors. This site publishes the actual measured numbers, continuously, so operators can make data-driven hosting decisions instead of guessing.

CEX Hyperliquid Prediction Markets Solana SUI Oracle Glassnode Studio→

← Back to map

About Hyperlatency

Real-time latency monitoring for Hyperliquid's API and validator network.

What is Hyperlatency?

Hyperlatency continuously measures network latency to Hyperliquid's trading infrastructure from probes deployed around the world.

WebSocket RTT to the Hyperliquid API
TCP/TLS breakdown
Direct TCP to all 24 validators
Data refreshes every 5 seconds

Why It Matters

Hyperliquid's validators are concentrated in Tokyo. HFT firms, market makers, and automated strategies all benefit from understanding latency to Hyperliquid's infrastructure. Hyperlatency tracks the lag experienced from probe locations worldwide, giving you the data to make informed infrastructure decisions.

Gossip & Order Priority

Hyperliquid documents two priority mechanisms: gossip priority for faster receipt of transaction data, and order priority for IOC orders in HIP-3 markets, with fees charged from undelegated staking balance in HYPE terms.

These mechanisms add protocol-level priority, but they sit on top of normal network latency and infrastructure rather than replacing them. Priority fees can improve your position, not erase a network-speed disadvantage.

Research Project Disclaimer

Hyperlatency is a research project provided for informational and educational purposes only. The latency metrics displayed (including WebSocket RTT, TCP/TLS breakdowns, and direct validator latencies) are measured from specific geographic probe locations using our distinct server environments. Actual latency may differ. Real-world network performance is highly volatile and depends on numerous factors, including your specific ISP routing, local network congestion, cloud provider variances (e.g., AWS vs. GCP routing to Tokyo), and hardware stack. Therefore, these numbers should be viewed as estimates and directional baselines.

Glassnode Latency Monitor — Real-Time Crypto Trading Infrastructure Latency