Peak time latency spikes

[#1]

Traceroute 00-20
Everything appears normal and has been since switching gateways.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Private>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.67]
over a maximum of 30 hops:
  1    1 ms    1 ms    <1 ms  192.168.1.1
  2    23 ms    16 ms    15 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  3    15 ms    15 ms    15 ms  link5-central10.pcl-gw01.plus.net [84.93.249.8]
  4    15 ms    14 ms    14 ms  xe-0-2-0.pcl-cr01.plus.net [212.159.1.0]
  5    15 ms    14 ms    15 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    15 ms    15 ms    15 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    16 ms    15 ms    15 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    17 ms    17 ms    15 ms  132.185.255.148
11    15 ms    15 ms    15 ms  bbc-vip112.telhc.bbc.co.uk [212.58.244.67]
Trace complete.
C:\Users\Private>

[#2]

Back to normal
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=38ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=38ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=36ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250
Reply from 212.159.6.10: bytes=32 time=37ms TTL=250

[#3]

@ Chris Pettitt - If you could take a look at my line that would be appreciated, although I already have a fault logged due to a possible noisy line.  I highly doubt the possible line problems are causing the spiking issues given that so many others are still experiencing this issue, it just appears to be congestion that isn't managed automatically. 
Is there any news on a likely timescale for an update on the works required to address the issue, or when a fix might be available.  I am sure I am not alone in saying it will make a difference to how long customers choose to stick with Plusnet.
There also appear to be significant issues with the forums - it keeps timing out and I have been trying for at least 15 minutes to post this.
Thank you,

[#4]

I believe Chris is aware of your other thread.  Plusnet have said that there doesn't appear to be a congestion problem within their Network if I understood correctly, I'm sure Kelly will comment a bit later.
No problems posting here.

[#5]

@Kelly
Have you been able to identify any common factors with those suffering serious effects compared to those only seeing a lesser or no impact?
e.g Which RAS and/or (super)node users are connected to on the BT Backhaul. Are there any common factors with those users with BT Retail or any other ISP that are seeing similar issues?
e.g IIRC some users (mostly Fibre) were seeing a significant impact on ptn-ag04 at some point whereas I'm only seeing some increase in pings and no slowdown, whereas purleigh for example was seeing no effect on this gateway. last night.
Does there appear to be any significant differences between 20CN and 21CN taking account of the different number of users on each?

[#6]

Quote from: purleigh

Why isn't it also shown on the "Priority Problems" page - http://www.plus.net/support/service/problems/index.php  ?

Have you not looked at the archive to see when the last priority problem was raised?

[#7]

Is anyone on a fibre service and affected by the peak time slow downs in the south east of england/london?

[#8]

yes, i'm on fibre unlimited and on the haslemere (GU27) exchange

[#9]

Really poor performance last night on:
pcl ag01
ptn ago3
thn ago3 (first time I've even been on that gateway)
Settled on:
THN-AG1 (first time I've been on that gateway, too).
Because I got fed up with hopping to consistently bad gateways, with speed graphs all over the place. This was the 'best' of the lot, but still uneven.

[#10]

@ ricmelia
I'm in Milton Keynes...my tbb graph looks slightly worse than yours yest in terms of the max pings....but d/l speeds for me were constant around 84Mb/s.
a few fibre users with problems were from the south west so thought that might mean something, but guess not. Will try gateway hopping and speed testing this evening to see how my results compare.

[#11]

the gateway hop at 7:30 last night sorted the speed for me, went from 2Mb back up to 70Mb. Ping graph (only set it up yesterday at 6.30, hence the red at the start) shows it was still not perfect though. Looks fairly clean overnight and so far today though.
oh and I've just noticed you're getting 84Mb - were you looking for people on FTTP? I'm on FTTC...

[#12]

Hi,
If anybody experiences any performance issues, would it be possible for you to perform a Tap3 test?
To run the TAP3 test you will need to change the Username and Password you are connecting to in the router. The details are as below:
USERNAME: speedtest@speedtest_domain
PASSWORD: testing
Once successfully logged in, you can then access the Speed Tester server by typing http://217.32.105.42 in your browser.
Once you have completed the speed test you will then need to change the details in your router back to your standard Plusnet Username and Password.
If you could post your results it would be appreciated.

[#13]

Have you checked it actually works now Chris? It didn't last time I tried it 

[#14]

I think it won't work because the newer speed test tries to connect to www.adobe.com (not sure why) which it can't resolve. So you just get a system is busy error.

[#15]

Everything should now be working on for a Tap3 test, please let me know if that's not the case.