Master Traceroute: Step‑by‑Step Guide to Network Path Diagnosis

What is Traceroute?

Traceroute is a network diagnostic tool that shows the route and latency of packets from your computer to a target host.

Step 1: Open Terminal or Command Prompt

Linux/macOS: open the terminal application.

Windows: open Command Prompt (cmd) or PowerShell.

Step 2: Syntax

Linux/macOS: traceroute [options] <target> Windows: tracert [options] <target> The <target> can be a domain name (e.g., example.com) or an IP address (e.g., 8.8.8.8).

Step 3: Run a Basic Traceroute

Linux/macOS: traceroute example.com Windows: tracert example.com This displays a list of intermediate hops and the round‑trip time for each hop.

Step 4: Analyze the Output

Each line typically contains:

Hop number : sequence of the hop.

Router IP or hostname : address of the hop.

RTT : three round‑trip time measurements.

Example output:

1  192.168.1.1   1.123 ms 0.567 ms 0.456 ms
2  10.0.0.1      10.456 ms 9.876 ms 8.123 ms
3  93.184.216.34 30.567 ms 29.876 ms 28.123 ms
4  example.com   50.345 ms 48.567 ms 49.234 ms

If you see * * *, the packet was blocked or experienced high latency at that hop.

Step 5: Advanced Options

Linux/macOS Options

-m <max_hops>

: set maximum number of hops (default 30). Example:

traceroute -m 20 example.com

-q <queries>

: set number of probes per hop (default 3). Example:

traceroute -q 5 example.com

-I

: use ICMP instead of UDP. Example:

traceroute -I example.com

-T

: use TCP instead of UDP. Example:

traceroute -T example.com

-p <port>

: set destination UDP port. Example:

traceroute -p 8080 example.com

Windows Options

-h <max_hops>

: set maximum hops. Example:

tracert -h 15 example.com

-w <timeout>

: set timeout in milliseconds. Example:

tracert -w 500 example.com

-d

: disable hostname resolution, show only IP addresses. Example:

tracert -d example.com

Step 6: Common Use Cases

Diagnose network problems – locate where packets are delayed or lost.

Analyze performance – measure latency of each hop to identify bottlenecks.

Bypass firewalls – use -T (TCP) or -I (ICMP) to avoid UDP blocks.

Test specific ports (Linux/macOS) – traceroute -p 443 example.com.

Step 7: Troubleshooting

If you see * * *, the router may block traceroute packets or the hop has high latency. Try -I or -T to use a different protocol.

If the command is not found, install it (e.g., sudo apt install traceroute on Debian/Ubuntu or sudo yum install traceroute on Red Hat/CentOS).

Tips

Combine with ping to test stability of a specific hop: ping <IP>.

Use mtr on Linux for real‑time statistics (combines traceroute and ping).

On Windows, pathping provides traceroute plus packet‑loss analysis.