Peak time latency spikes

[#1]

C:\Users\X>ping bbc.co.uk
Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=346ms TTL=243
Reply from 212.58.241.131: bytes=32 time=227ms TTL=243
Reply from 212.58.241.131: bytes=32 time=314ms TTL=243
Reply from 212.58.241.131: bytes=32 time=287ms TTL=243
Ping statistics for 212.58.241.131:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 227ms, Maximum = 346ms, Average = 293ms
C:\Users\X>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  1    *      23 ms  139 ms  dsldevice.lan [192.168.1.254]
  2  220 ms    53 ms    19 ms  lo0-central10.pcl-ag08.plus.net [195.166.128.189]
  3  186 ms    22 ms    18 ms  link1-central10.pcl-gw01.plus.net [84.93.249.224]
  4  363 ms  235 ms  292 ms  xe-2-2-0.pcl-cr01.plus.net [212.159.1.12]
  5  322 ms  282 ms  430 ms  ae2.pcl-cr02.plus.net [195.166.129.7]
  6  231 ms  443 ms  225 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  7  307 ms  434 ms  428 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  8  285 ms  419 ms  271 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  9    *        *        *    Request timed out.
10  264 ms  300 ms  499 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
11  414 ms  267 ms  192 ms  132.185.255.60
12  190 ms  198 ms  322 ms  virtual-vip.thdo.bbc.co.uk [212.58.241.131]
Trace complete.

[#2]

Anotherone - thanks - did that and now on  ptn-ag01 and back to normal speed. Much appreciated.

[#3]

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping bbc.co.uk
Pinging bbc.co.uk [212.58.241.131] with 32 bytes of data:
Reply from 212.58.241.131: bytes=32 time=18ms TTL=246
Reply from 212.58.241.131: bytes=32 time=18ms TTL=246
Reply from 212.58.241.131: bytes=32 time=17ms TTL=246
Reply from 212.58.241.131: bytes=32 time=17ms TTL=246
Ping statistics for 212.58.241.131:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 17ms, Maximum = 18ms, Average = 17ms
C:\Windows\system32>tracert bbc.co.uk
Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
 1    46 ms    98 ms    98 ms  dsldevice.lan [192.168.1.254]
 2    20 ms    18 ms    19 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
 3    19 ms    18 ms    17 ms  link10-central10.ptw-gw02.plus.net [84.93.248.82
]
 4    17 ms    17 ms    18 ms  xe-7-2-0.ptw-cr02.plus.net [212.159.1.22]
 5    17 ms    17 ms    17 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
 6    17 ms    16 ms    17 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
 7     *        *        *     Request timed out.
 8    64 ms    18 ms    18 ms  ae1.er01.rbsov.bbc.co.uk [132.185.254.46]
 9    22 ms    17 ms    22 ms  132.185.255.60
10    17 ms    18 ms    17 ms  virtual-vip.thdo.bbc.co.uk [212.58.241.131]
Trace complete.
Only Usenet affected here

[#4]

Hi guys,
I am new to Plusnet. Just got mine activated today.
Wow, isn't this a throwback to Entanet-esque shenanigans? I didn't think i'd see the day.
Anyway, I am on gateway pcl-ag06. Ping times and speeds are normal. I WAS on pcl-ag07 and it was absolutely dire (200ms pings, 3mb speeds)
I reckon what has happened is Plusnet have probably got an influx of new customers and it's hammering their systems.

[#5]

Sorry, didn't realise a reboot was different to a disconnect, I used the reboot the other night too..  
I just hopped briefly onto pcl-ag07 and it was atrocious:

So hopped again onto ptn-ag03 and it's slightly better, although a long way from my 70mb down, 9ms ping.

[#6]

Even ADSL was 10x faster lol

[#7]

@MrRichThomas
As you are on Fibre it's not so critical with the router, but it could be disastrous for an ADSL user depending on their connection.
But those speeds are really bad. Try another Gateway hop. Also run http://speedtest.btwholesale.com/ ignore the red pre-amble except make sure nothing else is using the Internet, after the first test Click Further Diagnostics, enter your phone number and run the test.Copy and paste the result.

[#8]

gateway pcl-ag04seems to be stable for the moment but with the traffic elevation plusnet made to my line does not seem to have made any difference during peak time .

[#9]

I jumped from pcl-ag01 where I was getting 1-2mbps to pcl-ag05 and now getting 67-70mbps.  Slightly slower than normal 80mbps but much better.

[#10]

I just got in and checked the graphs and spotted this:
http://www.thinkbroadband.com/ping/share/660bb73c13549817d7f965387a399f8e.html
Looks like we've had something push that same device again into failure.  Just called someone to sort it.  This would have affected anyone on pcl-ag08, pcl-ag07.

[#11]

Pcl-ag08 that would explain the high ping of 183ms then.

[#12]

Quote from: Kelly

I just got in and checked the graphs and spotted this: http://www.thinkbroadband.com/ping/share/660bb73c13549817d7f965387a399f8e.html Looks like we've had something push that same device again into failure.  Just called someone to sort it.   This would have affected anyone on pcl-ag08, pcl-ag07.

It wasn't me guv honest  (at least for pcl-ag08  ) but I do wonder what happened at 4:30 this afternoon to kick this all off?

[#13]

Been gaming all night then logged of to watch some YOUTUBE.  Videos start buffering so had to knock it down to 480p
Gateway is ptn-ag03.

Download speeds are fine, but I usually have a ping of 30 and 0-1 jitter.

[#14]

20CN,  'pcl-ag07'

[#15]

Yep.  That is http://community.plus.net/forum/index.php/topic,111170.msg966068.html#msg966068