Traceroute Explained: What It Is & How to Use
See how traceroute maps the hops between your device and a site, what its timings mean, and how to read the results to find where a connection slows down.
Your video keeps buffering, your game lags, and your internet feels slow — but your Wi-Fi signal looks fine. I have been there, and the problem is rarely your router. It sits somewhere along the path your data takes across the internet, and traceroute shows you exactly where.
This guide explains what traceroute is, how it works, and how to run it on Windows, Mac, and Linux — then how to read the results.
Traceroute maps the path your data takes to a website, hop by hop. On Windows run tracert example.com; on Mac or Linux run traceroute example.com. Hop 1 is your router — log in at 192.168.1.1 if the delay starts there.
What is traceroute?
Traceroute is a command-line tool that shows the route your data takes from your computer to a website or server. It lists each router along the way, called a hop, with the time that hop took to answer.
I use it when a site is slow or will not load, because it tells me where the delay starts. Ping only tells me something is wrong; traceroute tells me where.

The tool sends small packets toward the destination and waits for replies. Each router that answers shows up as one line in the output, with three times — one for each probe packet sent.
How traceroute works
Traceroute works with a clever trick. Every IP packet carries a Time-To-Live (TTL) value, and each router lowers it by one. When it hits zero, the router drops the packet and sends back a message.
- Traceroute sends a packet with a TTL of 1. The first router drops it and replies, so you learn hop 1 and its time.
- It sends another packet with a TTL of 2, which reaches the second router, and then a TTL of 3, and so on.
- Traceroute records each reply with its time, and the list grows until the packet reaches the destination.
The default limit is 30 hops, which is enough for almost any route. If the trace stops early with asterisks, that hop is not answering, not necessarily broken. I see this limit work fine on home networks.
Example traceroute output
I read the output like a journey log. Each line is one stop, and the three times show how steady that stop is.
| Hop | Address | Times |
|---|---|---|
| 1 | 192.168.1.1 | 1 ms, 1 ms, 1 ms |
| 2 | 10.20.30.1 | 8 ms, 7 ms, 9 ms |
| 3 | 203.0.113.45 | 22 ms, 21 ms, 23 ms |
| 4 | 93.184.216.34 | 28 ms, 27 ms, 29 ms |
Hop 1 is your own router at 1 ms, which is normal. The times grow as the packets travel further, and a sudden jump at one hop is the clue you are looking for.
How to run traceroute on Windows
Windows calls the command tracert, and it comes built in. I run this first on home networks. Nothing to install, and it works from Command Prompt or PowerShell.
- Press Win + R, type cmd, and press Enter to open Command Prompt.
- Type tracert followed by the destination, for example tracert google.com, then press Enter.
- Wait for the trace to finish. Each line appears as the packets come back, usually in under a minute.
- Add -d to skip DNS lookups and speed it up: tracert -d google.com.
Windows tracert uses ICMP echo requests. The -h option raises the maximum hops from the default 30, and -w sets the timeout per reply in milliseconds.
How to run traceroute on macOS
On a Mac the command is traceroute, and Terminal includes it. I run this the same way on home networks. The steps are the same shape as Windows, with a different command name.
- Open Terminal from Spotlight or from Applications, then Utilities.
- Type traceroute followed by the destination, for example traceroute google.com, then press Enter.
- Wait for the trace to finish, then read the hops from top to bottom.
macOS traceroute uses UDP probes by default. If you see only asterisks, try -I to switch to ICMP probes, which many routers answer more reliably.
How to run traceroute on Linux
Linux works like macOS, but some distributions need you to install the tool first. The install takes one command, and then it works the same way. I see this setup on home networks all the time.
- Open Terminal. If traceroute is not installed, install it with sudo apt install traceroute on Debian or Ubuntu, or sudo dnf install traceroute on Fedora.
- Type traceroute followed by the destination, for example traceroute google.com, then press Enter.
- Wait for the trace to finish, then read the hops from top to bottom.
Linux traceroute has the most options. The -T option sends TCP probes to a port, which helps when the path blocks both UDP and ICMPh.
Traceroute options worth knowing
I keep the defaults for a first run, then add one option at a time. Each option answers a different question about the route.
| Option | What it does | Example |
|---|---|---|
| -m / -h | Maximum hops to try | traceroute -m 10 example.com |
| -w | Wait time for each reply | traceroute -w 3 example.com |
| -q | Probes sent per hop | traceroute -q 5 example.com |
| -n | Show IPs, skip hostnames | traceroute -n example.com |
| -I / -T | Use ICMP or TCP probes | traceroute -I example.com |
| -d (Windows) | Skip DNS lookups, faster | tracert -d example.com |
Save the output for support with a redirect: traceroute example.com > traceroute-results.txt. A saved trace is worth more than a description when you report a fault.
How to read traceroute results
I read the output in three passes: the times, the asterisks, and the place where things change. That order keeps me from blaming the wrong hop.

Latency: the time each hop took to answer. A hop that jumps from 8 ms to 180 ms is the traffic jam. Small rises along the route are normal, because distance adds time.
Timeouts: asterisks mean a hop did not answer in time. One silent hop often means that router ignores traceroute, not that it is broken. Several in a row near the end usually means the same thing.
Hop 1: your own router. If hop 1 is slow or times out, the problem is inside your home. Check your Wi-Fi with our WiFi settings guide before you call your ISP.
If the delay starts past hop 1, the problem is outside your home. Note the hop where the times jump, and give that line to your ISP — it tells them exactly where to look.
Traceroute vs ping
Ping and traceroute both send packets, but they answer different questions. I use ping for a quick yes or no, and traceroute when I need the where.
| Tool | What it tells you | When to use it |
|---|---|---|
| Ping | Whether a device answers, and how fast | Quick check if a site is up |
| Traceroute | Every hop on the path, with times | Find where a slowdown starts |
Ping returns one summary: the fastest response times to the target. Traceroute returns a step-by-step report of every node the data crossed, which is what you need to find a bottleneck.
Tracert vs traceroute
The only real difference is the operating system. Windows calls the tool tracert, while macOS and Linux call it traceroute. Both do the same job: map the network path and show the time for each hop.
The options differ a little between them, so use the flags for your own system. Windows uses -h for max hops; macOS and Linux use -m for the same thing.
Common uses for traceroute
I reach for traceroute in four situations, and each one is about finding where a problem lives rather than guessing.
- Finding network problems: a site will not load, or it loads slowly, and the trace shows which hop is stuck.
- Checking performance: the trace highlights delays and bottlenecks along the path, so you know what to fix.
- Understanding data routes: sometimes data takes a long, strange path, and the trace shows you the detour.
- Helping your ISP fix issues: providers use traceroute to spot routing problems that hit many customers at once.
If you cannot reach your router at all, find your real gateway first with our Router IP Finder. A wrong gateway address looks like a dead network, but it is only a wrong number.
Best practices for using traceroute
A traceroute is only useful if you read it carefully. These habits keep the results honest. I follow these habits myself on home networks.
- Know what it is for: traceroute finds where a problem is, it does not fix it.
- Keep it simple: run traceroute followed by the destination, nothing fancy, on the first try.
- Read the output hop by hop. One slow hop is a clue; one silent hop usually is not.
- Run it at different times. Peak and off-peak traces show what is normal and what is a real fault.
- Pair it with ping. Ping checks if a device answers; traceroute shows the whole path to it.
Traceroute turns the invisible journey of your data into something you can track. Run it once when things are fine, so you know what normal looks like when they are not.
Running traceroute: what users ran into
Lines of “Request timed out” in the middle
A DigitalOcean user saw several timed-out hops but the trace still reached the destination. Those hops usually just block or drop traceroute probes and are not losing real traffic.
Timeouts at the very start
InMotion Hosting notes that timeouts in the first one or two hops are normal when the rest of the trace runs, since the local device simply does not answer.
Timeouts all the way to the end
If the stars continue to the last hop and ping also fails, there is real loss or a firewall at that point. A Cisco community answer adds that a destination firewall can block the probes while web pages still load.










