How Do I Run A Traceroute?
To Run a Traceroute in WindowsThe command application (cmd.exe) is used to run a traceroute on Windows. Launching it is slightly different depending on your version of Windows:
- In Windows 7:
- click on the Start menu
- type “cmd” and press Enter to get a command prompt.
- In Windows 8:
- move your mouse to the bottom-left corner of the screen to bring up the Start icon.
- Right-click on Start and select Run.
- Then type “command” and press Enter to launch the application.
- Alternatively, you can type “command” into the Search field in the Charms menu after moving your mouse to the lower right corner of your desktop.
- In Windows 10, type “command” into the search menu and press Enter for a command prompt.
tracert domainname.cominto the command prompt, where “domainname.com” is the name of the server to which you are having difficulty connecting. The traceroute may take only a few seconds or a few minutes. Typically, the closer you are to the server, geographically, the more quickly the traceroute will complete.
To Run a Traceroute in Mac OS XIf you have a Mac, you can use the built-in network tools to run a traceroute.
- Launch Spotlight (with ⌘ + SPACE or by clicking on the magnifying glass in your menu) to search for and launch Network Utility.
- Select the Traceroute tab and enter the hostname or domain name.
- You also can perform a traceroute from the Terminal app. Simply enter:
To Run a Traceroute in LinuxAt the command line, type:
What Does the Traceroute Show You?Let’s take a few sample traceroute outputs.
traceroute msu.eduThe output from that command shows a successful trace:
traceroute to msu.edu (188.8.131.52), 30 hops max, 40 byte packets 1 lw-dc2-hsrp-vlan132.rtr.liquidweb.com (184.108.40.206) 1.330 ms 1.420 ms 1.554 ms 2 lw-dc2-core4-po2.rtr.liquidweb.com (220.127.116.11) 1.092 ms 1.311 ms 1.451 ms 3 lw-dc1-core1-ge3-5.rtr.liquidweb.com (18.104.22.168) 1.596 ms 1.897 ms 2.209 ms 4 lw-dc1-border3-ge4.rtr.liquidweb.com (22.214.171.124) 1.657 ms 1.748 ms 1.894 ms 5 126.96.36.199 (188.8.131.52) 4.748 ms 5.382 ms 5.453 ms 6 cr81.dtrmi.ip.att.net (184.108.40.206) 12.893 ms 12.035 ms 11.043 ms 7 cr1.cgcil.ip.att.net (220.127.116.11) 11.509 ms 11.615 ms 11.769 ms 8 18.104.22.168 (22.214.171.124) 10.645 ms 10.711 ms 10.760 ms 9 126.96.36.199 (188.8.131.52) 9.473 ms 9.537 ms 9.605 ms 10 xe-0-0-0x14.msu6.mich.net (184.108.40.206) 15.047 ms 14.458 ms 14.487 ms 11 220.127.116.11 (18.104.22.168) 16.976 ms 20.066 ms 20.137 ms 12 cc-t1-ge1-23.net.msu.edu (22.214.171.124) 20.228 ms 20.432 ms 20.312 ms 13 www.msu.edu (126.96.36.199) 16.856 ms 17.071 ms 16.341 msIt looks like gibberish, right? But it’s actually fairly easy to understand. After the traceroute command, the program tells you what it’s doing:
- It has looked up the domain msu.edu
- It found msu.edu on the IP address of 188.8.131.52
- It now will attempt to find its way there using no more than 30 “hops” (stops along the way, or connections to routers), and it will send a packet of 40 bytes.
Note: When troubleshooting network latency by analyzing the time of each hop, please be aware that distance from your geographic location to the server is a factor. Any single hop covering a large physical distance (such as when crossing an ocean) naturally will take longer to complete.In this example, there are no asterisks (which indicate a failure to respond within 5 seconds) and no inordinately long delays. If your traceroute to your VPS server looks like this, you’re in good shape in terms of network connectivity. Now, let’s look at a simulated traceroute that ends without reaching its destination:
traceroute to liquidweb.com (184.108.40.206), 30 hops max, 40 byte packets 1 lw-dc2-hsrp-vlan132.rtr.liquidweb.com (220.127.116.11) 0.947 ms 1.028 ms 1.101 ms 2 lw-dc2-core4-po2.rtr.liquidweb.com (18.104.22.168) 1.275 ms 1.308 ms 1.385 ms 3 lw-dc1-core1-ge3-5.rtr.liquidweb.com (22.214.171.124) 1.849 ms 1.921 ms 1.980 ms 4 lw-dc1-dist1-ge1.rtr.liquidweb.com (126.96.36.199) 92.082 ms 92.155 ms 92.347 ms 5 * * * 6 * * * 7 * * * 8 * * * [truncated]In this example, our trace failed because we deliberately ran it from our internal network (just to demonstrate what a failed trace would look like). You can see that, beginning 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 traceroute to the server ends with asterisks like this one, and never displays an IP address or server name after the asterisks, 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 address
Note: If you see these asterisks once you are inside Liquid Web’s network, there may be no need to worry. VPS customers frequently are not able to trace to their instance on the parent server.If you believe you are experiencing network issues, having the output of traceroute handy and providing it, along with your public IPV4 address (which you can obtain from http://ip.liquidweb.com) when contacting Heroic Support® is an excellent way to help us begin investigating the issue as quickly as possible.