About Arbitrum Latency
Real-time latency monitoring for the Arbitrum One sequencer.
What is Arbitrum Latency?
Arbitrum Latency continuously measures the round-trip time from probes around the world to the Arbitrum One sequencer — the single machine that orders every transaction on the chain. There is no other way onto Arbitrum: whether a transaction arrives through a public RPC provider or is submitted directly, it must reach this sequencer to be included.
The sequencer runs in AWS us-east-2 (Ohio). The map shows how far each region is from it in network terms, and where co-location pays.
Why It Matters: Timeboost
Arbitrum orders transactions first-come-first-served, with one twist: Timeboost auctions off an express lane every minute. The auction winner's transactions are sequenced ahead of everyone else's, while non-express transactions absorb a small artificial delay.
The express lane raises the price of speed — it doesn't replace it. The controller still races its own reaction time to market events, and everyone else still queues first-come-first-served behind the delay. In both cases, the distance between your servers and the sequencer is the floor on how fast you can act. That floor is what this map measures.
Methodology
| Target | arb1-sequencer.arbitrum.io/rpc |
| Measurement | Each probe submits a fixed signed transaction via eth_sendRawTransaction. |
| Metric | Time to first byte of the sequencer's response over a warm connection — network round trip plus a few milliseconds of validation. p50 over 60-second windows. |
| Connection | Each probe pins the fastest sequencer gateway IP for consistency and re-checks DNS every five minutes, so a sequencer infrastructure move shows up as an annotated step-change rather than noise. |
Research Project Disclaimer
Arbitrum 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.