Glassnode
Glassnode has launched a live Latency Monitor that continuously measures network latency from probes deployed across 14 cities to the trading infrastructure that matters for crypto execution: Hyperliquid's WebSocket API and Tokyo validator nodes, every voting Solana mainnet validator (~760 nodes) plus the full set of Jito Block Engine regional endpoints, all active SUI mainnet validators with time-to-quorum and time-to-90% supermajority metrics, and WebSocket and FIX paths into Binance, Coinbase, Kraken, OKX, Bybit, Bitmex, and Deribit. The product also covers Polymarket and Kalshi REST endpoints and HFT-tier oracle gateways including Pyth Lazer, Stork JP, Switchboard Crossbar, and Chainlink Data Streams — the inputs that bound oracle-dependent pricing on Solana and SUI perps.
Why it matters
For trading firms racing into a price move, physical distance to matching engines and validator sets dominates total latency — a server in the wrong city can lose by tens to hundreds of milliseconds, more than enough to forfeit every arbitrage and MEV opportunity to better-located competitors. The data set that matters is the actual measured number, not the marketing claim from a colocation provider, and that is the gap Glassnode is filling. Prediction markets are a particularly sharp illustration: Polymarket's clob endpoint originates in AWS eu-west-2 London while Kalshi's api.elections.kalshi.com sits in AWS us-east-2 Ohio, so a firm trading both venues has to choose which choke point to optimize for — there is no single deployment that wins both.
Market impact
The monitor reframes hosting decisions for market makers and HFT books away from intuition toward measured input. On Solana, stake-weighted best-colocation rankings and leader-rotation tracking let a firm place infrastructure in the region that sees the next leader first; on SUI, time-to-quorum and time-to-90% supermajority translate network distance into the actual finality budget a DAG-BFT chain offers. Cross-exchange comparison mode lets a single probe identify the closest venue for a given product, collapsing the legwork of running the matrix internally.
Frequently asked questions
-
What does the Glassnode Latency Monitor actually measure?
It measures live network latency from probes in 14 cities to Hyperliquid (WebSocket + Tokyo validator nodes), every voting Solana mainnet validator plus all 8 Jito Block Engine endpoints, all active SUI validators (with time-to-quorum and time-to-90% supermajority), and WebSocket/FIX paths into Binance, Coinbase,…
-
Why does physical location matter this much for crypto trading?
For trading firms racing into a price move, physical distance to matching engines and validator sets dominates total latency. A server in the wrong city can lose by tens to hundreds of milliseconds — enough to forfeit every arbitrage and MEV opportunity to better-located competitors.
-
Why are prediction markets a special case in the dataset?
Polymarket's clob endpoint originates in AWS eu-west-2 London while Kalshi's api.elections.kalshi.com sits in AWS us-east-2 Ohio. A firm trading both venues has to pick which choke point to optimize for — there is no single deployment that wins both, and the monitor publishes the measured gap.
-
How does this help Solana and SUI operators specifically?
On Solana, stake-weighted best-colocation rankings and leader-rotation tracking let firms place infrastructure in the region that sees the next leader first. On SUI, time-to-quorum and time-to-90% supermajority translate network distance into the actual finality budget a DAG-BFT chain offers.
-
Where are the probes deployed?
Probes run on Fly.io and AWS bare-metal instances across Asia (Tokyo multi-AZ, Seoul, Hong Kong, Singapore), Europe (Amsterdam, Dublin, London, Frankfurt), the Americas (Ashburn, Ohio, Chicago, San Jose, São Paulo), and Oceania/Africa (Sydney, Johannesburg).
WuBlockchain
CoinTelegraph
CoinDesk
TheBlock