Network tools

Traceroute online with a map: every hop between Frankfurt and any host

Type an IP address or a domain. We run a traceroute from our server in Frankfurt, stream each hop as it answers and put every router on the map with its country, provider and round-trip time.

Try 8.8.8.8, 1.1.1.1 or google.com. IPv4 and domains, up to 22 hops.

Trace from

What a traceroute shows you

Hop by hop, and why the first ones look the same every time.

Traceroute follows the path your packets take to a host. Every router on the way (a hop) answers with its IP address, and we add the hostname, the country, the provider and how long the reply took. The map draws the route in the order the hops came back.

Our probe runs on a Hetzner VPS in Frankfurt. The first few hops are always Hetzner's own backbone, before the packets reach the public internet. That is normal and expected.

Traceroute follows the packet path hop by hop and measures round-trip time at every router

How to use it

  1. Enter an IPv4 address or a domain name in the field above and press Trace.
  2. The trace runs in the background on our Frankfurt server and streams hops live as they arrive.
  3. Each hop gets its country, flag, ISP and ASN from our own IP lookup database.
  4. The map plots every responding hop and draws the full route as a line. Timeouts are skipped on the map.

Each hop is probed three times, so the time column shows the average and, when the replies differ, the jitter. Results are cached for an hour per target, and you can start six traces a minute. If you only want to know whether a host answers at all, the ping test is quicker.

Questions we get a lot

Mostly about hops that look odd but are fine.

Why do early hops show Hetzner / Germany?
The trace starts on our Frankfurt server, so the first hops are Hetzner's internal backbone before the packets reach the public internet. It does not mean your destination is at Hetzner.
Why do some hops show * * *?
Many routers are set not to answer traceroute probes. Those hops are skipped on the map but still counted in the sequence.
How accurate is the geolocation?
We use the same database as the rest of IPWhois.net. Router locations are approximate, often the ISP's hub city rather than the exact building.
Why is this different from my local traceroute?
Routing is dynamic and asymmetric. Our trace starts in Frankfurt, so the path differs from one run on your own machine or from another country.