Traceroute on a 3D globe
See the path your packets take: every router with its network, city and response time, drawn hop by hop on a globe you can turn.
Our server sends the trace and shows the routers on the way. The first hops are inside our own network and appear as IP-FD.net without an address.
Route
Hops
| # | Router | Network | Location | Time |
|---|
How to read it
A traceroute sends packets with a growing hop limit. Every router on the way answers once, which gives its address and the time the answer took. We add the network (AS) that runs each router, its reverse DNS name and where it is.
Router locations are estimates. Most backbone routers carry a city code in their name (fra, ams, lhr), which we read first. Without one we use our stored location for the address. A place that cannot be right for the measured time is left off the globe: light in fibre covers about 100 km per millisecond of round trip.
A hop with no answer is a router that does not reply to traces, not a broken link. Higher times on one hop only matter when the hops after it are slow too.
To trace from your own computer, run traceroute -n example.com (Linux, macOS), tracert example.com (Windows) or mtr -rwb example.com and paste the output above.