Networking
Traceroute Analyzer
Paste traceroute, tracert or mtr output and get a straight answer: the last hop that replied, whether the destination was ever reached, and whether the silence after it is a firewall, a filtered router or real packet loss.
Route output
Needed only when the output has no header line to read it from — mtr --report,
for instance. With it, the tool can say whether the last hop that replied is your
destination.
Verdict
replied partial loss no reply rejected last confirmed hop
Summary
What the path is telling you
Hop by hop
| # | Hop | Network | Best | Avg | Loss | Status |
|---|
Reading a trace honestly
- A silent hop in the middle means nothing. Plenty of routers are configured not to send ICMP time-exceeded messages. If a later hop answers, the packets went straight through the quiet ones.
- A silent tail is not proof of an outage. Hosts and firewalls routinely drop
traceroute probes while happily serving traffic. Confirm with the real protocol —
traceroute -T -p 443,nc -vz host 443orcurl -v— before you escalate. - Rising latency at one hop is not that hop's fault. The number is the round trip to the router, on the router's slow control plane. What matters is whether the increase carries through to every hop after it.
Runs entirely in your browser — nothing you type here is uploaded, logged or stored. Privacy policy