MTR (My Traceroute)
Ping every hop along the path to a host, live and on a rolling basis, to see exactly where loss and latency happen as the run continues.
Pings every hop along the path on a rolling basis, live — takes about 15-20 seconds. ICMP may be blocked at some hops even when the path itself is fine.
Enter a host or IP to run MTR
Every hop along the path gets pinged live, on a rolling basis, so loss and latency show up per hop, all the way to the destination.
MTR combines Traceroute's hop discovery with Ping's repeated-probe statistics: it finds every router along the path, then pings each one on a rolling basis for the length of the run, showing live loss%, and last/average/best/worst round-trip time per hop.
A hop showing loss while every hop after it shows none is usually that specific router deprioritizing ICMP for its own traffic, not a real problem — the path is still fine, since traffic actually reaching the destination doesn't take the same shortcuts a diagnostic probe does. Loss that persists at a hop and at every hop after it is the real signal worth investigating.
This run is bounded — a fixed number of cycles, not an open-ended session — long enough to catch the kind of intermittent loss a single traceroute pass would miss, without holding a live probe running indefinitely.