Windows

To perform a trace route on Windows, click Start, then Run, and type cmd and click OK (type command for Windows Millennium, 98, and 95).

You'll be prompted if you want to modify the shortcut. We recommend that you do apply these settings to the shortcut so that you won't have to do this again.
Now you're ready to begin the traceroute. Type the following in the black command box:

tracert yoursite.com

Replacing yoursite.com with your actual domain name, and press ENTER. Once you do so, you will see the results of the trace route. It may take a while, so please be patient. When it is done, please copy and paste the information by highlighting the contents of the black command box and pasting it into notepad, or an e-mail message to our support staff.

While our support staff can use this information to diagnose connectivity problems to your site, you can also look at it and see yourself which nodes along the way of your connection to our servers are not working, or how they are performing. Any * on the right side of the results indicates that the node in question didn't respond in time. The last node that causes this problem before a wide series of failures is often the offending node.

Linux / MacOS X

To perform a trace route on Linux, UNIX, or Mac OSX, open up a command window and type the following:

traceroute yoursite.com

Replacing yoursite.com with your actual domain name, and press ENTER. Once you do so, you will see the results of the trace route. It may take a while, so please be patient. When it is done, please copy and paste the information by highlighting the contents of the black command box and pasting it into notepad, or an e-mail message to our support staff.

While our support staff can use this information to diagnose connectivity problems to your site, you can also look at it and see yourself which nodes along the way of your connection to our servers are not working, or how they are performing. Any * on the right side of the results indicates that the node in question didn't respond in time. The last node that causes this problem before a wide series of failures is often the offending node.