Tracert issues?

[Kryptonical]

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

[Batlin]

Not sure what you can do.

I'm playing from Europe and my ping almost equals yours. Average 102ms.

Code: Select all

  1    <1 ms    <1 ms    <1 ms  my.router [192.168.168.254]
  2     8 ms     7 ms     7 ms  gateway.dyn1.xxx.schedom-europe.net [83.101.1.1]
  3    11 ms    11 ms    11 ms  atm-11-32.largo-matisse.bru.schedom-europe.net [83.101.0.34]
  4    11 ms    13 ms    13 ms  unknown.hwng.net [209.197.1.245]
  5    20 ms    20 ms    46 ms  1-2.r1.pa.hwng.net [69.16.190.85]
  6    30 ms    28 ms    28 ms  1-1.r3.lo.hwng.net [209.197.1.182]
  7    29 ms    28 ms    28 ms  3-1.r1.lo.hwng.net [209.197.1.193]
  8    96 ms    95 ms    96 ms  1-2.r1.pa.hwng.net [69.16.191.49]
  9   109 ms    95 ms    95 ms  xe-1-0-0.paix.nyc-telx-dis-1.peer1.net [198.32.118.146]
 10   101 ms   101 ms   101 ms  10ge.ten1-2.wdc-sp2-cor-2.peer1.net [216.187.115.222]
 11   109 ms   110 ms   110 ms  216.187.120.253
 12   109 ms   109 ms   110 ms  216.187.120.238
 13   103 ms   101 ms   102 ms  1-2.r1.pa.hwng.net [64.34.176.148]

[Kryptonical]

yea that seems off. and I'm playing from the outskirts of seattle, I know some one who played from downtown seattle (who had more hops than I) and got 40-70 ping.

[Dagon]

bad excuse and not really worth much, but you must just have a whole set of bad hardware between you and the backbone.. all the rain drowning your cable lines!

Code: Select all

   1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     6 ms     7 ms     8 ms  10.242.108.1
  3     8 ms     7 ms     9 ms  96-34-84-34.static.unas.ma.charter.com [96.34.84.34]
  4     8 ms     7 ms     9 ms  96-34-80-22.static.unas.ma.charter.com [96.34.80.22]
  5     7 ms     9 ms     8 ms  96-34-80-16.static.unas.ma.charter.com [96.34.80.16]
  6    10 ms     8 ms    12 ms  bbr01oxfrma-tge-0-0-0-0.oxfr.ma.charter.com [96.34.2.12]
  7    14 ms    13 ms    14 ms  xe-4-3-0.edge2.NewYork1.Level3.net [4.71.230.69]
  8    13 ms    17 ms    17 ms  vlan79.csw2.NewYork1.Level3.net [4.68.16.126]
  9    14 ms    13 ms    13 ms  ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69]
 10    19 ms    30 ms    18 ms  ae-3-3.ebr4.Washington1.Level3.net [4.69.132.93]
 11    25 ms    19 ms    19 ms  ae-74-74.csw2.Washington1.Level3.net [4.69.134.182]
 12    20 ms    20 ms    18 ms  ae-2-79.edge2.Washington3.Level3.net [4.68.17.76]
 13    21 ms    23 ms    25 ms  PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16    23 ms    26 ms    23 ms  uosecondage.com [64.34.176.148]

Code: Select all

Pinging uosecondage.com [64.34.176.148] with 32 bytes of data:
Reply from 64.34.176.148: bytes=32 time=25ms TTL=113
Reply from 64.34.176.148: bytes=32 time=32ms TTL=113
Reply from 64.34.176.148: bytes=32 time=25ms TTL=113
Reply from 64.34.176.148: bytes=32 time=23ms TTL=113

Ping statistics for 64.34.176.148:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 32ms, Average = 26ms

[Chaos]

Well yes there is not much you can do to change how you get routed to the server other then change isp's . Not sure it will help but at least some good info .

go to http://whatismyipaddress.com/

it has a very simple trace ip feature were you can up in an ip address say the ones that you are having problems with .. find out who owns them and at least call them .. though if they are like my isp .. they hardly care about their customers much less someone who hops though their network.

I really hope this helps ..