Tracert issues?
Posted: Sat Mar 06, 2010 2:40 pm
my ping is avg around 100-150. I'm not complaining about my ping because its playable, but I know it could be better as I have a neighbor (not next to me but in the Seattle area) who has played here on uosa and has gotten about 50-70.
I did a tracert:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms ge-3-28-ur01.bellevue.wa.seattle.comcast.net [68.86.113.49]
4 8 ms 8 ms 7 ms po-10-ur02.bellevue.wa.seattle.comcast.net [68.85.240.78]
5 11 ms 9 ms 14 ms be-50-ar01.seattle.wa.seattle.comcast.net [68.85.240.65]
6 10 ms 9 ms 9 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.209]
7 12 ms 10 ms 11 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
8 13 ms 17 ms 17 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]
9 22 ms 11 ms 13 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]
10 42 ms 53 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 65 ms 67 ms 61 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 62 ms 61 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
13 93 ms 95 ms 104 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
14 105 ms 93 ms 117 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
15 97 ms 96 ms 93 ms ae-3-89.edge2.Washington3.Level3.net [4.68.17.140]
16 94 ms 95 ms 98 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 97 ms 97 ms 95 ms uosecondage.com [64.34.176.148]
Trace complete.
After seeing this I contact comcast and asked what they could do, they put in a ticket and reset my modem, disable my router (directly plugged into modem now) and had me do a new tracert
new tracert after reset:
1 * * * Request timed out.
2 10 ms 8 ms 7 ms ge-3-28-ur01.bellevue.wa.seattle.comcast.net [68.86.113.49]
3 10 ms 10 ms 7 ms po-10-ur02.bellevue.wa.seattle.comcast.net [68.85.240.78]
4 12 ms 9 ms 11 ms be-50-ar01.seattle.wa.seattle.comcast.net [68.85.240.65]
5 12 ms 10 ms 13 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.209]
6 27 ms 10 ms 12 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
7 19 ms 17 ms 17 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]
8 13 ms 17 ms 18 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]
9 47 ms 52 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
10 62 ms 62 ms 63 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
11 64 ms 66 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
12 96 ms 96 ms 95 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
13 98 ms 92 ms 105 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
14 93 ms 95 ms 94 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.204]
15 95 ms 95 ms 94 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
16 * * * Request timed out.
17 * * * Request timed out.
18 97 ms 99 ms 99 ms uosecondage.com [64.34.176.148]
Trace complete.
After reviewing this I noticed in the original my 17 and 18 hop points timed out, in the newer tracert my 16 and 17 hop points timed out. On my first tracert I had 19 hops, and my second I had 18. Both timed out hops were the 2 prior to meeting uosecondage.com
any thoughts where things are going wrong / how I could improve?
thank you
I did a tracert:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 * * * Request timed out.
3 8 ms 7 ms 8 ms ge-3-28-ur01.bellevue.wa.seattle.comcast.net [68.86.113.49]
4 8 ms 8 ms 7 ms po-10-ur02.bellevue.wa.seattle.comcast.net [68.85.240.78]
5 11 ms 9 ms 14 ms be-50-ar01.seattle.wa.seattle.comcast.net [68.85.240.65]
6 10 ms 9 ms 9 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.209]
7 12 ms 10 ms 11 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
8 13 ms 17 ms 17 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]
9 22 ms 11 ms 13 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]
10 42 ms 53 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
11 65 ms 67 ms 61 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 62 ms 61 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
13 93 ms 95 ms 104 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
14 105 ms 93 ms 117 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
15 97 ms 96 ms 93 ms ae-3-89.edge2.Washington3.Level3.net [4.68.17.140]
16 94 ms 95 ms 98 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
17 * * * Request timed out.
18 * * * Request timed out.
19 97 ms 97 ms 95 ms uosecondage.com [64.34.176.148]
Trace complete.
After seeing this I contact comcast and asked what they could do, they put in a ticket and reset my modem, disable my router (directly plugged into modem now) and had me do a new tracert
new tracert after reset:
1 * * * Request timed out.
2 10 ms 8 ms 7 ms ge-3-28-ur01.bellevue.wa.seattle.comcast.net [68.86.113.49]
3 10 ms 10 ms 7 ms po-10-ur02.bellevue.wa.seattle.comcast.net [68.85.240.78]
4 12 ms 9 ms 11 ms be-50-ar01.seattle.wa.seattle.comcast.net [68.85.240.65]
5 12 ms 10 ms 13 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.209]
6 27 ms 10 ms 12 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
7 19 ms 17 ms 17 ms ae-31-51.ebr1.Seattle1.Level3.net [4.68.105.30]
8 13 ms 17 ms 18 ms ae-1-100.ebr2.Seattle1.Level3.net [4.69.132.18]
9 47 ms 52 ms 53 ms ae-2-2.ebr2.Denver1.Level3.net [4.69.132.54]
10 62 ms 62 ms 63 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
11 64 ms 66 ms 63 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
12 96 ms 96 ms 95 ms ae-2-2.ebr2.Washington1.Level3.net [4.69.132.70]
13 98 ms 92 ms 105 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
14 93 ms 95 ms 94 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.204]
15 95 ms 95 ms 94 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
16 * * * Request timed out.
17 * * * Request timed out.
18 97 ms 99 ms 99 ms uosecondage.com [64.34.176.148]
Trace complete.
After reviewing this I noticed in the original my 17 and 18 hop points timed out, in the newer tracert my 16 and 17 hop points timed out. On my first tracert I had 19 hops, and my second I had 18. Both timed out hops were the 2 prior to meeting uosecondage.com
any thoughts where things are going wrong / how I could improve?
thank you