Can anyone trouble shoot these tracerts fror me? [Archive] - SpeedGuide.net Broadband Community

View Full Version : Can anyone trouble shoot these tracerts fror me?


Druss
02-04-01, 10:47 AM
Ok, here they are. I am trying to get to uswest.battle.net. It gets really slow around hop 13 and 14. I tried it again recently and I got some stars in the beginning mostly. SO i did a few of those tracerts and I also did 3 excite and 3 speedguid tracerts with rather disturbing results, lots of stars. Any suggestions on decreasing my ping for battle.net? Or comments on what stars and such mean. Im clueless. I never did a tracert before last week.

Tracing route to uswest.battle.net [63.241.83.8]
over a maximum of 30 hops:

1 23 ms 14 ms 12 ms 10.81.236.1
2 11 ms 11 ms 12 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 12 ms 12 ms 23 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 13 ms 14 ms 15 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 17 ms 22 ms 19 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 22 ms 22 ms 23 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 25 ms 24 ms 25 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 25 ms 25 ms 25 ms home-gw.attga.ip.att.net [192.205.32.229]
9 26 ms 25 ms 26 ms gbr4-p50.attga.ip.att.net [12.123.20.254]
10 40 ms 40 ms 39 ms gbr4-p80.wswdc.ip.att.net [12.122.2.178]
11 39 ms 41 ms 39 ms gbr3-p60.wswdc.ip.att.net [12.122.1.129]
12 44 ms 45 ms 46 ms gbr3-p40.sl9mo.ip.att.net [12.122.2.82]
13 83 ms 82 ms 82 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
14 87 ms 82 ms 82 ms 12.122.255.222
15 84 ms 84 ms 99 ms 216.148.209.18
16 84 ms 85 ms 85 ms 216.148.209.14
17 82 ms 94 ms 84 ms uswest.battle.net [63.241.83.8]

Trace complete.

Tracing route to uswest.battle.net [63.241.83.7]
over a maximum of 30 hops:

1 25 ms 11 ms 10 ms 10.81.236.1
2 12 ms 11 ms 11 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 12 ms 12 ms 13 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 14 ms 18 ms 15 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 16 ms 18 ms 18 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 23 ms 23 ms 38 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 24 ms 25 ms 24 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 25 ms 27 ms 24 ms home-gw.attga.ip.att.net [192.205.32.229]
9 26 ms 25 ms 24 ms gbr4-p50.attga.ip.att.net [12.123.20.254]
10 43 ms 41 ms 40 ms gbr4-p80.wswdc.ip.att.net [12.122.2.178]
11 41 ms 39 ms 40 ms gbr3-p60.wswdc.ip.att.net [12.122.1.129]
12 47 ms 44 ms 46 ms gbr3-p80.sl9mo.ip.att.net [12.122.2.145]
13 82 ms 81 ms 86 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
14 83 ms 82 ms 82 ms 12.122.255.222
15 84 ms 85 ms 86 ms 216.148.209.18
16 168 ms 84 ms 83 ms 216.148.209.14
17 84 ms 83 ms 83 ms uswest.battle.net [63.241.83.7]

Trace complete.

Tracing route to uswest.battle.net [63.241.83.7]
over a maximum of 30 hops:

1 12 ms 11 ms 11 ms 10.81.236.1
2 11 ms 12 ms 12 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 11 ms 12 ms 11 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 13 ms 14 ms 13 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 17 ms 17 ms 18 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 24 ms 23 ms 70 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 26 ms 26 ms 25 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 25 ms 27 ms 24 ms home-gw.attga.ip.att.net [192.205.32.229]
9 24 ms 25 ms 25 ms gbr4-p50.attga.ip.att.net [12.123.20.254]
10 40 ms 40 ms 39 ms gbr4-p80.wswdc.ip.att.net [12.122.2.178]
11 40 ms 42 ms 39 ms gbr3-p60.wswdc.ip.att.net [12.122.1.129]
12 * 46 ms * gbr3-p80.sl9mo.ip.att.net [12.122.2.145]
13 85 ms 82 ms 83 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
14 85 ms 82 ms 81 ms 12.122.255.222
15 * 85 ms 83 ms 216.148.209.18
16 87 ms 84 ms 84 ms 216.148.209.14
17 82 ms 83 ms 85 ms uswest.battle.net [63.241.83.7]

Trace complete.

Tracing route to uswest.battle.net [63.241.83.8]
over a maximum of 30 hops:

1 11 ms 14 ms 11 ms 10.81.236.1
2 12 ms 12 ms 11 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 11 ms 12 ms 11 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 * 62 ms 15 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 18 ms 17 ms 22 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 23 ms 25 ms 21 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 * * * Request timed out.
8 26 ms 24 ms 27 ms home-gw.attga.ip.att.net [192.205.32.229]
9 26 ms 27 ms 24 ms gbr4-p50.attga.ip.att.net [12.123.20.254]
10 124 ms 39 ms 39 ms gbr4-p80.wswdc.ip.att.net [12.122.2.178]
11 41 ms 39 ms 41 ms gbr3-p60.wswdc.ip.att.net [12.122.1.129]
12 45 ms 45 ms 46 ms gbr3-p40.sl9mo.ip.att.net [12.122.2.82]
13 85 ms * 82 ms gbr3-p20.sffca.ip.att.net [12.122.2.74]
14 84 ms 82 ms 82 ms 12.122.255.222
15 84 ms 84 ms 83 ms 216.148.209.18
16 * 157 ms 106 ms 216.148.209.14
17 85 ms 85 ms 84 ms uswest.battle.net [63.241.83.8]

Trace complete.

Tracing route to www.excite.com (http://www.excite.com) [199.172.146.99]
over a maximum of 30 hops:

1 14 ms 11 ms 11 ms 10.81.236.1
2 12 ms 12 ms 11 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 12 ms 17 ms 12 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 19 ms 19 ms 19 ms c1-pos9-0.clevoh1.home.net [24.7.65.246]
5 30 ms 29 ms 29 ms c1-pos3-0.chcgil1.home.net [24.7.64.173]
6 47 ms 45 ms 47 ms c1-pos7-0.lnmtco1.home.net [24.7.65.150]
7 70 ms 70 ms 70 ms c1-pos3-0.snjsca1.home.net [24.7.65.141]
8 68 ms 70 ms 69 ms bb1-pos1-0.rwc1.sfba.home.net [24.7.74.118]
9 * * * Request timed out.
10 * * * Request timed out.
11 bfr-ge0-0.excite.com [24.7.70.34] reports: Destination net unreachable.

Trace complete.

Tracing route to www.excite.com (http://www.excite.com) [199.172.146.99]
over a maximum of 30 hops:

1 10 ms 10 ms 12 ms 10.81.236.1
2 * 11 ms 11 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 13 ms 12 ms 11 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 20 ms 21 ms 22 ms c1-pos9-0.clevoh1.home.net [24.7.65.246]
5 28 ms 30 ms 29 ms c1-pos3-0.chcgil1.home.net [24.7.64.173]
6 45 ms 45 ms 46 ms c1-pos7-0.lnmtco1.home.net [24.7.65.150]
7 67 ms 68 ms 68 ms c1-pos3-0.snjsca1.home.net [24.7.65.141]
8 71 ms 69 ms 71 ms bb1-pos1-0.rwc1.sfba.home.net [24.7.74.118]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * bfr-ge0-0.excite.com [24.7.70.34] reports: Destination n
et unreachable.

Trace complete.

2 12 ms 12 ms 12 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 12 ms 11 ms 11 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 19 ms 20 ms 19 ms c1-pos9-0.clevoh1.home.net [24.7.65.246]
5 29 ms 29 ms 30 ms c1-pos3-0.chcgil1.home.net [24.7.64.173]
6 45 ms 46 ms 47 ms c1-pos7-0.lnmtco1.home.net [24.7.65.150]
7 67 ms 68 ms 67 ms c1-pos3-0.snjsca1.home.net [24.7.65.141]
8 68 ms 68 ms 69 ms bb1-pos1-0.rwc1.sfba.home.net [24.7.74.118]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * bfr-ge0-0.excite.com [24.7.70.34] reports: Destination n
et unreachable.

Trace complete.

Tracing route to www.speedguide.net (http://www.speedguide.net) [216.167.23.73]
over a maximum of 30 hops:

1 10 ms 12 ms 11 ms 10.81.236.1
2 * * * Request timed out.
3 * 12 ms 12 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 14 ms 14 ms 14 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 * 18 ms 18 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 * 23 ms 23 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 * * 25 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 47 ms 48 ms 48 ms 24.7.70.38
9 48 ms 47 ms 48 ms atl-core-03.inet.qwest.net [205.171.21.105]
10 47 ms 49 ms 47 ms wdc-core-03.inet.qwest.net [205.171.5.241]
11 46 ms 47 ms 49 ms wdc-edge-06.inet.qwest.net [205.171.24.126]
12 39 ms 37 ms 37 ms 208.46.126.122
13 39 ms 37 ms 38 ms ge0031.ed2.wdc.dn.net [216.167.88.124]
14 39 ms 38 ms 39 ms www.speedguide.net (http://www.speedguide.net) [216.167.23.73]

Trace complete.


C:\WINDOWS>tracert www.speedguide.net (http://www.speedguide.net)

Tracing route to www.speedguide.net (http://www.speedguide.net) [216.167.23.73]
over a maximum of 30 hops:

1 11 ms 10 ms 10 ms 10.81.236.1
2 12 ms 11 ms 13 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 13 ms 12 ms 13 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 14 ms 14 ms 16 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 19 ms 18 ms 16 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 23 ms 23 ms 22 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 25 ms 24 ms 27 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 48 ms 47 ms 49 ms 24.7.70.38
9 48 ms 48 ms 50 ms atl-core-03.inet.qwest.net [205.171.21.105]
10 47 ms 48 ms 47 ms wdc-core-03.inet.qwest.net [205.171.5.241]
11 49 ms 58 ms 48 ms wdc-edge-06.inet.qwest.net [205.171.24.126]
12 37 ms 38 ms 38 ms 208.46.126.122
13 * 37 ms 38 ms ge0031.ed2.wdc.dn.net [216.167.88.124]
14 44 ms 38 ms 41 ms www.speedguide.net (http://www.speedguide.net) [216.167.23.73]

Trace complete.

C:\WINDOWS>tracert www.speedguide.net (http://www.speedguide.net)

Tracing route to www.speedguide.net (http://www.speedguide.net) [216.167.23.73]
over a maximum of 30 hops:

1 11 ms 11 ms 13 ms 10.81.236.1
2 12 ms 12 ms 12 ms bb1-fe1-0-100bt.indnpls1.in.home.net [24.8.89.1]

3 12 ms 12 ms 12 ms c1-pos5-1.iplsin1.home.net [24.7.73.29]
4 14 ms 14 ms 14 ms c1-pos2-0.lsvlky1.home.net [24.7.69.10]
5 17 ms 18 ms 18 ms c1-pos2-0.nsvltn1.home.net [24.7.64.226]
6 21 ms 22 ms 64 ms c1-pos4-0.brhmal1.home.net [24.7.64.230]
7 25 ms 25 ms 24 ms c1-pos1-0.atlnga1.home.net [24.7.64.242]
8 47 ms 47 ms 45 ms 24.7.70.38
9 49 ms 47 ms 49 ms atl-core-03.inet.qwest.net [205.171.21.105]
10 65 ms 45 ms 50 ms wdc-core-03.inet.qwest.net [205.171.5.241]
11 48 ms 48 ms 52 ms wdc-edge-06.inet.qwest.net [205.171.24.126]
12 40 ms 37 ms 40 ms 208.46.126.122
13 40 ms 38 ms 39 ms ge0031.ed2.wdc.dn.net [216.167.88.124]
14 * 38 ms 38 ms www.speedguide.net (http://www.speedguide.net) [216.167.23.73]

Trace complete.

Kip Patterson
02-04-01, 11:39 AM
The asterisks indicate packets that were lost or not replied to by the destination router.
If all three packets have an asterisk, that normally indicates a router that is configured to not respond to pings. In your 8th traceroute, however, the 2nd router is known to reply to pings from your earlier traces, so it must have been overloaded at that point.

Your route to uswest.battle.net is exceptionally fast. Of the round trip time, 63 milliseconds is due to the length of the path. Granted, the routing is pretty bad but there is nothing you can do about it. Your ISP doesn't have many more options, either.