Trace the network route to any domain or IP from the US, Europe, Asia or India - with latency and loss per hop.
Last updated:
Runs MTR (3 packets per hop) on a real server in that location.
| You see | Meaning |
|---|---|
| Latency jumps and stays high | A long link (ocean cable) or congestion from that hop on |
| Loss on one middle hop only | Usually harmless: the router limits its replies |
| Loss from a hop to the end | Real packet loss starting there |
| * * * at the end | The destination does not reply to traceroute (common) |
| Hops with the same ASN | Inside one provider's network |
| System | Command |
|---|---|
| Windows | tracert example.com |
| Mac / Linux | traceroute example.com |
| MTR (Linux / Mac) | mtr example.com |
| Windows (MTR-like) | pathping example.com |
Every router between the test location and the destination, with the delay and packet loss at each step.
Those routers do not answer traceroute packets. It is normal unless the trace stops completely.
My Traceroute sends several packets to each hop, so it shows average latency and loss, not just one sample.
Browsers cannot run traceroute. Use tracert (Windows) or traceroute (Mac/Linux) for your own route.
Often a long-distance link like an undersea cable, or congestion at that point.
Yes, free with no signup. A small number of tests per hour is allowed per connection.