topic Re: Its terrible, really is.. Pings are awful! in Plusnet Feedback

Its terrible, really is.. Pings are awful!

KaotiK — Wed, 06 Jan 2010 10:22:30 GMT

Now im going to post here because its the only place i see people getting answers on problems. If anyones bothered to look at the gaming forums ul see a few gamers moaning constantly about high pings in the evening. Now this has been going on for months now really, you get the odd week where its fine but the mjaority of the time games for me at least get unplayable at those pings. So is there anyone able to shed some light on why its happening AGAIN. Im close to moving ISP again its just not acceptable to be paying for this rubbish. I never thought id find another ISP which in a way is as bad as AOL. (maybe not as bad, but its getting pretty close.)
So yea please, just sort it out or something!

Re: Its terrible, really is..

mal0z — Wed, 06 Jan 2010 10:26:24 GMT

Some of the regular PN CS and comms staff here on the forum, say they are gamers - so hopefully they will respond ?

Re: Its terrible, really is..

KaotiK — Wed, 06 Jan 2010 14:04:55 GMT

Lets hope so as im getting ping spikes in the god damn day time also, its beyond a joke.

Re: Its terrible, really is..

mal0z — Wed, 06 Jan 2010 14:53:57 GMT

Don't you think it might help attract appropriate attention if you changed the title of the thread ?

Re: Its terrible, really is..

Lurker — Wed, 06 Jan 2010 15:29:04 GMT

The OP doesn't really give much in the way of useful info - no mention of hardware, configuration etc.
Its not exactly encouraging folks to stick their necks out with suggestions.

Re: Its terrible, really is.. Pings are awful!

KaotiK — Wed, 06 Jan 2010 17:10:55 GMT

there you go changed.. and hardware? its not my hardware lol, thats would be a typical answer. If thats what u meant so all people moaning about pings in the gamers forum have hardware probs etc. Its blatantly a plusnet problem as it was discussed for months over there and i thought it was fixed, but its reared its ugly head again. i Look at all the gateways and they all look so congested if thats the right word exept for one, which luckily i jsut managed to get on after rebooting the router and bam my pings is nice and low, whether it will stay like that in the evening though is another matter.
edit - love that, the minute i say my pings are low after switching to a gateway that looks good, its spikes up again .. great.
Im on pcl-ag02 gateway now btw, which by the looks of http://www.plus.net/support/network_performance/broadband_packets_drop.shtml is the only one that isnt congested and yet, high pings..

Re: Its terrible, really is.. Pings are awful!

Lurker — Thu, 07 Jan 2010 08:42:25 GMT

I didn't say you had a problem with hardware, I simply pointed out that you haven't given anybody much to go on to help you.
Until you describe your problem, people really aren't likely to be able to offer much help.
Suggestion: Tell folks what your problem is - start with something simple like saying what game it is, and what platform, and what servers you are trying to contact.

Re: Its terrible, really is.. Pings are awful!

Mand — Thu, 07 Jan 2010 09:35:14 GMT

Hi there,
As James has said if you could give us a little more info we could try and help.
We do have an issue we're working on with evening latency, but that affects customers on our 21CN platform (which you're not on) so you're not a part of that issue.
If you could tell us what game it is, when you have the problem, where the server is based, a traceroute to the server and your setup we can try and take it from there.

Re: Its terrible, really is.. Pings are awful!

Myst — Thu, 07 Jan 2010 10:06:03 GMT

As i'm sure you are aware there are 11 pages at the last count on the gamer forum on the subject!
Below is copied from there from two nights ago - last night was just as bad, this morning seems better although ping is erratic, just not as high
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 56 ms 57 ms 60 ms lo0-plusnet.pte-ag2.plus.net [195.166.128.72
3 * * * Request timed out.
4 * * * Request timed out.
5 61 ms 56 ms 73 ms rt0.thdo.bbc.co.uk [212.58.239.25]
6 65 ms 57 ms 54 ms 212.58.238.133
7 63 ms 57 ms 58 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]
1 <1 ms <1 ms <1 ms 192.168.0.1
2 56 ms 59 ms 59 ms lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * 819 ms 59 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]e complete.

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 65 ms 60 ms 78 ms lo0-plusnet.pte-ag2.plus.net [195.166.128.72
3 * 1102 ms 61 ms ge0-0-0-504.pte-gw2.plus.net [84.92.4.90]
4 77 ms 72 ms 57 ms vl23.thn-gw2.plus.net [212.159.4.20]
5 63 ms 60 ms 59 ms rt0.thdo.bbc.co.uk [212.58.239.25]
6 58 ms 57 ms 54 ms 212.58.238.133
7 65 ms 54 ms 55 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Re: Its terrible, really is.. Pings are awful!

GixerBoy75 — Thu, 07 Jan 2010 10:44:18 GMT

Hi,
I've just made a similar post in the gamer section, but as there seems to be some form of support staff in this area, here's further proof of there being an issue. This was taken literally a couple of minutes ago:-
C:\>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.0.1]
2 2 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
3 33 ms 31 ms 31 ms lo1.ptn-ag03.plus.net [195.166.128.43]
4 32 ms 31 ms 32 ms gi2-6.ptn-gw01.plus.net [84.92.3.45]
5 34 ms 31 ms 30 ms te2-2.thn-gw1.plus.net [212.159.1.54]
6 211 ms 210 ms 212 ms te2-3.thn-gw2.plus.net [212.159.1.58]
7 32 ms 31 ms 31 ms rt0.thdo.bbc.co.uk [212.58.239.25]
8 32 ms 31 ms 31 ms 212.58.238.149
9 33 ms 33 ms 31 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
10 34 ms 33 ms 32 ms www.bbc.co.uk [212.58.253.67]
Trace complete.

Re: Its terrible, really is.. Pings are awful!

KaotiK — Thu, 07 Jan 2010 10:46:07 GMT

I get the problem on World of Warcraft, as its the game i mostly play, in the evenings, sometimes it start 7ishpm sometimes later til like 10pm or even later 10:30pm. on the odd occasion it happens during the day, like yesterday. The realm i play is an english one. Ive done a wireshark capture on it before and put it in a ticket and they said blah blah they were gonna prioritise it as it wasnt, yet that was ages ago... and no improvement. Like i said the week around christmas there was NO problems, low pings always, before that as u know it was terrible, and now its terrible again. Il do a traceroute tonight or whenever it goes bad again.
I still dont understand how WoW isnt being prioritzed properly 😐 Il have to try cod aswell around these times as ive seen people in gamers forum complain of that to.
Hardware wise im on a netgear router DG834G, Wired, etc dunno waht else to mention. But i hope it doesnt turn into its a your hardware problem not ours cuz its many people having these problems not me. And the fact its at the busiest times kinda shows what the problem is..
Im on the unlimited package.. isit that? I just hope it gets sorted because im not just gonna put up with it and get frustrated gaming every night.
Like myst said, theres pages and pages of people complaining, posting traceroutes in the gamers forum, just check there!

Re: Its terrible, really is.. Pings are awful!

GixerBoy75 — Thu, 07 Jan 2010 11:30:51 GMT

It is getting worse for me as the day goes on!
Tracing route to www.bbc.net.uk [212.58.251.195]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms DD-WRT [192.168.0.1]
2 1 ms 2 ms 1 ms mygateway1.ar7 [192.168.1.1]
3 254 ms 276 ms 281 ms lo1.ptn-ag03.plus.net [195.166.128.43]
4 456 ms 423 ms 410 ms gi2-6.ptn-gw01.plus.net [84.92.3.45]
5 300 ms 304 ms 309 ms te2-2.thn-gw1.plus.net [212.159.1.54]
6 322 ms 331 ms 325 ms te2-3.thn-gw2.plus.net [212.159.1.58]
7 330 ms 338 ms 345 ms rt0.thdo.bbc.co.uk [212.58.239.25]
8 346 ms 354 ms 350 ms 212.58.238.149
9 298 ms 308 ms 296 ms 212.58.239.62
10 295 ms 304 ms 310 ms www.bbc.co.uk [212.58.251.195]
Trace complete.

Re: Its terrible, really is.. Pings are awful!

Mand — Thu, 07 Jan 2010 12:25:38 GMT

@KaotiK, we've got some fixes for WoW happening on Tuesday.
@GixerBoy75, can you do a ping as well please?

Re: Its terrible, really is.. Pings are awful!

GixerBoy75 — Thu, 07 Jan 2010 12:36:03 GMT

Sure here you go:-
Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms DD-WRT [192.168.0.1]
2 2 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
3 313 ms 174 ms 225 ms lo1.ptn-ag03.plus.net [195.166.128.43]
4 201 ms 351 ms 239 ms gi2-6.ptn-gw01.plus.net [84.92.3.45]
5 186 ms 182 ms 148 ms te2-2.thn-gw1.plus.net [212.159.1.54]
6 247 ms 216 ms 198 ms te2-3.thn-gw2.plus.net [212.159.1.58]
7 205 ms 244 ms 317 ms rt0.thdo.bbc.co.uk [212.58.239.25]
8 90 ms 138 ms 254 ms 212.58.238.149
9 309 ms 212 ms 234 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
10 208 ms 190 ms 229 ms www.bbc.co.uk [212.58.253.67]
Trace complete.
Pinging www.bbc.net.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=244ms TTL=119
Reply from 212.58.253.67: bytes=32 time=238ms TTL=119
Reply from 212.58.253.67: bytes=32 time=223ms TTL=119
Reply from 212.58.253.67: bytes=32 time=245ms TTL=119
Ping statistics for 212.58.253.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 245ms, Average = 237ms

Re: Its terrible, really is.. Pings are awful!

KaotiK — Thu, 07 Jan 2010 14:09:46 GMT

Glad to hear WoW is getting a fix. Hopefully that will fix the problems. But i look at the gateway graphs and i dunno if i read em right but every one of them looks really busy and congested? is that not overloaded?

Re: Its terrible, really is.. Pings are awful!

Mand — Thu, 07 Jan 2010 14:36:01 GMT

@GixerBoy75, that looks like a problem BT side, the latency is before our ERX, and occurs all the way down the traceroute.
@KaotiK, some gateways are busier than others, but they're not all congested.

Re: Its terrible, really is.. Pings are awful!

KaotiK — Thu, 07 Jan 2010 14:44:13 GMT

Tracing route to www.bbc.net.uk [212.58.251.195]
over a maximum of 30 hops:
1 2 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 49 ms 31 ms 27 ms lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
3 32 ms 80 ms 53 ms gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
4 30 ms 26 ms 27 ms te2-1.pcl-gw02.plus.net [212.159.1.114]
5 35 ms 30 ms 56 ms te2-2.thn-gw2.plus.net [212.159.0.190]
6 44 ms 29 ms 31 ms rt0.thdo.bbc.co.uk [212.58.239.25]
7 28 ms 66 ms 39 ms 212.58.238.149
8 30 ms 46 ms 72 ms 212.58.239.62
9 50 ms 31 ms 26 ms www-vip.telhc.bbc.co.uk [212.58.251.195]
Trace complete.
C:\Users\KaotiK>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.251.195] with 32 bytes of data:
Reply from 212.58.251.195: bytes=32 time=69ms TTL=120
Reply from 212.58.251.195: bytes=32 time=28ms TTL=120
Reply from 212.58.251.195: bytes=32 time=69ms TTL=120
Reply from 212.58.251.195: bytes=32 time=69ms TTL=120
Ping statistics for 212.58.251.195:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 69ms, Average = 58ms

heres a trace and ping right now, its a bit up and down it seeems, my ping WoW right now is relatively high, so im guessing it is mainly wow not being prioritized properly and the fixes tuesday should solve it? Although msot of the time i do a trACE theres pings in there way over a 100, and evenings it is worse.

Re: Its terrible, really is.. Pings are awful!

GixerBoy75 — Thu, 07 Jan 2010 14:58:54 GMT

Seems better now for some reason:-
Tracing route to www.bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.0.1]
2 3 ms 1 ms 1 ms mygateway1.ar7 [192.168.1.1]
3 32 ms 31 ms 32 ms lo1.ptn-ag03.plus.net [195.166.128.43]
4 32 ms 30 ms 30 ms gi2-6.ptn-gw01.plus.net [84.92.3.45]
5 32 ms 31 ms 31 ms te2-2.thn-gw1.plus.net [212.159.1.54]
6 31 ms 30 ms 30 ms te2-3.thn-gw2.plus.net [212.159.1.58]
7 33 ms 31 ms 31 ms rt0.thdo.bbc.co.uk [212.58.239.25]
8 33 ms 31 ms 31 ms 212.58.238.149
9 32 ms 32 ms 33 ms te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
10 33 ms 33 ms 34 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.
Pinging www.bbc.co.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=31ms TTL=119
Reply from 212.58.253.67: bytes=32 time=32ms TTL=119
Reply from 212.58.253.67: bytes=32 time=32ms TTL=119
Reply from 212.58.253.67: bytes=32 time=32ms TTL=119
Ping statistics for 212.58.253.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms

Re: Its terrible, really is.. Pings are awful!

KaotiK — Fri, 08 Jan 2010 17:30:15 GMT

Its 5:30pm... and already my ping is sky high. Something is so wrong somewhere theres no way this is jsut a priority issue. Its exactly like it was few weeks ago when you were saying the networks etc are broke and your adding capacity. You need to add a load more? Another night of horrendous pings, great.

Re: Its terrible, really is.. Pings are awful!

Mand — Fri, 08 Jan 2010 18:00:17 GMT

We've got more than enough capacity at the moment, and more on order (to keep ahead of forecasting).
Is the problem specific to WoW, or across the board?