Constant High Latency

[#1]

I've been experiencing really high latency for several days now. This is without anything on the network but a single laptop. Tried with different laptops (one at a time) but the latency continues to be very high.
Pinging www.google.com [74.125.140.105] with 32 bytes of data:
Reply from 74.125.140.105: bytes=32 time=86ms TTL=46
Reply from 74.125.140.105: bytes=32 time=87ms TTL=46
Reply from 74.125.140.105: bytes=32 time=44ms TTL=46
Reply from 74.125.140.105: bytes=32 time=85ms TTL=46
Reply from 74.125.140.105: bytes=32 time=96ms TTL=46
Reply from 74.125.140.105: bytes=32 time=82ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=58ms TTL=46
Reply from 74.125.140.105: bytes=32 time=88ms TTL=46
Reply from 74.125.140.105: bytes=32 time=59ms TTL=46
Reply from 74.125.140.105: bytes=32 time=95ms TTL=46
Reply from 74.125.140.105: bytes=32 time=71ms TTL=46
Reply from 74.125.140.105: bytes=32 time=59ms TTL=46
Reply from 74.125.140.105: bytes=32 time=93ms TTL=46
Reply from 74.125.140.105: bytes=32 time=94ms TTL=46
Reply from 74.125.140.105: bytes=32 time=78ms TTL=46
Reply from 74.125.140.105: bytes=32 time=42ms TTL=46
Reply from 74.125.140.105: bytes=32 time=44ms TTL=46
Reply from 74.125.140.105: bytes=32 time=93ms TTL=46
Reply from 74.125.140.105: bytes=32 time=81ms TTL=46
Reply from 74.125.140.105: bytes=32 time=89ms TTL=46
Reply from 74.125.140.105: bytes=32 time=69ms TTL=46
Reply from 74.125.140.105: bytes=32 time=59ms TTL=46
Reply from 74.125.140.105: bytes=32 time=56ms TTL=46
Reply from 74.125.140.105: bytes=32 time=77ms TTL=46
Reply from 74.125.140.105: bytes=32 time=58ms TTL=46
Reply from 74.125.140.105: bytes=32 time=64ms TTL=46
Reply from 74.125.140.105: bytes=32 time=43ms TTL=46
Reply from 74.125.140.105: bytes=32 time=78ms TTL=46
Reply from 74.125.140.105: bytes=32 time=84ms TTL=46
Reply from 74.125.140.105: bytes=32 time=97ms TTL=46
Reply from 74.125.140.105: bytes=32 time=84ms TTL=46
Reply from 74.125.140.105: bytes=32 time=74ms TTL=46
Reply from 74.125.140.105: bytes=32 time=85ms TTL=46
Reply from 74.125.140.105: bytes=32 time=73ms TTL=46
Reply from 74.125.140.105: bytes=32 time=83ms TTL=46
Reply from 74.125.140.105: bytes=32 time=75ms TTL=46
Reply from 74.125.140.105: bytes=32 time=62ms TTL=46
Reply from 74.125.140.105: bytes=32 time=76ms TTL=46
Reply from 74.125.140.105: bytes=32 time=58ms TTL=46
Reply from 74.125.140.105: bytes=32 time=67ms TTL=46
Reply from 74.125.140.105: bytes=32 time=48ms TTL=46
Reply from 74.125.140.105: bytes=32 time=56ms TTL=46
Reply from 74.125.140.105: bytes=32 time=49ms TTL=46
Reply from 74.125.140.105: bytes=32 time=85ms TTL=46
Reply from 74.125.140.105: bytes=32 time=68ms TTL=46
Reply from 74.125.140.105: bytes=32 time=50ms TTL=46
Reply from 74.125.140.105: bytes=32 time=82ms TTL=46
Reply from 74.125.140.105: bytes=32 time=86ms TTL=46
Reply from 74.125.140.105: bytes=32 time=59ms TTL=46
Reply from 74.125.140.105: bytes=32 time=88ms TTL=46
Reply from 74.125.140.105: bytes=32 time=82ms TTL=46
Reply from 74.125.140.105: bytes=32 time=82ms TTL=46
Reply from 74.125.140.105: bytes=32 time=76ms TTL=46
Reply from 74.125.140.105: bytes=32 time=91ms TTL=46
Reply from 74.125.140.105: bytes=32 time=80ms TTL=46
Reply from 74.125.140.105: bytes=32 time=74ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=81ms TTL=46
Reply from 74.125.140.105: bytes=32 time=42ms TTL=46
Reply from 74.125.140.105: bytes=32 time=75ms TTL=46
Reply from 74.125.140.105: bytes=32 time=90ms TTL=46
Reply from 74.125.140.105: bytes=32 time=77ms TTL=46
Reply from 74.125.140.105: bytes=32 time=66ms TTL=46
Reply from 74.125.140.105: bytes=32 time=97ms TTL=46
Reply from 74.125.140.105: bytes=32 time=65ms TTL=46
Reply from 74.125.140.105: bytes=32 time=39ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=77ms TTL=46
Reply from 74.125.140.105: bytes=32 time=74ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=113ms TTL=46
Reply from 74.125.140.105: bytes=32 time=71ms TTL=46
Reply from 74.125.140.105: bytes=32 time=91ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=63ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=71ms TTL=46
Reply from 74.125.140.105: bytes=32 time=69ms TTL=46
Reply from 74.125.140.105: bytes=32 time=52ms TTL=46
Reply from 74.125.140.105: bytes=32 time=50ms TTL=46
Reply from 74.125.140.105: bytes=32 time=86ms TTL=46
Reply from 74.125.140.105: bytes=32 time=77ms TTL=46
Reply from 74.125.140.105: bytes=32 time=49ms TTL=46
Reply from 74.125.140.105: bytes=32 time=60ms TTL=46
Reply from 74.125.140.105: bytes=32 time=58ms TTL=46
Reply from 74.125.140.105: bytes=32 time=47ms TTL=46
Reply from 74.125.140.105: bytes=32 time=72ms TTL=46
Reply from 74.125.140.105: bytes=32 time=90ms TTL=46
Reply from 74.125.140.105: bytes=32 time=83ms TTL=46
Reply from 74.125.140.105: bytes=32 time=63ms TTL=46
Reply from 74.125.140.105: bytes=32 time=70ms TTL=46
Reply from 74.125.140.105: bytes=32 time=88ms TTL=46

C:\Users\Dan>tracert www.google.com
Tracing route to www.google.com [74.125.140.105]
over a maximum of 30 hops:
  1    3 ms    97 ms    99 ms  dsldevice.lan [192.168.1.254]
  2    82 ms    56 ms    45 ms  lo0-central10.pcl-ag06.plus.net [195.166.128.187
]
  3    96 ms    52 ms    43 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.18
2]
  4    75 ms    64 ms    42 ms  xe-10-3-0.pcl-cr02.plus.net [212.159.0.214]
  5    65 ms    49 ms    65 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    61 ms    39 ms    84 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  7    86 ms    72 ms    53 ms  72.14.222.97
  8  141 ms    72 ms    72 ms  209.85.246.244
  9    49 ms    58 ms    91 ms  209.85.253.94
10    46 ms    92 ms    68 ms  72.14.239.152
11    56 ms    60 ms    66 ms  216.239.51.213
12    *        *        *    Request timed out.
13    76 ms    84 ms    75 ms  wq-in-f105.1e100.net [74.125.140.105]
Trace complete.
C:\Users\Dan>

Looking at the tracert 90 odd ms looks awfully high for a trace from a laptop to the defalt gateway that is connected directly to the router via Ethernet. Incidental Ethernet cable or wireless the times are around the same.
This is making playing online games nearly impossible and incredibly frustrating. Any help would be appreciated.
Regards
Dan

[#2]

Maybe help if you post any stats you can get from your router.
Is the latency high all the time or at what might be considered peak usage times.
Have tried running ttb quality monitor

[#3]

I took the previous readings at 7:15am so not exactly peak time, but it has been the same at peak times. There is no change on time of day.
Uptime : 0 Days 14:08:35
DSL Type : G.992.5 annexA
Bandwidth : 444 / 14,487
Data Transdered 0.00 / 104.00
Output Power : 12.0 / 0.0
Line Attenuation : 10.5 / 27.0
SN Margin: 30 / 6.5
Vendor ID TMMB / IFTN
No loss of framing/signal/power/link/error seconds
FEC Errors NA / 1,116,795
CRC Errors NA / 56
HEC Errors 0 / 54
I'll start the quality monitor now but the latency has not changed for days, hovering around 70-90, so I would not expect the monitor to do anything but show this continuation.

[#4]

I am no expert but looks to me you have some sort of fault  - High number of errors and low (possibly banded upload speed) 444
If no PN staff look at your thread I would go down the faults report route  https://faults.plus.net/
You could try a graceful resync rather than just switching off the router and see if that improves it at all

[#5]

Honestly, I think you're maxing out the upload on your line. This is causing the problems you're seeing with the latency and poor performance.
Your upload speed is currently capped so that's not going to be helping. I'm going to place an order to uncap the upload which should complete tomorrow and help a bit.

[#6]

Hi Chris,
Actually, after looking up the symptoms of maxing out the upload that does sound very likely. Not sure what would be causing it to max out when I can happily play Guild Wars 2 on a tethered mobile connection that runs at about 40 kbps. So I'm not dumping that much upstream as far as I can tell, but I welcome anything that might stabilize the quality.
Many thanks
Dan

[#7]

At some points of the day you're doing around 150Mb per hour upload, which on a 448 upload speed is pretty much the max I'd expect. The uncap should help increase that, but you might want to check for any software doing lots of uploads just in case.