Glassnode Latency Monitor — Real-Time Crypto Trading Infrastructure Latency

Live network latency from probes worldwide to crypto trading infrastructure and blockchains (Solana, SUI, Hyperliquid, Arbitrum One, Robinhood Chain, Base, X Layer). 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.

← Back to map

About X Layer Latency

Real-time latency monitoring for X Layer.

What is X Layer Latency?

X Layer is OKX's Layer 2, built on the OP Stack. Every transaction is ordered by a single sequencer, and there is no other route onto the chain — whatever path a transaction takes, it has to reach that sequencer to be included.

How To Read These Numbers

X Layer sits behind a CDN (Amazon CloudFront), so every measurement passes through a nearby edge server on its way to the sequencer. On busy routes that edge keeps a connection open onward and the cost is negligible. On quiet ones it opens a fresh one far more often, and that setup is not a small fixed overhead — it repeats the journey, landing at roughly three times the usual figure.

That is why Sydney can read higher than cities much further from Hong Kong. Its shortest measured path is among the best outside Asia, but little traffic flows that way, so the typical figure carries the setup cost far more often. It is a real cost users in those regions pay, which is why we show it rather than smoothing it out. The lowest figures for each probe give the underlying distance.

Why It Matters

X Layer produces a block roughly every second. Fees compete for position inside a block, but arrival time decides which block a transaction makes at all — and once that block is built, a later transaction cannot buy its way into it. Paying for priority raises the price of speed rather than removing the need for it. That distance is what this map measures.

Methodology

Targetrpc.xlayer.tech
MeasurementEach probe submits a fixed signed transaction via eth_sendRawTransaction.
MetricTime to first byte of the response over a warm connection — network round trip plus a few milliseconds of validation. p50 over 60-second windows.

Research Project Disclaimer

X Layer 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. This project is not affiliated with or endorsed by X Layer or OKX.

Want this data programmatically?
A REST API for all latency data is in the works. Join the waitlist and we'll email you once at launch