topic Re: Fed up with it now in Plusnet Feedback

Fed up with it now

RTW01 — Thu, 30 Jun 2011 19:56:22 GMT

Have been a customer from Jan 2009 paying £20 a month for Your way pro service ( and now have a plusnet home phone service). I was happy until now. After 3 weeks, 4 tickets ( 3 still open ) I can not game in the evening on my pc due to latency spikes of various length. I have completed all the tests ruling out my equipment as asked by various PN staff, I have provided (and can provide loads more) evidence of my problem. The issue is just affecting gaming my whole traffic profile is getting slowed. Every day since the 7th of June i have been getting excellent latency outside the peak hours - typically 35 -60ms for most uk game servers i try - on different games COD, BFBC2 etc...but once evening comes i can anywhere from 35ms upto 600ms - Which makes playing FPS games useless - let alone waiting for internet pages to load up during these spikes (which can last most of the evening or a few mins).
Raising help ticket(s) in my case seems to have caused confusion within PN as i keep getting the same request/question over and over - Which if someone had read the tickets in full or asked me questions to help clarify my issue i think we would be nearer a solution. However no one from PN has called me once - i have called them 4 times now The last time today @ 12:30. No one has yet to answer my query of "am i being throttled" not that i download massive files - 80% of my online time is gaming which hardly uses any bandwidth up. I was told today my contention ratio is 50 :1 - is that right for a Pro package? My VP is ok apparently.

Is any]ne else on an old "pro" package that is getting useless gaming latency in the evenings? Am based in Market Weighton , East yorks. I may aswell play COD from the moon on an evening. speed test run just now....

Re: Fed up with it now

RTW01 — Thu, 30 Jun 2011 20:03:25 GMT

add another test result

on a 7000k line that normally gives 35ms and about 6600 during the off peak hours of day...../sigh
more of the same

Re: Fed up with it now

RTW01 — Thu, 30 Jun 2011 20:13:54 GMT

Speaking to two clan mates, who were thinking of joining PN - needless to say they are holding off

Re: Fed up with it now

ChrisL — Thu, 30 Jun 2011 22:36:46 GMT

This sounds much more like a contention issue with your local exchange than anything in Plusnet's control?
Hope you get it sorted soon.
Chris

Re: Fed up with it now

spraxyt — Thu, 30 Jun 2011 23:16:49 GMT

Has contention on the VP you are connected to at the exchange been specifically checked, or is the "my VP is OK apparently" statement, which I assume came from support, based on BT not having announced any issues in that exchange?
If you download something across the midnight threshold does the download speed change at midnight?

Re: Fed up with it now

rongtw — Fri, 01 Jul 2011 06:18:14 GMT

i play bc2 mainly, and yes i used to have loads of problems with high pings on PN but eventually we sort of resolved it
.
firstly , you need if available to be on 21CN and have the upload uncapped.
this does make a fair bit of difference
.
secondly i found the thompson router 585 v8, poooh so i use a old BT HH2 seams a lot better for gaming.
next you need to go into router setup , and disable Upnp, unbelievable but yes it makes a difference .
and now i game fairly good connection with the odd ping spike on the evening but its a vast improvement since i first moved to PN
i am in west Yorkshire , with extra package only , i did try pro add on but made no difference to gaming

Re: Fed up with it now

RTW01 — Fri, 01 Jul 2011 06:24:31 GMT

"The VP for this circuit has been checked and has been found to be not over utilised currently." - from Matt
Things tend to return to normal before midnight.
Just seen rongtw added...
Thanks for the pointers im sure unless PN can sort this i'll have to look at that, But i have used this connection for 2 years without any problems, I want to know what has changed?

Re: Fed up with it now

orbrey — Fri, 01 Jul 2011 09:19:17 GMT

Hi there,
Are you seeing the same slow speeds on a BT speed test, and do you get the same high pings when gaming? Most important thing is to try the BT speed test when the issue is apparent though.

Re: Fed up with it now

RTW01 — Fri, 08 Jul 2011 20:43:11 GMT

BT speed test run just before this gave 4.7mps...
I have an Engineer coming on Mondaty for a BOOST visit....to check for cable corrosion Funny how the cable corrosion only affects me in the evenings....
I have asked countless times if I am being throttled....still no answer regarding this
Its an absolute joke the service i get in a evening

Re: Fed up with it now

WWWombat — Sat, 09 Jul 2011 18:48:40 GMT

After answering another post on here (in the Broadband & Routers section), I just realised that you may be showing the same symptoms - that the problem could be your upstream sync speeds.
Certainly your upstream speeds are a bit better than on the other thread, but they still seem low. And the ping times are horrendous - but could be explained if packets require a lot of retries to get over a bad uplink.
Can you monitor and post a variety of the sync speeds, rather than (or in addition to) speedtest results? It would be good to get an idea of what theat is syncing at, and whether it is changing (ie disconnecting).

Quote
Funny how the cable corrosion only affects me in the evenings....

Interference has this horrible habit of only turning up in the evening. My parents suffered a problem that only started at around 5pm, and went on until 9 or 10pm. That was mainly because of interference caused by internal wiring.
As I said on the other thread, though, interference on upstream is comparitively rare.

Re: Fed up with it now

RTW01 — Mon, 11 Jul 2011 16:29:00 GMT

Not seen engineer...but aparently no faults, BT wholesale say "lift and shift" wont improve anything.. Enginner said its down to congestion/bottlenecks at peak time and I may have to lump it. Well this wasnt an issue till June 7th so why lately?
Therefore at square one again. PN confirm i am not being deliberately throttled.
will mention upstream sync to PN in my ticket

Re: Fed up with it now

orbrey — Tue, 12 Jul 2011 10:43:02 GMT

Hi there,
I can see the usertools exchange checker is reporting the VP status as green but that's from June, so I've emailed to find out the latest on the exchange and will let you know as soon as we have any information back.

Re: Fed up with it now

RTW01 — Sat, 16 Jul 2011 10:38:11 GMT

Still not identified or fixed, Reported this on June 7th.....

Re: Fed up with it now

dannyflounders — Sat, 16 Jul 2011 19:06:37 GMT

I would not rely on speedtest.net or pingtest.net for results as you will find they can be extremely inaccurate.
In fact, at present the manchester server is given extreme erratic results.
If you are going to use those services, you need to be completing at least 3 tests from different servers / locations.
My brother tried manchester last night and got 87 ping, 7 jitter, very poor line.
Immediately tried Maidenhead and got 31 ping, 0 jitter and grade A line.
So don't rely on those tests, you need multiple tests.
Also some tests may not work properly if your router is blocking ping from wan (internet side), such tests are found on dslreports website for example.

Re: Fed up with it now

pierre_pierre — Sat, 16 Jul 2011 19:23:18 GMT

nearly all PN lines are routed throught the London data centre in Docklands, that is why you results are like that

Re: Fed up with it now

RTW01 — Sun, 17 Jul 2011 10:40:10 GMT

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

Re: Fed up with it now

rongtw — Sun, 17 Jul 2011 13:42:52 GMT

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

Re: Fed up with it now

RTW01 — Sun, 17 Jul 2011 18:04:10 GMT

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

Re: Fed up with it now

orbrey — Mon, 18 Jul 2011 15:24:35 GMT

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?

Re: Fed up with it now

RTW01 — Wed, 20 Jul 2011 18:49:45 GMT

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