Post the results of your trace route here. Here are two guides for running a trace route.

Here's a guide for Windows:

http://www.mediacollege.com/internet/troubleshooter/traceroute.html

Here's one for Mac:

http://support.verio.com/documents/view_article.cfm?doc_id=3693

 

Subscribing

 

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 7 ms L100.PRVDRI-VFTTP-32.verizon-gni.net [74.103.242.1]
3 6 ms 7 ms 7 ms G10-0-5-232.PRVDRI-LCR-02.verizon-gni.net [130.81.180.24]
4 11 ms 11 ms 12 ms P11-0-0.PRVDRI-LCR-01.verizon-gni.net [130.81.27.66]
5 11 ms 12 ms 12 ms so-3-3-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.29.28]
6 16 ms 16 ms 17 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
7 17 ms 17 ms 17 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
8 11 ms 12 ms 14 ms 0.xe-7-0-0.BR2.NYC4.ALTER.NET [152.63.3.166]
9 16 ms 11 ms 15 ms 204.255.168.90
10 15 ms 14 ms 14 ms cr1-tengig-0-8-3-0.NewYork.savvis.net [204.70.198.13]
11 22 ms 22 ms 21 ms cr1-tengig-0-15-0-0.Washington.savvis.net [204.70.196.101]
12 26 ms 24 ms 24 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]
13 24 ms 24 ms 24 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
14 22 ms 22 ms 21 ms corporate-executive-board.Washington.savvis.net[208.174.119.98]
15 22 ms 21 ms 21 ms sc-smv1160.servint.net [207.58.153.136]
16 24 ms 21 ms 24 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

 

Re: When the site is running slowly or non responsive please run a traceroute an

This probably won't show anything worthwhile because I couldn't get to this post for the instructions whilst it was hanging, lol. By the time I got in, it stopped acting up, but I did it anyway for fun and excitement.

traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2766.042 ms 2.401 ms 1.866 ms
2 10.96.200.1 (10.96.200.1) 9.281 ms 11.051 ms 9.573 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 10.415 ms 7.373 ms 7.757 ms
4 70.169.76.229 (70.169.76.229) 9.390 ms 8.798 ms 10.003 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 21.891 ms 29.601 ms 21.981 ms
6 207.88.186.153.ptr.us.xo.net (207.88.186.153) 22.443 ms
te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 24.868 ms 29.896 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 85.175 ms 85.071 ms
te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 27.034 ms
8 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 85.254 ms 88.239 ms
te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 85.309 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 86.735 ms
te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 86.756 ms
te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 85.391 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 86.508 ms 83.950 ms 84.095 ms
11 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 78.941 ms 82.021 ms 88.979 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 87.165 ms 83.799 ms 83.637 ms
13 209.50.254.25 (209.50.254.25) 82.832 ms 82.684 ms 89.109 ms
14 sc-smv1160.servint.net (207.58.153.136) 82.421 ms 81.448 ms 82.882 ms
15 vps.theturboforums.com (207.58.161.157) 79.180 ms 81.133 ms 81.792 ms

 

Looks like #10 timed out ....


Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 7 ms 7 ms L100.PRVDRI-VFTTP-32.verizon-gni.net [74.103.242.1]
3 5 ms 7 ms 7 ms G10-0-5-232.PRVDRI-LCR-02.verizon-gni.net [130.81.180.24]
4 11 ms 12 ms 12 ms P11-0-0.PRVDRI-LCR-01.verizon-gni.net [130.81.27.66]
5 57 ms 12 ms 12 ms so-3-3-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.29.28]
6 34 ms 29 ms 32 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
7 17 ms 16 ms 19 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
8 18 ms 42 ms 14 ms 0.xe-8-0-0.BR2.NYC4.ALTER.NET [152.63.3.130]
9 15 ms 14 ms 14 ms 204.255.168.90
10 16 ms * * cr1-tengig-0-8-3-0.NewYork.savvis.net [204.70.198.13]
11 22 ms 22 ms 21 ms cr1-tengig-0-15-0-0.Washington.savvis.net [204.70.196.101]
12 28 ms 25 ms 24 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]
13 25 ms 24 ms 25 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
14 22 ms 21 ms 22 ms corporate-executive-board.Washington.savvis.net[208.174.119.98]
15 22 ms 21 ms 21 ms sc-smv1160.servint.net [207.58.153.136]
16 24 ms 21 ms 25 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

C:\Users\OSL>

 

Sat for about 10 min trying to open this thread... all the time the traceroute was sub 10ms except this try... I dont think its the connection, I think its how the DB cache is settup or possibly the application server's cache is settup.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

H:\>tracert www.theturboforums.com

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 2 ms 5 ms 2 ms 10.0.6.1
2 <1 ms <1 ms <1 ms 10.0.0.1
3 1 ms <1 ms <1 ms 10.0.255.130
4 1 ms 2 ms 2 ms 152.161.136.185
5 14 ms 13 ms 13 ms 152.176.48.118
6 39 ms 40 ms 39 ms 204.235.124.34
7 13 ms 14 ms 13 ms 204.235.124.1
8 14 ms 13 ms 13 ms ge-9-2.car3.Washington1.Level3.net [4.79.168.49]

9 118 ms 86 ms 225 ms ae-11-79.car1.Washington3.Level3.net [4.68.17.71
] 10 14 ms 14 ms 14 ms XO-COMMUNIC.car1.Washington3.Level3.net [4.71.20
4.26]
11 16 ms 15 ms 16 ms vb2000d1.rar3.washington-dc.us.xo.net [207.88.13
.62]
12 15 ms 15 ms 15 ms ae0d0.mcr1.washington-dc.us.xo.net [216.156.0.34
]
13 27 ms 198 ms 41 ms ip65-46-126-202.z126-46-65.customer.algx.net [65
.46.126.202]
14 17 ms 17 ms 18 ms 209.50.254.9.254.50.209.in-addr.arpa [209.50.254
.9]
15 16 ms 16 ms 16 ms 209.50.254.25
16 16 ms 15 ms 16 ms sc-smv1160.servint.net [207.58.153.136]
17 16 ms 16 ms 16 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

H:\>

 

Based on how the site behaves - If I had to make a guess, I would say that the network is fine, if anything its probably the MYSQL server - either the indexes or maybe even how the query cache is configured.

-Jason

 

A single hop or two showing *s in the middle or higher latentcy is not a huge deal. The *s are likely because that router is blocking ICMP. Network difficulties tend to be more where one hop suddenly spikes, and then the rest do too or where the last hops are *s. That is also where a lot of cross nation web sites tend to get a big increase in ping times. For any of you people that are on a unix based OS mtr may be a better option to reflect packet loss.

 

Re: When the site is running slowly or non responsive please run a traceroute an

Maybe I caught this one in time. It simply refused to go 'back' out of a thread to the index and was still hanging by the time I finished the traceroute.

traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2298.365 ms 0.596 ms 1.661 ms
2 10.96.200.1 (10.96.200.1) 9.281 ms 7.469 ms 7.754 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 9.507 ms 9.243 ms 7.717 ms
4 70.169.76.229 (70.169.76.229) 7.392 ms 9.070 ms 9.485 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 20.553 ms 30.144 ms 22.020 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 23.160 ms 22.157 ms 23.319 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 84.186 ms 85.221 ms 86.315 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 85.894 ms 85.171 ms 83.763 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 83.807 ms 84.032 ms 83.820 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.321 ms 84.234 ms 83.916 ms
11 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 79.652 ms
ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 83.515 ms 83.008 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 254.189 ms 80.972 ms
ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 77.543 ms
13 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 126.352 ms
209.50.254.25 (209.50.254.25) 80.690 ms
209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 208.022 ms
14 sc-smv1160.servint.net (207.58.153.136) 79.452 ms 79.949 ms
209.50.254.25 (209.50.254.25) 80.489 ms
15 vps.theturboforums.com (207.58.161.157) 78.906 ms 79.021 ms 81.055 ms

 

Re: When the site is running slowly or non responsive please run a traceroute an

I did both of these two while it was hanging @ midnight pacific

traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 1751.223 ms 0.573 ms 1.051 ms
2 10.96.200.1 (10.96.200.1) 10.697 ms 6.719 ms 6.060 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 7.946 ms 6.318 ms 8.117 ms
4 70.169.76.229 (70.169.76.229) 9.134 ms 9.948 ms 8.118 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 20.158 ms 23.153 ms 19.832 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 21.759 ms 20.659 ms
207.88.186.153.ptr.us.xo.net (207.88.186.153) 21.141 ms
7 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 21.735 ms
vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 83.413 ms 86.829 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 84.789 ms 85.174 ms
vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 83.437 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 84.241 ms 89.879 ms 94.444 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.204 ms
te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 85.367 ms
ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.354 ms
11 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 78.634 ms 80.595 ms 79.834 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 79.060 ms 82.049 ms 80.838 ms
13 209.50.254.25 (209.50.254.25) 79.277 ms 80.058 ms 80.076 ms
14 sc-smv1160.servint.net (207.58.153.136) 123.579 ms 81.556 ms 81.933 ms
15 vps.theturboforums.com (207.58.161.157) 80.925 ms 79.940 ms 80.363 ms


traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 1.792 ms 2.686 ms 2.409 ms
2 10.96.200.1 (10.96.200.1) 10.446 ms 9.271 ms 8.305 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 10.722 ms 6.885 ms 7.873 ms
4 70.169.76.229 (70.169.76.229) 11.438 ms 8.304 ms 9.586 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 22.921 ms 21.211 ms 23.770 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 23.314 ms 21.385 ms 21.730 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 85.271 ms 86.063 ms 84.470 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 84.388 ms 83.408 ms 84.783 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 84.802 ms 83.064 ms 86.333 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.966 ms 83.581 ms 84.133 ms
11 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 81.625 ms
ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 83.265 ms
ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 79.189 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 79.425 ms 79.473 ms 80.574 ms
13 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 80.273 ms 79.139 ms 82.149 ms
14 sc-smv1160.servint.net (207.58.153.136) 81.227 ms 84.922 ms 82.002 ms
15 sc-smv1160.servint.net (207.58.153.136) 77.664 ms
vps.theturboforums.com (207.58.161.157) 79.991 ms 78.971 ms

 

Re: When the site is running slowly or non responsive please run a traceroute an

Here's a fun one. It was completely unresponsive a few minutes ago (~2:04 pacific), so I gave it a try and got this for a response. The lines with the asterisks took about five seconds each.

traceroute to theturbofoums.com (72.215.225.9), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2769.984 ms 0.602 ms 0.447 ms
2 10.96.200.1 (10.96.200.1) 6.135 ms 6.176 ms 6.245 ms
3 emescmtu05-atm010002.ph.ph.cox.net (68.2.2.234) 7.986 ms 7.941 ms 5.716 ms
4 70.169.73.41 (70.169.73.41) 9.055 ms 9.125 ms 9.741 ms
5 paltbprj02-ae2.0.rd.pt.cox.net (68.1.2.160) 32.902 ms 33.686 ms 33.902 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 ip72-215-225-9.at.at.cox.net (72.215.225.9) 56.335 ms * *

 

Tracing route to theturboforums.com [207.58.161.157]

over a maximum of 30 hops:



1 3 ms 2 ms 1 ms williamsrouter1 [192.168.1.1]

2 6 ms 9 ms 5 ms L100.WASHDC-VFTTP-46.verizon-gni.net [173.66.249.1]

3 6 ms 13 ms 6 ms 4-1-646.WASHDC-LCR-06.verizon-gni.net [130.81.59.150]

4 7 ms 7 ms 4 ms so-4-2-0-0.RES-BB-RTR2.verizon-gni.net [130.81.28.146]

5 7 ms 4 ms 7 ms 0.so-6-1-0.XL4.IAD8.ALTER.NET [152.63.36.237]

6 7 ms 4 ms 15 ms 0.xe-10-1-0.BR1.IAD8.ALTER.NET [152.63.41.157]

7 7 ms 9 ms 4 ms te4-1-0d0.cir1.ashburn-va.us.xo.net [206.111.0.209]

8 8 ms 7 ms 7 ms vb2000d1.rar3.washington-dc.us.xo.net [207.88.13.62]

9 25 ms 24 ms 36 ms ae0d0.mcr1.washington-dc.us.xo.net [216.156.0.34]

10 15 ms 12 ms 12 ms ip65-46-126-202.z126-46-65.customer.algx.net [65.46.126.202]

11 13 ms 10 ms 11 ms 209.50.254.9.254.50.209.in-addr.arpa [209.50.254.9]

12 12 ms 9 ms 9 ms 209.50.254.25

13 11 ms 11 ms 10 ms sc-smv1160.servint.net [207.58.153.136]

14 10 ms 12 ms 12 ms vps.theturboforums.com [207.58.161.157]



Trace complete.

This was done at 12:00:24 pm on 5/9/2010, Just in case you wanna check your logs. You should already have my IP...

 

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 10 ms 10 ms 10.144.0.1
3 9 ms 8 ms 11 ms 172.23.9.225
4 10 ms 10 ms 21 ms 172.23.9.1
5 25 ms 25 ms 25 ms 12.125.176.117
6 28 ms 25 ms 27 ms cr2.phlpa.ip.att.net [12.123.224.210]
7 23 ms 24 ms 26 ms cr2.phlpa.ip.att.net [12.122.107.117]
8 27 ms 26 ms 25 ms cr1.wswdc.ip.att.net [12.122.4.54]
9 24 ms 23 ms 26 ms 12.122.135.165
10 28 ms 26 ms 25 ms 192.205.35.106
11 27 ms 23 ms 23 ms te0-2-0-2.ccr21.iad02.atlas.cogentco.com [154.54.31.181]
12 24 ms 26 ms 25 ms te0-3-0-5.ccr21.dca01.atlas.cogentco.com [154.54.2.49]
13 25 ms 27 ms 25 ms te4-2.mpd03.dca01.atlas.cogentco.com [154.54.40.62]
14 25 ms 26 ms 26 ms vl3901.na41.b003328-0.dca01.atlas.cogentco.com [66.28.65.218]
15 25 ms 26 ms 25 ms 38.104.30.102
16 26 ms 25 ms 26 ms 209.50.254.9.254.50.209.in-addr.arpa [209.50.254.9]
17 25 ms 26 ms 25 ms 209.50.254.25
18 72 ms * * sc-smv1160.servint.net [207.58.153.136]
19 * 50 ms * vps.theturboforums.com [207.58.161.157]
20 48 ms 37 ms 48 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

 

Site is UBAR slow right now for me

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 7 ms 7 ms L100.PRVDRI-VFTTP-32.verizon-gni.net [74.103.242.1]
3 7 ms 7 ms 7 ms G10-0-5-232.PRVDRI-LCR-02.verizon-gni.net [130.81.180.24]
4 10 ms 12 ms 12 ms P11-0-0.PRVDRI-LCR-01.verizon-gni.net [130.81.27.66]
5 11 ms 12 ms 12 ms so-3-3-0-0.NY5030-BB-RTR1.verizon-gni.net [130.81.29.28]
6 16 ms 17 ms 16 ms 0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]
7 16 ms 16 ms 17 ms 0.so-6-0-0.XL3.NYC4.ALTER.NET [152.63.16.221]
8 11 ms 12 ms 12 ms 0.xe-7-0-0.BR2.NYC4.ALTER.NET [152.63.3.166]
9 14 ms 14 ms 14 ms 204.255.168.90
10 14 ms 15 ms 14 ms cr1-tengig-0-8-3-0.NewYork.savvis.net [204.70.198.13]
11 25 ms 24 ms 25 ms cr1-tengig-0-15-0-0.Washington.savvis.net [204.70.196.101]
12 32 ms 22 ms 24 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]
13 22 ms 21 ms 22 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
14 24 ms 21 ms 22 ms corporate-executive-board.Washington.savvis.net[208.174.119.98]
15 26 ms 117 ms 21 ms sc-smv1160.servint.net [207.58.153.136]
16 22 ms 24 ms 22 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

 

response times are due to a large infrastructure being created to sensitize your web browsing by your government currently upgrading their software/hardware. i cant remember where i read this the other day, but seems conspiracy theory relevant. saying that they are going to start minimizing your ability to get a large amount of information that is not propaganda based "factual" information. just something i read the other day, cuz it happening on more then on site ive been on and it all seems to be slowing down.

 

#ad

 

Re: When the site is running slowly or non responsive please run a traceroute an

These are consecutive, from earlier today when the site was down. I have no idea what it means or if it's worth anything. All gibberish to me.


traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2338.985 ms 0.714 ms 0.906 ms
2 10.96.200.1 (10.96.200.1) 7.776 ms 9.435 ms 7.059 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 8.146 ms 7.650 ms 8.595 ms
4 70.169.76.229 (70.169.76.229) 8.841 ms 10.728 ms 19.780 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 32.581 ms 22.825 ms 24.118 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 22.904 ms 22.244 ms 22.714 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 85.579 ms 84.765 ms 84.318 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 84.049 ms 85.608 ms 85.715 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 85.028 ms 87.120 ms 86.660 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 85.073 ms 139.731 ms 87.870 ms
11 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 86.137 ms 86.440 ms 84.436 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 110.115 ms 252.526 ms 204.789 ms
13 209.50.254.25 (209.50.254.25) 110.201 ms
209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 189.762 ms 199.190 ms
14 sc-smv1160.servint.net (207.58.153.136) 81.040 ms 81.979 ms 79.856 ms
15 vps.theturboforums.com (207.58.161.157) 79.829 ms 79.207 ms 79.701 ms

traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.646 ms 0.497 ms 1.058 ms
2 10.96.200.1 (10.96.200.1) 6.460 ms 8.408 ms 7.034 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 6.264 ms 7.188 ms 6.476 ms
4 70.169.76.229 (70.169.76.229) 9.617 ms 8.775 ms 11.882 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 21.003 ms 27.669 ms 37.788 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 22.492 ms 22.765 ms 21.554 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 86.162 ms 85.982 ms 86.641 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 82.985 ms 90.934 ms 85.026 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 86.007 ms 84.592 ms 86.143 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.888 ms 87.560 ms 83.960 ms
11 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 79.151 ms 78.751 ms 80.074 ms
12 ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 79.274 ms 80.063 ms
209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 79.755 ms
13 209.50.254.25 (209.50.254.25) 90.556 ms 87.585 ms 88.281 ms
14 sc-smv1160.servint.net (207.58.153.136) 83.065 ms 83.577 ms
209.50.254.25 (209.50.254.25) 81.094 ms
15 vps.theturboforums.com (207.58.161.157) 80.781 ms
sc-smv1160.servint.net (207.58.153.136) 80.627 ms 80.237 ms

traceroute to theturboforums.com (207.58.161.157), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2.811 ms 1.981 ms 2.965 ms
2 10.96.200.1 (10.96.200.1) 6.801 ms 7.287 ms 7.938 ms
3 ip68-2-2-232.ph.ph.cox.net (68.2.2.232) 6.152 ms 7.523 ms 7.596 ms
4 70.169.76.229 (70.169.76.229) 11.238 ms 9.041 ms 8.172 ms
5 langbbrj02-as0.r2.la.cox.net (68.1.1.231) 19.933 ms 20.000 ms 29.415 ms
6 te-11-2-0.rar3.la-ca.us.xo.net (207.88.14.45) 21.050 ms 23.322 ms 22.037 ms
7 vb15.rar3.dallas-tx.us.xo.net (207.88.12.45) 94.353 ms 85.787 ms 88.353 ms
8 te-4-0-0.rar3.atlanta-ga.us.xo.net (207.88.12.1) 85.784 ms 86.315 ms 86.157 ms
9 te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 90.889 ms 86.762 ms 86.417 ms
10 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 84.604 ms 85.138 ms
te-11-0-0.rar3.washington-dc.us.xo.net (207.88.12.10) 84.023 ms
11 ae0d0.mcr1.washington-dc.us.xo.net (216.156.0.34) 83.027 ms
ip65-46-126-202.z126-46-65.customer.algx.net (65.46.126.202) 81.135 ms 81.016 ms
12 209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 79.720 ms 81.425 ms 98.900 ms
13 209.50.254.25 (209.50.254.25) 98.784 ms 88.631 ms
209.50.254.9.254.50.209.in-addr.arpa (209.50.254.9) 80.484 ms
14 209.50.254.25 (209.50.254.25) 97.415 ms 91.272 ms
sc-smv1160.servint.net (207.58.153.136) 80.414 ms
15 vps.theturboforums.com (207.58.161.157) 80.798 ms 80.992 ms 84.318 ms

 

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jill>tracert theturboforums.com

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.domain.actdsltmp [192.168.0.1]
2 41 ms 41 ms 40 ms spkn-dsl-gw04-196.spkn.qwest.net [207.225.41.196
]
3 41 ms 42 ms 41 ms spkn-agw1.inet.qwest.net [207.225.42.25]
4 42 ms 42 ms 42 ms spk-core-01.inet.qwest.net [205.171.153.69]
5 112 ms 112 ms 112 ms dcp-edge-01.inet.qwest.net [67.14.28.42]
6 112 ms 112 ms 115 ms 63.238.58.222
7 112 ms 112 ms 112 ms ae1-40g.ar2.iad1.us.nlayer.net [69.31.31.182]
8 112 ms 112 ms 112 ms as26821.xe-4-0-4.ar2.iad1.us.nlayer.net [69.31.1
0.74]
9 121 ms 117 ms 133 ms 208.131.235.14
10 114 ms 114 ms 113 ms sc-smv1160.servint.net [207.58.153.136]
11 180 ms 246 ms 223 ms 207.58.153.1.servint.net [207.58.153.1]
12 114 ms 113 ms 113 ms sc-smv1160.servint.net [207.58.153.136]
13 151 ms 224 ms 254 ms 207.58.153.1.servint.net [207.58.153.1]
14 114 ms 113 ms 114 ms sc-smv1160.servint.net [207.58.153.136]
15 131 ms 120 ms 136 ms 207.58.153.1.servint.net [207.58.153.1]
16 114 ms 113 ms 113 ms sc-smv1160.servint.net [207.58.153.136]
17 130 ms 118 ms 114 ms 207.58.153.1.servint.net [207.58.153.1]
18 115 ms 114 ms 113 ms sc-smv1160.servint.net [207.58.153.136]
19 126 ms 122 ms 119 ms 207.58.153.1.servint.net [207.58.153.1]
20 114 ms 114 ms 115 ms sc-smv1160.servint.net [207.58.153.136]
21 124 ms 125 ms 116 ms 207.58.153.1.servint.net [207.58.153.1]
22 114 ms 114 ms 114 ms sc-smv1160.servint.net [207.58.153.136]
23 127 ms 118 ms 121 ms 207.58.153.1.servint.net [207.58.153.1]
24 115 ms 114 ms 115 ms sc-smv1160.servint.net [207.58.153.136]
25 118 ms 117 ms 156 ms 207.58.153.1.servint.net [207.58.153.1]
26 114 ms 114 ms 115 ms sc-smv1160.servint.net [207.58.153.136]
27 124 ms 125 ms 134 ms 207.58.153.1.servint.net [207.58.153.1]
28 115 ms 114 ms 114 ms sc-smv1160.servint.net [207.58.153.136]
29 122 ms 115 ms 114 ms 207.58.153.1.servint.net [207.58.153.1]
30 115 ms 114 ms 115 ms sc-smv1160.servint.net [207.58.153.136]

Trace complete.

 

C:\Users\TylersGaming>tracert theturboforums.com

Tracing route to theturboforums.com [207.58.161.157]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 18 ms 10 ms 19 ms 67-197-192-1.ln.dyn.cm.comporium.net [67.197.192
.1]
3 9 ms 8 ms 21 ms 208-104-1-77.sta.comporium.net [208.104.1.77]
4 7 ms 11 ms 9 ms 208-104-1-113.sta.comporium.net [208.104.1.113]

5 7 ms 10 ms 7 ms 208-104-0-9.sta.comporium.net [208.104.0.9]
6 9 ms 7 ms 8 ms 208-104-0-185.sta.comporium.net [208.104.0.185]

7 10 ms 9 ms 17 ms te-4-3.car1.Charlotte1.Level3.net [4.71.124.73]

8 24 ms 17 ms 16 ms ae-4-4.ebr1.Atlanta2.Level3.net [4.69.132.162]
9 30 ms 49 ms 207 ms ae-28-52.car2.Atlanta4.Level3.net [4.68.103.45]
10 30 ms 17 ms 17 ms s265122-1.msr1-atx.savvis.net [208.173.177.137]

11 13 ms 21 ms 16 ms pr2-so-0-3-0.AtlantaPaix.savvis.net [204.70.200.
125]
12 14 ms 18 ms 15 ms cr2-te-0-0-0-0.atlanta.savvis.net [204.70.200.2]

13 28 ms 29 ms 29 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.7
0.196.102]
14 40 ms 33 ms 32 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
15 30 ms 35 ms 58 ms er1-gig-3-0-0.dck.savvis.net [204.70.203.2]
16 32 ms 30 ms 35 ms 64.242.15.186
17 30 ms 32 ms 38 ms 209.50.254.26
18 30 ms 37 ms 31 ms 209.50.254.10.254.50.209.in-addr.arpa [209.50.25
4.10]
19 35 ms 35 ms 31 ms sc-smv1160.servint.net [207.58.153.136]
20 43 ms 40 ms 39 ms vps.theturboforums.com [207.58.161.157]

Trace complete.

 

Hey any of you guys on the *nix try mtr instead.