Ping rate shot through the roof why?

[[UDF2.1]Darkman]

Today the 05/09/2000 my ping rate on wireplay open play has gone from 130 to 350 whats going on, I cannot play counter-strike with a ping rate of 350, so why, what have you changed, because it's making the game unplayable.

[Champ]

hi,

could u post a few more details for us:

which isp u r using, which game(s) u r playing and on what servers, and the time u tend to play on them.

then we can have a look at possible causes for these ping problems u r having.

champ :)

[[UDF2.1]Darkman]

Below is a trecert to one of your severs, can't remember which, it only started yesturday.
I'm with telewest, Blueyonder isp, I know there upgrading, but untill yesturday there has been no problems, the times I go online to play counter-strike is from 7pm till 6am









C:\>tracert 212.127.20.30

Tracing route to 212.127.20.30 over a maximum of 30 hops

1 87 ms 83 ms 82 ms 213.48.135.7
2 89 ms 83 ms 82 ms rtr1-pre.cableinet.net [213.48.135.2]
3 89 ms 81 ms 84 ms 194.117.132.21
4 105 ms 99 ms 97 ms h111-uk-gw3.cableinet.net [193.38.108.81]
5 103 ms 98 ms 100 ms 194.117.150.14
6 108 ms 98 ms 98 ms 212.4.203.197
7 417 ms 452 ms 437 ms core3-s8-0-1.uk1.concert.net [195.99.64.137]
8 277 ms 287 ms 235 ms t2c1-p2-2.uk-lon2.concert.net
[166.49.163.65]
9 277 ms 118 ms 116 ms t2a1-ge8-0-0.uk-lon2.concert.net
[166.49.176.49

10 344 ms 439 ms 400 ms 166.49.156.158
11 257 ms 205 ms 207 ms 212.127.20.30

Trace complete.

C:\>tracert 212.127.20.30

Tracing route to 212.127.20.30 over a maximum of 30 hops

1 86 ms 79 ms 80 ms 213.48.135.7
2 84 ms 78 ms 80 ms rtr1-pre.cableinet.net [213.48.135.2]
3 82 ms 79 ms 79 ms 194.117.132.21
4 115 ms 94 ms 98 ms h111-uk-gw3.cableinet.net [193.38.108.81]
5 212 ms 508 ms 282 ms 194.117.150.14
6 115 ms 106 ms 109 ms 212.4.203.197
7 279 ms 331 ms 261 ms core3-s8-0-1.uk1.concert.net [195.99.64.137]
8 314 ms 348 ms 333 ms t2c1-p2-2.uk-lon2.concert.net
[166.49.163.65]
9 146 ms 143 ms 141 ms t2a1-ge8-0-0.uk-lon2.concert.net
[166.49.176.

10 336 ms 334 ms 323 ms 166.49.156.158
11 354 ms 460 ms 455 ms 212.127.20.30

Trace complete.

[[UDF2.1]Darkman]

This was a tracert at 2:45 today to server 21 for counter-strike, isp Blueyonder.C:\>tracert 212.127.20.27

Tracing route to 212.127.20.27 over a maximum of 30 hops

1 95 ms 82 ms 78 ms 213.48.135.7
2 86 ms 86 ms 81 ms rtr1-pre.cableinet.net [213.48.135.2]
3 95 ms 83 ms 82 ms 194.117.132.21
4 336 ms 262 ms 311 ms h111-uk-gw3.cableinet.net [193.38.108.81]
5 123 ms 120 ms 123 ms 194.117.150.14
6 126 ms 118 ms 116 ms fastethernet0-0.lth-icr-02.carrier1.net [212.4
03.197]
7 261 ms 285 ms 269 ms core3-s8-0-1.uk1.concert.net [195.99.64.137]
8 203 ms 188 ms 181 ms t2c1-p2-2.uk-lon2.concert.net [166.49.163.65]
9 * 264 ms * t2a1-ge8-0-0.uk-lon2.concert.net [166.49.176.4

10 336 ms 298 ms 273 ms 166.49.156.158
11 263 ms 254 ms 220 ms 212.127.20.27

Trace complete.

[-=Apex=-]

I think you might find that telewest are having routing problems at the moe which might explain it :)

[Champ]

cheers for the trace routes.

your not the only one i've seen with bad pings once it hits the concert from blueyonder unfortunately.

all i can suggest atm is to use the servers which aren't on the concert feed. not all the servers have been transferred over, because of the problems some people on certain isp's are having. try using servers that begin 212.140 on their ip addresses.


champ :)

[[UDF2.1]Darkman]

Thanks for the help.......