How to Use Traceroute

How to Use Traceroute

Traceroute is an application that traces the path data takes from one computer to another. Basically, a traceroute is a map that shows what stops or locations that data must pass through in order to go from one computer to another.

To be an effective troubleshooting tool, the traceroute needs to be run during a time when the problem is occurring, from a computer that is experiencing the problem.

How do I run a traceroute?

To Run a Traceroute in Windows:

In Windows 8, 10, or 11, go to Start > Run and type cmd, and press the Enter key.

This will bring up a black command prompt window. It will have a line that looks like this:
C:Documents and Settings>
with a cursor blinking next to the > symbol.

To run the traceroute, type:
Where is the name of the server that you are having difficulty connecting to. The traceroute process may take only a few seconds or a few minutes. Typically, the farther you are away, geographically, from your target location, the longer the trace will take.

If you have difficulty copying the traceroute information, or if it runs off the screen, you can instead type:
tracert > C:trace.txt
This would write the command results to a text file named trace.txt in the root of your C: drive.

To Run a Traceroute on a Mac:

If you have Mac OS, you can use the built-in network tools. Double-click the Hard Drive icon > Applications folder > Utilities folder > Network Utility program. Select the Traceroute tab and enter the hostname or domain name.

Mac OS X users can also take advantage of the terminal that is built into the system. Inside the same Utility folder described above and open the program labeled Terminal. Once inside the terminal application type in the command traceroute Be sure to leave out the quotation marks and substitute the target server name or IP address instead of

If you have an older Macintosh, you may need to acquire third-party software utility software. Go to and do a search for Trace on Macintosh. Programs like the DNS Expert Professional will allow you to run a traceroute. Then send us the results for analysis.

To Run a Traceroute on Linux or UNIX:

At the command line, type:
Please note that should be replaced if the site is not working for you.


Let’s take a few samples traceroute outputs. The first is a successful trace:
Tracing route to []
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms
2 1 ms 1 ms 2 ms
3 4 ms 3 ms 1 ms
4 5 ms 4 ms 7 ms []
5 3 ms 11 ms 10 ms
6 3 ms 2 ms 7 ms
7 150 ms 153 ms 150 ms []
8 195 ms 205 ms 193 ms []
9 187 ms 205 ms 217 ms []
10 324 ms 329 ms 322 ms
11 314 ms 305 ms 304 ms []
12 310 ms 310 ms 313 ms []
13 313 ms 310 ms 310 ms

It looks like gibberish, right? But it actually fairly easy to understand. After the traceroute command, the program tells you what it doing;

It looked up the domain,
It found on the IP address of
Now it will now attempt to find its way there.

It will only be able to attempt 30 hops (stops along the way, or connections to routers) and it will send a packet of 40 bytes.

The numbers at the far left are the number of the hop, followed by the name and/or IP address of the router that hop is going through. You can see our trace started within the TechaByte network, progressed through AT&T and found its way to

The set of three numbers on the right side of the lines indicates the amount of time, in milliseconds, it took for that hop to complete. Traceroute performs each hop three times.

In this example, there are no asterisks (which indicate packet loss) and no inordinately long delays. If your trace to the server looks like this, you are in good shape in terms of network connectivity.

Now, let’s look at a traceroute that ends without reaching its destination:traceroute
traceroute to (, 30 hops max, 40 byte packets
1 (  0.947 ms  1.028 ms  1.101 ms
2 (  1.275 ms  1.308 ms  1.385 ms
3 (  1.849 ms  1.921 ms  1.980 ms
4 (  92.082 ms  92.155 ms  92.347 ms
5  * * *
6  * * *
7  * * *
8  * * *

Our trace to failed because we ran it from our internal network is not actually down. It’s just a nice, short example of what a failed trace looks like.

You can see on the fifth hop we have nothing but packet loss. The traceroute continued for the full 30 hops, each reporting * * * as it went. If your trace to the server has many asterisks like this one, that means that the connection was not able to be completed. ?This could be for a variety of reasons including:

A network outage
High amounts of traffic causing network congestion
A firewall dropping traffic from your IP

If you see these asterisks once you are inside TechaByte’s network, there may be no need to worry. VPS customers frequently are not able to trace to their instance on the parent server.

Having traceroute output ready is an excellent way to help us help you if you are experiencing network issues.

Image link
Hi! Welcome.
Some of our links might not be open as our website is still in development.
PLEASE accept Our Apology