Traceroute: definition, explanation, and why it matters

Definition

A diagnostic that maps the sequence of routers (hops) a packet traverses to reach a destination, along with the latency to each hop.

Plain-English explanation

Traceroute sends probes with increasing TTL values, so each router along the path is forced to respond. The result is a hop-by-hop view of the route and the delay introduced at each step.

It is the canonical tool for localizing where a problem starts — your home, your ISP, an intermediate carrier, or the destination network.

Real-world examples

• If hops 1–3 are healthy (low latency) and hop 4 jumps to 200 ms, the bottleneck is at that hop's network.
• Asymmetric routes are common — the path back from the server may take a completely different sequence.

Why it matters

Traceroute moves troubleshooting from guessing to evidence. It shows whether the issue is your network or somebody else's.

Common misconceptions

• Myth: A traceroute hop showing '* * *' means that router is down.
  Reality: Many routers deliberately deprioritize or block ICMP responses. Missing replies don't necessarily mean a failure.

Frequently asked questions

Why does traceroute show different paths to the same site?

Routes change as carriers rebalance traffic. Different probes can take different paths even within seconds.