significant ping/latency increase????

[Kanibal]

lo

since last week i have been suffering the most terribly high pings on wireplay. as u can imagine, this has had me pulling my hair out.

i have read Darkman's posts below, and my problems are identical. when running tracert, everything is fine until i hit the concert router. i can provide copies if required, but they are very similar to Darkman's.

so...what is the latest developement, are we going to see some kind of improvement?

cos at the moment i cannot play tfc on wireplay, i read that we can use an alternative server not routed through concert. but unfortunately, all 3 open tfc(tf1.5) servers are routed through there. meaning i can't play on wireplay. :mad:

i am at the end of my tether, what am i 2 do.

any help to get things back to a decent standard, which can only be expected of the "UK's biggest and best gaming servers/community", would be greatly appreciated.

thank you for your time!

[metatron]

there has been a problem on wireplay with the concert netfeed. as far as i know we are currently moving servers around to ease the bottlenecks.... I will ask around to find out when this will be completed and get abck to you...


:)

[[BROUZE]Plague]

concert isnt that the newwww net feed thats supposed to help with the ping /lag prob until new feed went live yesterday and my favorit sof servers were moved i got a ping at around 180 this is tracert performed tonight
C:\WINDOWS\Desktop>tracert 212.162.240.63

Tracing route to 212.162.240.63 over a maximum of 30 hops

1 83 ms 80 ms 80 ms Lv2d2.cableinet.net [213.48.145.5]
2 85 ms 78 ms 81 ms rtr137-kno.cableinet.net [213.48.137.2]
3 79 ms 80 ms 83 ms 194.117.132.21
4 126 ms 123 ms 127 ms h111-uk-gw3.cableinet.net [193.38.108.81]
5 120 ms 142 ms 121 ms 194.117.150.14
6 128 ms * * fastethernet0-0.lth-icr-02.carrier1.net [212.4.2
03.197]
7 674 ms 657 ms 540 ms core3-s8-0-1.uk1.concert.net [195.99.64.137]
8 * * * Request timed out.
9 * * * Request timed out.
10 * 738 ms * 166.49.218.130
11 * * 697 ms 212.162.240.63
surely this is not an improvment

[metatron]

we've split all the servers across 2 netfeeds, so those who can benefit from the new concert one can use that and those on ntl, virgin and i think red hot ant who's isp's are having problems when connecting to concert can use the servers connected to the old netfeed which now should be a bit smoother with less traffic. the best thing to doo is try them all. check all the ip addresses and do tracert (cant do that myself cos we've got a firewall that messes it all up) you'll find some that are on the old netfeed which should be good as gold.

this is just a temparary messure though so the guys are still sorting a more permament solution

top jolly

:)

[[BROUZE]Plague]

how do i do that when both dm servers have moved

[Kanibal]

thx for the swift reply, METATRON.
but unfortunately as i stated previously, all 3 openplay servers for TF1.5 have been put onto the new net feed. that leaves me no option but to get a game somewhere else (something i don't wanna do). unless i invade somebody's clan match/practice cos the clan servers have not been switched yet. :wink:
if u get any more info, i'll be interested to hear it.

thx again :E

[Custodian]

Unfortunately the peering agreements between your ISPs and Concert are not set by gameplay, so we have no control on how connections are made. Having said that, we are concerned that the new feed gives improvement to the majority of our customers, even accepting that it might not help everyone. I am keen to put presure on the company to ask Concert for improvements where these poor links are hightlighted, and yuo can put the same pressure on your ISP to sort things their end.

Please let us know which ISP and service you are using as well, and we will see what we can do.

[Kanibal]

ok, i'm on telewest/blueyonder ISP using their SurfUnlimited service on a 56K modem.
i have been onto telewest and as far as they are concerned it is the router at concert which is causing the problem, and looking at the tracert, i gotta agree with that.
also, my ISP is functioning very well to all other gaming networks, including your own, except the servers using the concert router.
maybe there is a problem between telewest and concert but unfortunately that still doesn't help me to get a game on wireplay :(
and with more and more people signing up with none bt-backbone ISP's, i can't see this being a problem which is gonna just disappear.

[Kanibal]

latest situation,
i have finally discussed this with some1 at telewest with more than 2 brain cells to rub together :E
looks like its a problem at their end :emb:
thx again for your help.
maybe you should add telewest to the list of ISP's having trouble (RHA,NTL Virgin,etc).

cheers,
Kanibal

[Custodian]

Thanks for that feedback Kanibal.
I hope they sort it out soon for you (and the rest of the telewest users).

[Toffee]

Ok im glad wireplay are aware of the situation. But one thing I have to point out is that it is not the customers responsability for your servers to work properly. It is not our fault your servers run badly with some ISP's. So as far as Im concerned it's wireplays responsability to sort this mess up, and I hope they do it soon cos Im sick (no offence) of all these **** ups being made.

[T 1 0 0 0]

i have a similar problem, as soon as i connect to a HL, TFC, CS game (is when is say connection accepted 213.34.4343.434...) , my modem hags up. I have posted this on HELP ME PLEEEESSEE!!!!1 but ideas seem to have dried up, plz can anyone help :)

[Custodian]

Toffee,
Our servers are working fine, and the connection to most ISPs is fine also. There are just a few ISPs that seem to have trouble routing traffic to Concert. If you have read all the threads in all the forums about the Concert feed you would have seen the ones where other customers have had confirmation from their ISP that they do have a problem. That is why I have been suggesting that anyone suffering from this does some chasing their end.

Having said that, it does not mean we are doing nothing. We are pointing out the problem to Concert, the supplier at our end. As peering arrangents are done by agreement we know that our end has to be ready to help.

I know that the usual "Concert blames NTL, NTL blame Concert" scenario has existed, but hopefully with the feedback that is being provided to both our supplier and the customer supplier the arrangements will be improved and everyone will be happy.

[[BROUZE]Plague]

soz m8 but servers are not fine the lag on sof dm is ridiculous andf thats on wp direct

[Slash]

Lo Kanibal m8:

I've had a quick look from carrier1's web site at the peering with Concert - seems OK at the mo, but perhaps Concert have problem under load ??

Check for yerself here ...

http://lg.carrier1.net/lg/lg.cgi

and type in the server IP.

will keep an eye on this l8r...

Slash

[Kanibal]

thx slash for the info

fortunately though, things have been much better last few days.
not as good as they were (160-180 ping) but better all the same (200-220 ping).
even better news for me is telewest have pulled there finger out and now have cable modems in my area.
i ordered 1 yesterday, installation date 04-10-00 :E

thx 2 all the gameplay staff who have helped me out ;)

[Thorne]

er Kanibal dont speak 2 soon,the problem is still occurring with Blueyonder Cable Modems,+ 500 pings on Wireplay SOf servers up in till 11pm at nite.

Can someone do some asking at Gameplays end please? Ive logged the ip details with Telewest again and theyre going 2 look in to it. I ask everyone who has similar problems to report it to Blueyonder so we can stress how serious this is.

Thanks