As of late when i play at a 1.6 server i like i have been getting shitty ping. it used to be in the 40-50's but now its all the way up to the 140's!! I checked to see if anything was changed to the server and they said no. So i did a tracert... i have no idea what this info means so somebody please help/translate.

1 * * * Request timed out.
2 11 ms 11 ms 11 ms ge-2-2-ur01.plymouth.mi.mich.comcast.net [68.87
1.229]
3 14 ms 12 ms 13 ms srp-0-1-ar01.taylor.mi.mich.comcast.net [68.87.
.129]
4 14 ms 15 ms 14 ms 12.119.243.37
5 13 ms 14 ms 14 ms gbr1-p20.dtrmi.ip.att.net [12.123.139.30]
6 14 ms 14 ms 14 ms tbr1-p012501.dtrmi.ip.att.net [12.122.12.169]
7 29 ms 27 ms 27 ms 12.122.12.186
8 27 ms 28 ms 27 ms tbr2-cl2.sl9mo.ip.att.net [12.122.9.142]
9 45 ms 46 ms 42 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
10 40 ms 41 ms 42 ms ggr1-p370.dlstx.ip.att.net [12.123.16.245]
11 133 ms 128 ms 131 ms IPP-dllstx9lce1-pos5-0.wcg.net [64.200.232.201]

12 136 ms 131 ms 135 ms dllstx9lce1-yipes.wcg.net [64.200.226.118]
13 138 ms 138 ms 141 ms 66.7.164.90
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 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

trace complete.

I think what it means is that your connection is hopping through some really dodgy connections, probably beginning from #9 and getting worse until it falls apart at #14. I have no idea where those places are.

Does it only happen late at night? What I mean by this is that if you try during the day and your ping is fine but gets worse at night it probably means that local traffic through those hubs is too much for the system to handle well. If that is the case then you have to wait until your company sorts out a better route or find servers in locations closer to you so fewer hops are made. I had this problem for a couple of weeks and then it was fine again.

ill start to take notes... even though its hard cause i usually dont get home till 5:00-6:00... but ill see if i notice what you mentioned. Thanks.

ya what mr said

I second Soldat's comment..Mr is on target.

Back in the days when used to play on JCS I also had comcast. It was absolutely terrible and the service was spotty at best.

There were certain blocks of time that I knew I shouldn't even think about playing, due to high network saturation (I hated sharing my bandwidth.) I'd do trace routes and find that some of the hops would timeout just as you are experiencing above.

Unfortunately, there really insn't much you can do but call and complain. Record your trace routes because they might want to see them, so they can figure out which hops (routers) are carrying too much burden. In any case, I must have sent them a dozen or so logs and nothing was ever done.

I think it's something to do with comcast in general and how they handle adding new communities to the network. When I first got them, service wasn't so bad, but I think what happens is that they add new users without regard to the current infrastructure, causing problems for everyone else. I finally got fed up and switched to DSL.

Just wait it out. I'm sure they are aware of the issues, and over time they will get corrected.

ya what theeda said