Ping and traceroute reader
Paste the output of ping, traceroute, tracert or mtr, and read it the way an engineer would: where the delay is actually added, which silent hops do not matter, and whether packets are really being lost.
完全在你的浏览器中运行 — 不会发送到任何地方
The two rules
- A delay that starts at a hop and continues to the end is real. A delay at one hop that later hops do not share is that router being slow to answer, not slow to forward.
- The same goes for loss. Loss that carries on to the destination is real; loss at one hop only is rate limiting.
Reading traceroute explains why, with examples, and how to report a network problem covers what to send your provider.
Which commands does it understand?
ping and traceroute on macOS and Linux, ping and tracert on Windows in English or Korean, and mtr reports (mtr -rw).
A hop shows * * *. Is that the problem?
Only if every hop after it is silent too. A silent hop followed by answering hops is a router that does not reply to traceroute, which is common and harmless.
Why run mtr instead of traceroute?
mtr sends many probes per hop and reports loss and averages, which separates real loss from routers that are merely slow to answer. Run it for a minute or two.
Is the output sent anywhere?
No. It is read in your browser, which matters because it often contains internal addresses.