Glassnode Latency Monitor — Real-Time Crypto Trading Infrastructure Latency

Live network latency from probes worldwide to crypto trading infrastructure and blockchains (Solana, SUI, Hyperliquid). Built for traders, HFT firms, market makers, and arbitrage operators choosing where to co-locate.

What we measure

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.

Probe infrastructure

Probes deployed worldwide 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). Probes run on Fly.io and AWS bare-metal instances.

CEXHyperliquidPrediction MarketsSolanaSUIOracleGlassnode Studio→

Coverage

Slot weighting is over the whole current epoch (the leader schedule for all 432k slots, ~2 days).
Probe latency is over only the last 90 minutes.

For reactive Solana HFT — strategies that submit transactions directly to the current leader's TPU port rather than pre-submitting to a block engine — latency to the validator is the only thing that matters. The table below shows what fraction of leader slots this epoch each probe can reach within 30, 50, and 100 ms.

If you're in Frankfurt and 56% of slots are inside 30 ms, that's your probability of winning a direct-TPU race on any given slot. If you're in Tokyo and only 10% of slots are inside 30 ms, you're already out of the race nine times out of ten.

By probe

#LocationProvider< 30 ms ↓< 50 ms ↕< 100 ms ↕Distribution
Loading coverage data…
< 30 ms < 50 ms < 100 ms