traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. It's a great way to inspect the routing to your box.
How does it work
- Open the command prompt:
- Windows 7 or Vista: From the Start menu, in the search field, type "cmd" and then press Enter
- Previous versions: From the Start menu, select Run... . In the "Open:" box, type "cmd" and then press Enter
- At the command prompt, enter
On Linux and Mac OS X
Open the Terminal app and type
What does it mean?
You will get something like this:
Tracing route to www.indiana.edu [184.108.40.206] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms 220.127.116.11 2 10 ms 20 ms 20 ms indy-bloomington-s4-6.ivy.tec.in.us [18.104.22.168] 3 10 ms 10 ms 20 ms akicita-lena.ivy.tec.in.us [22.214.171.124] 4 20 ms 30 ms 30 ms indnet.ivy.tec.in.us [126.96.36.199] 5 71 ms 40 ms 50 ms ind-s1-0-7-T1.ind.net [188.8.131.52] 6 80 ms 40 ms 40 ms serverfarm-atm0.ind.net [184.108.40.206] 7 60 ms 90 ms 80 ms iupui-atm6-0-100.ind.net [220.127.116.11] 8 50 ms 40 ms 90 ms indy-dmz.atm.iupui.edu [18.104.22.168] 9 * * * Request timed out. 10 40 ms 70 ms 90 ms wcc6-gw.ucs.indiana.edu [22.214.171.124] 11 * 40 ms 50 ms viator.ucs.indiana.edu [126.96.36.199] Trace complete.
The first column, the hop count, represents the number of stops your information has made along the route to attempt to contact the other computer. The next three columns are the round-trip times in milliseconds for three different attempts to reach the destination. The last column is the name of the host that responded to the request.
The above example shows that a computer user on ivy.tec.in.us ran a traceroute to www.indiana.edu. On the fifth hop, the request left the Ivy Tech network and went to the ind.net network. On the eighth hop, the request went to the iupui.edu network. Finally, on the tenth hop, the request found its way to the indiana.edu network. Since there is a "Request timed out" message on the ninth hop, you might guess that there could be some problem between the iupui.edu network and the indiana.edu network. If you are seeing other problems, such as the web page at http://www.indiana.edu/ loading slowly, this could indicate the location of the problem.