JJMAN5
join:2004-06-23
Park Hills, MO | reply to apply17
Re: High pings at night for the past 2 months. apply17 - Well if I wanted to read 40 billion messages I would have read them. I did in fact read SEVERAL. So your comment on suffitiant knowledge is lame and uncalled for. You could have stated your comment without the first sentence all together. Try to help instead of adding flames to somethen that is upsetting as this whole ping issue is.
eshiku - Its weird because some nights it will play ok. During the week mostly. Close to the weekend or the weekend itself is when it takes a dive. I would hate to hit up on dsl again as I serisoulsy HATE there support they have. Its more terrible than charter if you can believe that. 
Barney
JJMAN
www.JJMAN.org |
|
JJMAN5
join:2004-06-23
Park Hills, MO | Everynight I ping out of quake servers. Everynight now. Does Charter have to many people on one connection and when they all get online it eleminates online gameing when I can actualy play. Has anyeone else got this issue even close to me? St Louis is about 75 miles North of me and Im sure they have to be effected also. Just wondered if anyone else gets these issues at nighttime.
JJMAN
www.JJMAN.org
admin@jjman.org |
|
| Yeah I hear ya. I too have been having issues for a few weeks (2-3)now. I haven't said anything because it usually clears up in a couple of days. It does really start to grate on ya. I will most likely call support, but I don't want to make an appointment to have them come out or go through the remove router, reboot, etc. I can see where the problem is from my tracerts. Here is my trace to my game server.
Tracing route to 69.13.39.83 over a maximum of 30 hops
1 tracert 69.13.39.83
Tracing route to 69.13.39.83 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 6 ms 7 ms 10.202.224.1
3 177 ms 188 ms 185 ms 68-112-12-220.dhcp.stls.mo.charter.com [68.112.1
2.220]
4 200 ms 190 ms 213 ms 24-217-5-126.dhcp.stls.mo.charter.com [24.217.5.
126]
5 215 ms 226 ms 233 ms 24-217-4-14.dhcp.stls.mo.charter.com [24.217.4.1
4]
6 281 ms 291 ms 307 ms so-1-2-0.gar2.chi1.bbnplanet.net [4.79.74.1]
7 271 ms 283 ms 296 ms ge-6-0-0-51.edge1.Chicago1.Level3.net [4.68.101.
13]
8 261 ms 281 ms 295 ms he-level3-oc12.Chicago1.Level3.net [4.68.127.66]
9 304 ms 276 ms 256 ms pos1-0.gsr12012.sjc.he.net [64.62.227.53]
10 288 ms 284 ms 288 ms pos8-0.gsr12416.sjc2.he.net [64.62.133.18]
11 317 ms 334 ms 346 ms pos2-3.gsr12416.pao.he.net [66.220.13.42]
12 317 ms 312 ms 284 ms pos3-0.gsr12012.lax.he.net [65.19.129.2]
13 279 ms 290 ms * pos4-0.gsr12012.dal.he.net [66.160.184.6]
14 234 ms 194 ms 216 ms 216.218.217.182
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
|
|
| And here is to something as simple as charter.net:
Tracing route to charter.net [64.192.190.12]
over a maximum of 30 hops:
1 tracert 69.13.39.83
Tracing route to 69.13.39.83 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 6 ms 7 ms 10.202.224.1
3 177 ms 188 ms 185 ms 68-112-12-220.dhcp.stls.mo.charter.com [68.112.1
2.220]
4 200 ms 190 ms 213 ms 24-217-5-126.dhcp.stls.mo.charter.com [24.217.5.
126]
5 215 ms 226 ms 233 ms 24-217-4-14.dhcp.stls.mo.charter.com [24.217.4.1
4]
6 281 ms 291 ms 307 ms so-1-2-0.gar2.chi1.bbnplanet.net [4.79.74.1]
7 271 ms 283 ms 296 ms ge-6-0-0-51.edge1.Chicago1.Level3.net [4.68.101.
13]
8 261 ms 281 ms 295 ms he-level3-oc12.Chicago1.Level3.net [4.68.127.66]
9 304 ms 276 ms 256 ms pos1-0.gsr12012.sjc.he.net [64.62.227.53]
10 288 ms 284 ms 288 ms pos8-0.gsr12416.sjc2.he.net [64.62.133.18]
11 317 ms 334 ms 346 ms pos2-3.gsr12416.pao.he.net [66.220.13.42]
12 317 ms 312 ms 284 ms pos3-0.gsr12012.lax.he.net [65.19.129.2]
13 279 ms 290 ms * pos4-0.gsr12012.dal.he.net [66.160.184.6]
14 234 ms 194 ms 216 ms 216.218.217.182
15 * * * Request timed out.
16 * * * Request timed out.
|
|
