Fed up with it now

[#1]

I have done hundreds of different ping tests and speed tests using internet based  ones like speedtest.net and via the CMD prompt.....as am using a PC
The examples posted are "typical" of the results I get when i see ping spikes whilst gaming...ie I will drop out of a game shut all services/programs down then run some tests...
The only time I get crap results is in the evening - At all other times I dont get ANY issues. Paying extra to ensure gaming traffic gets priority is not working during peak times.  I have a months worth and more of monitoring.
Funny how the Maidenhead server gives me consistently 35ms and 6.6mbs every time I ping it during off peak hours then only in the evening do I get results that are just useless for anything let alone gaming

[#2]

RTW01 , as i posted earlier i had exactly same problem myself earlier .
as i suggested have you turned off UPNP on the router ?
also are you on 21CN ?
and had upload uncapped ?
these are the main things t found that made a big difference to my connection

[#3]

I do not need to make any changes....Everything was fine as it was for 6 months up till June 7th then bang the evenings went. Also the fact its ok at all other times tells me something else changed out of my control

[#4]

Hi there,
I've requested another port check from our suppliers as the answer to the last one was that there would be an update on Friday 15th.
In the mean time it'd be well worth trying the checks rongtw mentions - it may be that nothing's changed, but it may be that something's gone wrong or changed without your own intervention?

[#5]

UPNP is off...nothing changed apart from i dont get randomly booted from Bad company 2 now
Not 21cn
Plusnet have confirmed my upload syncs etc.....are ok
still only the evenings cause trouble...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\System32>ping ntp.plus.net -t
Pinging ntp.plus.net [212.159.13.50] with 32 bytes of data:
Reply from 212.159.13.50: bytes=32 time=79ms TTL=251
Reply from 212.159.13.50: bytes=32 time=183ms TTL=251
Reply from 212.159.13.50: bytes=32 time=161ms TTL=251
Reply from 212.159.13.50: bytes=32 time=219ms TTL=251
Reply from 212.159.13.50: bytes=32 time=205ms TTL=251
Reply from 212.159.13.50: bytes=32 time=98ms TTL=251
Reply from 212.159.13.50: bytes=32 time=108ms TTL=251
Reply from 212.159.13.50: bytes=32 time=116ms TTL=251
Reply from 212.159.13.50: bytes=32 time=178ms TTL=251
Reply from 212.159.13.50: bytes=32 time=151ms TTL=251
Reply from 212.159.13.50: bytes=32 time=194ms TTL=251
Reply from 212.159.13.50: bytes=32 time=210ms TTL=251
Reply from 212.159.13.50: bytes=32 time=120ms TTL=251
Reply from 212.159.13.50: bytes=32 time=143ms TTL=251
Reply from 212.159.13.50: bytes=32 time=151ms TTL=251
Reply from 212.159.13.50: bytes=32 time=107ms TTL=251
Reply from 212.159.13.50: bytes=32 time=121ms TTL=251
Reply from 212.159.13.50: bytes=32 time=163ms TTL=251
Reply from 212.159.13.50: bytes=32 time=167ms TTL=251
Reply from 212.159.13.50: bytes=32 time=156ms TTL=251
Reply from 212.159.13.50: bytes=32 time=163ms TTL=251
Reply from 212.159.13.50: bytes=32 time=141ms TTL=251
Reply from 212.159.13.50: bytes=32 time=131ms TTL=251
Reply from 212.159.13.50: bytes=32 time=106ms TTL=251
Reply from 212.159.13.50: bytes=32 time=135ms TTL=251
Reply from 212.159.13.50: bytes=32 time=122ms TTL=251
Reply from 212.159.13.50: bytes=32 time=130ms TTL=251
Reply from 212.159.13.50: bytes=32 time=242ms TTL=251
Reply from 212.159.13.50: bytes=32 time=304ms TTL=251
Reply from 212.159.13.50: bytes=32 time=301ms TTL=251
Reply from 212.159.13.50: bytes=32 time=175ms TTL=251
Reply from 212.159.13.50: bytes=32 time=220ms TTL=251
Reply from 212.159.13.50: bytes=32 time=240ms TTL=251
Reply from 212.159.13.50: bytes=32 time=331ms TTL=251
Reply from 212.159.13.50: bytes=32 time=240ms TTL=251
Reply from 212.159.13.50: bytes=32 time=156ms TTL=251
Reply from 212.159.13.50: bytes=32 time=239ms TTL=251
Reply from 212.159.13.50: bytes=32 time=196ms TTL=251
Reply from 212.159.13.50: bytes=32 time=176ms TTL=251
Reply from 212.159.13.50: bytes=32 time=172ms TTL=251
Reply from 212.159.13.50: bytes=32 time=191ms TTL=251
Reply from 212.159.13.50: bytes=32 time=48ms TTL=251
Reply from 212.159.13.50: bytes=32 time=108ms TTL=251
Reply from 212.159.13.50: bytes=32 time=135ms TTL=251
Reply from 212.159.13.50: bytes=32 time=162ms TTL=251
Reply from 212.159.13.50: bytes=32 time=147ms TTL=251
Reply from 212.159.13.50: bytes=32 time=152ms TTL=251
Reply from 212.159.13.50: bytes=32 time=122ms TTL=251
Reply from 212.159.13.50: bytes=32 time=199ms TTL=251
Reply from 212.159.13.50: bytes=32 time=139ms TTL=251
Reply from 212.159.13.50: bytes=32 time=178ms TTL=251
Reply from 212.159.13.50: bytes=32 time=191ms TTL=251
Reply from 212.159.13.50: bytes=32 time=235ms TTL=251
Reply from 212.159.13.50: bytes=32 time=226ms TTL=251
Reply from 212.159.13.50: bytes=32 time=230ms TTL=251
Reply from 212.159.13.50: bytes=32 time=201ms TTL=251
Reply from 212.159.13.50: bytes=32 time=220ms TTL=251
Reply from 212.159.13.50: bytes=32 time=100ms TTL=251
Reply from 212.159.13.50: bytes=32 time=166ms TTL=251
Reply from 212.159.13.50: bytes=32 time=152ms TTL=251
Reply from 212.159.13.50: bytes=32 time=137ms TTL=251
Ping statistics for 212.159.13.50:
    Packets: Sent = 61, Received = 61, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 331ms, Average = 170ms
Control-C
^C
C:\Windows\System32>time
The current time is: 19:43:42.11
Enter the new time:
C:\Windows\System32>date
The current date is: 20/07/2011
Enter the new date: (dd-mm-yy)
C:\Windows\System32>
ALL was fine at 1900......this is not correct fro a PRO based customer

[#6]

Over 2 months go i reported this....
I have had one specialist fault engineer out - everything perfect
2 attempts at a lift and shift - never happened but at least spoke to engineer
Then yesterday I was supposed to be getting another lift and shift attempt AM and nothing! - reported this on my ticket 3 times yesterday and not even a reply/notifiaction from plusnet.
I spend a full day of my "holiday" waiting at home for nothing.
Also My bank statement comes....I was offereed a months BB free as a goodwill gesture....nah the payment was taken as per usual - This is not the same company i signed up to 2 years ago.
If any of the good CS people on here can look at ticket 43564211 and tell me what is going on I would be grateful and it might just stop me from exploding down the phone at someone.

[#7]

Hi there,
Your ticket is in hand with one of our faults agents as a personal ticket, he'll be booking your engineer shortly and should be in touch to confirm. In the mean time I've added a credit to your account to cover the next month's broadband fees as a gesture of goodwill, sorry that this didn't happen this month for you.

[#8]

3 months down the line from first reporting this to plusnet - 3 engineer visits, a lift and shift and a brand spanking new plusnet router and still the problem persists - From what i gather the issue is with plusnets provider....BT.
I have still no clue what / who is causing the issue i have - although it is not my end of things. Ran BT speedtest tonight  - 2.6Gb, although  5 mins previous to this my interent was standing still
Anyone with suggestions on my next step - Ofcom? MAC Code?

[#9]

Have you looked to see what speeds other people on your exchange are getting: http://maps.thinkbroadband.com/?utm_source=mainsite&utm_medium=text&utm_campaign=maps&utm_content=we...

[#10]

RTW01
I know how you feel
I have had the same ticket running for about 3 months.
Lots of "its fine" and not our problem answers.
I had to push very hard to get an engineer.
Now its "what do you expect"
Its very frustrating and hard work to get any more than a quick glance from the variuos people who take it in turns to "fob you off"
keep going, don't let them off the hook.
have you read
General / Your Feedback / Re: Sadly leaving -> now happily staying

[#11]

Hi RTW01,
Thanks for bearing with us, I understand it's very frustrating and I'm sorry it's been going on so long. Looking at the ticket I can see one of our faults agents has taken personal ownership of this fault and has escalated it with our suppliers, There'll be an update for you later on today.

[#12]

Hi RTW01,
have you had any success or improvement yet?