Path diagnostics

How to run and interpret traceroute on Windows, macOS, and Linux

Traceroute is path evidence, not automatic proof that the first slow or silent hop is broken.

Safety boundary: Use these instructions only for a router or network you own or are authorised to manage. Never enter a router password, Wi-Fi password, SSID, serial number or private network data into Router Portal.
Quick answer: Windows uses tracert example.com; macOS/Linux commonly use traceroute example.com. Read repeated patterns, not one row.

Commands

PlatformCommandNote
Windowstracert example.comCommand Prompt; flags vary
macOStraceroute example.comTerminal; check man page
Linuxtraceroute example.comInstall only from official distro guidance

Read a row

ItemMeaning
Hop numberPosition in path
Hostname/IPWhen revealed
Probe timesResponse time in ms
* * *No response; filtering is possible

Patterns

  • A spike that normalises later may be reply prioritisation.
  • A persistent rise from one point onward is more useful evidence.
  • Asterisks can mean filtering or rate limiting.
  • A final timeout does not prove the destination is down.

Repeat and redact

Compare times, destinations and wired/wireless paths. Redact public IPs, hostnames, usernames and timestamps before sharing output. Pair with a ping test.

Frequently asked questions

What does traceroute prove?

Only the responding path and timing from that method and moment.

Why is an intermediate hop slow?

It may deprioritise probes while forwarding traffic normally.

Is tracert the same command?

Similar purpose, different OS implementation and flags.