Traceroute (MTR)
Map the network path to a host hop by hop, with latency and packet-loss for each router along the way.
MTR combines traceroute and ping: it shows every router (hop) between the server and your target and continuously measures latency and packet loss at each one. That makes it far better than plain traceroute for spotting where a connection degrades.
Enter a host above to trace the path to it from this server.
Frequently asked questions
What causes packet loss at one hop but not later ones?
Some routers rate-limit or deprioritise the ICMP responses used for tracing, so they report loss while still forwarding real traffic fine. Loss that persists to the final hop is the concern.
Why does the path differ from my own traceroute?
The trace runs from this server, so it follows that server's route to the target — different from the path out of your own network.
What is a hop?
Each hop is one router the packets pass through on the way to the destination.