Fed up with ping times from Hell

[#1]

Seriously,
This is now just getting beyond stupid.
Every day I always seem to encounter issue with high pings. I've posted on forums and bought it up with support however never had any real resolve to the problem.
Like right now, 11:56pm

Pinging bbc.co.uk [212.58.251.195] with 32 bytes of data:
Reply from 212.58.251.195: bytes=32 time=63ms TTL=118
Reply from 212.58.251.195: bytes=32 time=55ms TTL=118
Reply from 212.58.251.195: bytes=32 time=245ms TTL=118
Reply from 212.58.251.195: bytes=32 time=988ms TTL=118
Reply from 212.58.251.195: bytes=32 time=1156ms TTL=118
Reply from 212.58.251.195: bytes=32 time=1221ms TTL=118
Reply from 212.58.251.195: bytes=32 time=1229ms TTL=118
Request timed out.
Reply from 212.58.251.195: bytes=32 time=855ms TTL=118
Reply from 212.58.251.195: bytes=32 time=883ms TTL=118
Reply from 212.58.251.195: bytes=32 time=910ms TTL=118
Reply from 212.58.251.195: bytes=32 time=958ms TTL=118
Reply from 212.58.251.195: bytes=32 time=1006ms TTL=118
Reply from 212.58.251.195: bytes=32 time=999ms TTL=118
Reply from 212.58.251.195: bytes=32 time=770ms TTL=118
Reply from 212.58.251.195: bytes=32 time=853ms TTL=118
Reply from 212.58.251.195: bytes=32 time=282ms TTL=118
Reply from 212.58.251.195: bytes=32 time=506ms TTL=118
Reply from 212.58.251.195: bytes=32 time=531ms TTL=118
Reply from 212.58.251.195: bytes=32 time=585ms TTL=118
Reply from 212.58.251.195: bytes=32 time=695ms TTL=118
Reply from 212.58.251.195: bytes=32 time=735ms TTL=118

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2   824 ms   249 ms   246 ms  lo0-central10.pcl-ag05.plus.net [195.166.128.186
]
  3    21 ms    21 ms    21 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.17
8]
  4    20 ms    20 ms    21 ms  xe-1-2-0.pcl-cr02.plus.net [212.159.0.210]
  5    38 ms    21 ms    22 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    21 ms    21 ms    21 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  7    21 ms    21 ms    21 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10   942 ms  1014 ms  1015 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 11   793 ms   683 ms   707 ms  132.185.255.140
 12   929 ms   953 ms   979 ms  212.58.251.195

I am seriously getting frustrated here. As it appears to be your "AG" routes that are currently overloaded
Update:
I rebooted my router, different route. This time AG02

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2   960 ms   968 ms   993 ms  lo0-central10.ptw-ag02.plus.net [195.166.128.196
]
  3     *      623 ms   672 ms  link-a-central10.ptw-gw01.plus.net [212.159.2.14
8]
  4   695 ms   572 ms   394 ms  xe-0-2-0.ptw-cr01.plus.net [212.159.0.248]
  5   368 ms   405 ms   488 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]

Upstream	444
Downstream	9703
SNR Margin(Upstream)	29.3
SNR Margin(Downstream)	2.2
Line Attenuation(Upstream)	21.2
Line Attenuation(Downstream)	34.5

This is intermittent, sometimes hours can go by and the net is fantastic.. however like now when I am trying to use the Internet at non-peak time.. its hell.
Why plus? Why.

[#2]

Are the errors on your line increasing during these slow ping events? I ask because errors could cause slow ping responses due to retransmissions.

[#3]

Thanks for the reply,
I receive no Errors or Drops on both Upload and Download during the PING spikes.

[#4]

I get pretty much the same... lag spikes and high pings, so I don't think it is a problem with your line

[#5]

I don't think line errors would cause slow ping response times, CRC errors would cause packet loss, but I don't think there's anything to retransmit the ICMP ping packets. Unless "G.998.4 Universal retransmission" (G.INP) is in use, and I doubt it is on ADSL.
Also, all the gateways have ag in their names - pcl-ag04 is not the same as ptn-ag04.

[#6]

Hi Yaroze, is there any chance you could set up a thinkbroadband ping meter, as syates has in their signature at all? That'd give us more of an idea of when and how often it happens, should give us something to look into. You can set one up on their site here: http://www.thinkbroadband.com/ping

[#7]

Matt, Is Yaroze on a static IP? If not the ping monitor is going to be a pain.

[#8]

Thank for the replys.
However I am on dynamic not static but I've setup a graph for my current IP.
Edit: Updated graph with new static iP

[#9]

Thanks for that, I've added you a static IP anyway so you'll only need to update the monitor once more when you next disconnect/reconnect. Thanks for that, we'll check on it after the weekend and see when it's been bad and if there's anything we can do for you.

[#10]

Thanks Matt,
I've updated the graph in my previous post to reflect the new static IP.
However traceroutes are now failing to display the whole route.

traceroute to google.com (212.56.71.219), 30 hops max, 60 byte packets
 1  home.gateway.home.gateway (192.168.1.254)  0.753 ms  1.060 ms  1.311 ms
 2  lo0-central10.pcl-ag08.plus.net (195.166.128.189)  22.553 ms  23.436 ms  25.664 ms
 3  link-b-central10.pcl-gw02.plus.net (212.159.2.190)  27.345 ms  29.827 ms  31.006 ms
 4  xe-9-1-0.pcl-cr02.plus.net (212.159.0.222)  32.823 ms  35.061 ms  36.411 ms
 5  ae2.pcl-cr01.plus.net (195.166.129.6)  38.919 ms  40.191 ms  42.604 ms
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

traceroute to bbc.co.uk (212.58.253.67), 30 hops max, 60 byte packets
 1  home.gateway.home.gateway (192.168.1.254)  0.654 ms  0.923 ms  1.208 ms
 2  lo0-central10.pcl-ag08.plus.net (195.166.128.189)  35.054 ms  36.093 ms  36.303 ms
 3  link-b-central10.pcl-gw02.plus.net (212.159.2.190)  27.175 ms  29.555 ms  31.024 ms
 4  xe-9-1-0.pcl-cr02.plus.net (212.159.0.222)  102.054 ms  102.291 ms  102.896 ms
 5  ae2.pcl-cr01.plus.net (195.166.129.6)  38.936 ms  41.370 ms  42.578 ms
 6  ae1.ptw-cr01.plus.net (195.166.129.0)  44.852 ms  38.037 ms  40.247 ms
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Is this normal?

[#11]

Hmm. No, I'd guess not - can you still view the bbc website though? Hopefully it's not interfering with http traffic.

[#12]

BBC Website is working as it should. As are many others.
dick:quote

[#13]

Certainly doesn't look normal to me - here is my tracert

Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:
  1    51 ms     1 ms     4 ms  192.168.1.1
  2    13 ms     9 ms     8 ms  lo0-central10.pcl-ag04.plus.net [195.166.128.185
]
  3     8 ms     8 ms     8 ms  link-a-central10.pcl-gw01.plus.net [212.159.2.17
2]
  4    11 ms    11 ms    31 ms  xe-0-2-0.pcl-cr01.plus.net [212.159.0.204]
  5     8 ms    10 ms     8 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6     8 ms     8 ms    68 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7     *        *        *     Request timed out.
  8    12 ms    11 ms     9 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
  9     9 ms     9 ms    11 ms  132.185.255.156
 10    10 ms     9 ms    10 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.

[#14]

Which kind of devices do you have on your network?
Are you running the pings/traceroutes wired or wirelessly?

[#15]

Traceroutes are all wired as are the PING tests.
My PC (running Linux), Nexus 5 and  my router are the only devices on my network. All connected via wire (apart from my Phone)
dick:quote