drag to turn · scroll to zoom

latency.zone

Thirty datacentres, timed from this browser. Every wire runs at the speed of its own round trip.

opening sockets

0 of 32 answered · 0.0s

Your nearest datacentre is —, 0.0 ms away — near enough that the wire barely has time to glow.

— sits 0.0× further than the globe says it should, which is what a bad route looks like from here.

Your quickest path runs at 0% of light in fibre, and everything you send pays 0.0 ms before it leaves town.

Your timings put you near —. Solved in this tab, never sent anywhere.

Distance here is round-trip time, not kilometres. What gets measured is the path to a provider's edge — routes bend around oceans, peering and congestion — so this is the shape of the internet from where you sit, not the shape of the earth.

Method

How it works

Your browser times HTTPS requests to about thirty cloud regions whose cities are published. Each host is warmed up once — that first request pays DNS, TCP and TLS and is thrown away — then sampled five times, keeping the minimum, which is the cleanest estimate of a true round trip.

Those milliseconds become a distance matrix. Stress majorisation solves for where each city has to sit in space for the distances to hold, Procrustes turns the answer back onto the real globe so your continent stays recognisable, and a biharmonic spline drags every coastline along with the thirty anchors. Press Warp to latency and the planet reshapes itself so that how far a city sits from you is how long it took to answer — swelling wherever the internet is slower than the map says it should be.

No account, no cookie, no analytics, no server. Close the tab and it is gone.