Traceroute (called tracert on Windows) is a network diagnostic tool that shows every router your data passes through on its way to a destination — and how long each hop takes. It’s like GPS tracking for internet packets.
How Traceroute Works
Traceroute sends packets with increasing TTL (Time to Live) values. Each router that handles a packet decrements the TTL by 1. When it reaches 0, the router sends back an error message identifying itself. Traceroute uses these error messages to map each hop:
- Packet with TTL=1 → first router responds
- Packet with TTL=2 → second router responds
- And so on until the destination is reached
How to Run Traceroute
Windows: Open Command Prompt → tracert google.com
Mac/Linux: Open Terminal → traceroute google.com
You’ll see a list of hops with their IP addresses and round-trip times in milliseconds (three measurements per hop).
How to Read Traceroute Output
- * * * — The router didn’t respond (firewall blocking ICMP) — not necessarily a problem
- High latency at one hop: That router may be congested or distant
- Latency drops after a high hop: Usually just that router deprioritising ICMP — not a real bottleneck
- Request timed out at end: The destination may be blocking traceroute
- Consistent high latency from hop X onwards: The bottleneck is at or before hop X
What Traceroute Is Used For
- Identifying where exactly in the network a connection is failing
- Finding which ISP or network is causing high latency
- Diagnosing routing loops
- Seeing how traffic is routed internationally
- Network troubleshooting for IT administrators
Traceroute vs Ping
Ping tells you if a destination is reachable and how long one round trip takes. Traceroute tells you the full path and where delays occur. Use ping first to confirm a problem, then traceroute to locate it.