Network Tool
Latency Checker
See the real round-trip latency from each OrbitServers location to your connection — or to Jito, Helius Sender, Astralane, Nozomi, bloXroute, OrbitFlare and custom endpoints — measured live from every edge.
Latency by location
Round-trip time measured from each location to your connection. If a location can't reach you, your network is likely dropping ICMP (ping). The server-to-Jito reference is always shown for context.
Frankfurt
Germany
London
UK
Amsterdam
Netherlands
New York
USA
Salt Lake City
USA
Tokyo
Japan
Ashburn
USA
Los Angeles
USA
Common Questions
Latency Checker — FAQ
From a server co-located with a Jito edge, expect sub-millisecond round trips. From another city, tens of milliseconds is normal. Our Jito latency benchmarks page shows the continuously measured numbers per location.
Your network is almost certainly dropping ICMP (ping). Home routers, VPNs, and some ISPs block it by default. The tool needs your public IP to answer pings; try from a server or a network that allows ICMP.
That provider publishes no endpoint in that region, so there is nothing local to measure. We never ping a stand-in host from another city and present it as local latency.
Looking-glass nodes inside each OrbitServers data center run a real ping to the target and report the round-trip time. It is the same measurement path behind our published benchmarks, triggered on demand.
Up to 12 runs per minute. Endpoint results are also cached briefly and shared, so switching between targets is usually instant.