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 Prediction Markets Latency

Real-time latency monitoring for prediction market exchanges.

What is Prediction Markets Latency?

Prediction Markets Latency continuously measures network latency to prediction market trading infrastructure from probes deployed around the world.

REST API round-trip to Polymarket (clob.polymarket.com)
REST API round-trip to Kalshi (api.elections.kalshi.com)
TCP/TLS breakdown for each exchange
Data refreshes every 5 seconds

The Exchanges

Polymarket

Prediction market built on Polygon. Orders are placed through a centralized off-chain order book (CLOB) at clob.polymarket.com, then settled on-chain after matching. The API is behind Cloudflare CDN. Origin servers are on AWS eu-west-2 (London, UK).

Note: While Polymarket's infrastructure is hosted in London, it is not legal to trade Polymarket in England or the Netherlands. Trading infrastructure is typically co-located in nearby jurisdictions such as Dublin (AWS eu-west-1).

Kalshi

CFTC-regulated prediction market exchange. Fully centralized order book at api.elections.kalshi.com, behind AWS CloudFront CDN. Origin servers are in AWS us-east-2 (Ohio).

Why It Matters

Both Polymarket and Kalshi run centralized off-chain order books where all orders pass through a single API endpoint. Network latency to that endpoint directly affects order placement speed. Market makers, automated strategies, and active traders benefit from understanding which exchange is faster from their location.

Research Project Disclaimer

Prediction Markets Latency is a research project provided for informational and educational purposes only. The latency metrics displayed are measured from specific geographic probe locations using our distinct server environments. Actual latency may differ. Real-world network performance depends on numerous factors including ISP routing, local network congestion, and hardware. These numbers should be viewed as estimates and directional baselines.

Glassnode Latency Monitor — Real-Time Crypto Trading Infrastructure Latency