The Network Trouble Shooter option provides you with access to a common network tracing utility named Traceroute. Traceroute does exactly what its name implies, tracing the route of data from your domain to the server you specify. The results of performing a Traceroute show you every server your packets of information are going to in order to connect to that server. The results can indicate if any of the servers along the way are causing connection problems by timing out or by slowing down the data flow. This is a good tool to use to help determine if a slow or downed connection is a problem on your server or someone else’s server. How To Use the Network Trouble Shooter:

1. From your Control Panel, select the Network Trouble
Shooter Option. The Traceroute Manager displays.

2. Directions for using Traceroute Manager appear on the screen. They are also summarized here.

3. To trace the connection from your web site to the place from which you are connecting, click on the From your domain to your IP number button. The results appear near the bottom of the Traceroute Manager screen.

4. To trace the connection from your website to any other location on the internet, type the name (or IP address) into the Server Name field, then select the Trace Route button. The results display near the bottom of the Traceroute Manager screen. Traceroute results show the "hops" made between servers, say between yours and ours, or the server that houses your site.

1.  BGW-VE1.dedicatedns.com (209.239.32.1) 0.730 ms 0.435 ms 0.426 ms
2.  BCR1-GE100.dedicatedns.com (64.176.255.250) 0.609 ms 0.485 ms 0.491 ms
3.  * 12.124.234.9 (12.124.234.9) 81.506 ms *
4.  gbr6-p80.wswdc.ip.att.net (12.123.9.62) 58.842 ms 96.767 ms *
5.  * gbr4-p90.wswdc.ip.att.net (12.122.5.206) 52.293 ms 59.006 ms
6.  ggr1-p370.wswdc.ip.att.net (12.123.9.53) 56.316 ms * *
7.   att-gw.dc.uu.net (192.205.32.134) 75.336 ms 74.674 ms 60.037 ms
8.   0.so-3-1-0.XR2.DCA8.ALTER.NET (152.63.35.194) 73.135 ms 53.633 ms *
9.   0.so-3-0-0.TR2.DCA8.ALTER.NET (152.63.144.29) 72.455 ms 60.206 ms 87.523 ms
10.  115.at-6-0-0.TR2.SAC1.ALTER.NET (146.188.141.118) 124.094 ms 96.275 ms *
11.  * * 127.ATM5-0.IR2.SAC1.ALTER.NET (152.63.11.113) 133.546 ms
12.  POS3-0.IR2.SAC2.ALTER.NET (137.39.31.209) 127.408 ms * *
13.  * 335.ATM5-0-0.TR2.SYD2.ALTER.NET (210.80.51.186) 288.363 ms 282.259 ms
14.  * * So-3-1-2.XR2.SYD2.Alter.Net (210.80.48.146) 333.223 ms
15.  * * *
16.  412.ATM8-0-0.GW1.PER1.ALTER.NET (210.80.32.114) 335.358 ms 334.015 ms *
17.  * per-uun-bdr1-atm3-0-100.iinet.net.au (203.166.7.142) 393.723 ms 394.724 ms
18.  * ragtime-02.iinet.net.au (203.59.24.126) 431.355 ms 430.133 ms
19.  * 203.59.14.3 (203.59.14.3) 407.269 ms *
20.  * * 203.59.16.19 (203.59.16.19) 380.756 ms
21.  i194-187.nv.iinet.net.au (203.59.194.187) 520.645 ms 511.212 ms *

The traceroute is like a road map showing each section of a browser's "trip" and how long it took to negotiate each "distance." The time measurements are in milliseconds (ms). You can also see that there are different networks (like different roads/hiways) involved along the way. For instance, above you can see lines 4-6 show the information "traveling" on an AT&T network. Our network is shown on lines 1,2. We would consider slow times to be 100 ms or longer. You can run a traceroute any time you are experiencing problems accessing your site, the results may help explain the nature of any problem. If the slowness appears to be in our network please copy the results into a ticket in our ticketing system and forward to us.

Back to Control Panel Details