Peak time latency spikes

[#1]

This doesn't look too clever
You are using a debugging mode - and checking IP 87.114.xxx.xxx
Array
(
   [0] =>  1  84.92.0.73 (84.92.0.73)  0.360 ms
   [1] =>  2  po3.3659.peh-cr02.plus.net (84.93.232.38)  0.430 ms
   [2] =>  3  84-93-232-60 (84.93.232.60)  9.562 ms
   [3] =>  4  ae3.ptw-cr01.plus.net (195.166.129.32)  7.712 ms
   [4] =>  5  ae1.pcl-cr01.plus.net (195.166.129.1)  7.593 ms
   [5] =>  6  55.core.plus.net (212.159.1.55)  8.180 ms
   [6] =>  7  link4-central10.pcl-ag04.plus.net (84.93.249.103)      888.795 ms
   [7] =>  8  *
   [8] =>  9  *
   [9] => 10  *
   [10] => 11  *
)
You are currently connected to gateway pcl-ag04.
hop2 from 3 separate runs
Tracing route to link4-central10.pcl-ag04.plus.net [84.93.249.103]
over a maximum of 30 hops:
 2   140 ms   120 ms    40 ms  link4-central10.pcl-ag04.plus.net [84.93.249.103]
 2    51 ms   598 ms   225 ms  link4-central10.pcl-ag04.plus.net [84.93.249.103]
 2   650 ms    90 ms   126 ms  link4-central10.pcl-ag04.plus.net [84.93.249.103]

[#2]

Are you seen performance problems.  We know that PCL-AG04 will be responding erratically to pings at minute.  We've got a case raised on it with the vendor, but it shouldn't be affecting traffic routing, only it's ability to respond to ping style requests.

[#3]

Quote from: Kelly

We know that PCL-AG04 will be responding erratically to pings at minute.

I noticed this post and I was getting packet loss on AG04 so I hopped, ended up on AG01 and I'm getting packet loss there too 

[#4]

How much packet loss?  How are you seeing it?

[#5]

With pathping...

C:\WINDOWS\system32>pathping bbc.co.uk
Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
  0  Finguz-PC.lan [192.168.1.64]
  1  192.168.1.254
  2  lo0-central10.pcl-ag01.plus.net [195.166.128.182]
  3  link6-central10.pcl-gw02.plus.net [84.93.249.10]
  4  xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
  5  ae1.ptw-cr02.plus.net [195.166.129.2]
  6  ae2.ptw-cr01.plus.net [195.166.129.4]
  7  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Finguz-PC.lan [192.168.1.64]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2  102ms     2/ 100 =  2%     2/ 100 =  2%  lo0-central10.pcl-ag01.plus.net [1
95.166.128.182]
                                0/ 100 =  0%   |
  3   27ms     2/ 100 =  2%     2/ 100 =  2%  link6-central10.pcl-gw02.plus.net
[84.93.249.10]
                                0/ 100 =  0%   |
  4   24ms     2/ 100 =  2%     2/ 100 =  2%  xe-0-2-0.pcl-cr02.plus.net [212.15
9.1.2]
                                0/ 100 =  0%   |
  5   25ms     1/ 100 =  1%     1/ 100 =  1%  ae1.ptw-cr02.plus.net [195.166.129
.2]
                                0/ 100 =  0%   |
  6   25ms     0/ 100 =  0%     0/ 100 =  0%  ae2.ptw-cr01.plus.net [195.166.129
.4]
                                2/ 100 =  2%   |
  7   23ms     2/ 100 =  2%     0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58
.239.6]
Trace complete.

Download speed is also half of linespeed, with a slight bump in latency.

[#6]

Speed deteriorating and latency increasing, same as last night and the night before..

Normally download @ 61.** and ping around 22ms
Still seeing same packet loss too..

C:\WINDOWS\system32>pathping bbc.co.uk
Tracing route to bbc.co.uk [212.58.253.67]
over a maximum of 30 hops:
  0  Finguz-PC.lan [192.168.1.64]
  1  192.168.1.254
  2  lo0-central10.pcl-ag01.plus.net [195.166.128.182]
  3  link6-central10.pcl-gw02.plus.net [84.93.249.10]
  4  xe-0-2-0.pcl-cr02.plus.net [212.159.1.2]
  5  ae1.ptw-cr02.plus.net [195.166.129.2]
  6  ae2.ptw-cr01.plus.net [195.166.129.4]
  7  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Finguz-PC.lan [192.168.1.64]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                0/ 100 =  0%   |
  2   36ms     3/ 100 =  3%     3/ 100 =  3%  lo0-central10.pcl-ag01.plus.net [1
95.166.128.182]
                                0/ 100 =  0%   |
  3   28ms     0/ 100 =  0%     0/ 100 =  0%  link6-central10.pcl-gw02.plus.net
[84.93.249.10]
                                2/ 100 =  2%   |
  4   24ms     2/ 100 =  2%     0/ 100 =  0%  xe-0-2-0.pcl-cr02.plus.net [212.15
9.1.2]
                                2/ 100 =  2%   |
  5   25ms     4/ 100 =  4%     0/ 100 =  0%  ae1.ptw-cr02.plus.net [195.166.129
.2]
                                0/ 100 =  0%   |
  6   25ms     4/ 100 =  4%     0/ 100 =  0%  ae2.ptw-cr01.plus.net [195.166.129
.4]
                                1/ 100 =  1%   |
  7   23ms     5/ 100 =  5%     0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58
.239.6]
Trace complete.

[#7]

Getting worse every day now

[#8]

Here is mine.
Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
 0  
 1  192.168.2.1
 2  lo0-central10.ptn-ag04.plus.net [195.166.128.193]
 3  link7-central10.ptn-gw01.plus.net [84.93.248.236]
 4  xe-10-1-0.ptw-cr01.plus.net [212.159.1.44]
 5  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
 6     *        *        *
Computing statistics for 125 seconds...
           Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
 0                                          
                                            0/ 100 =  0%   |
1    0ms     0/ 100 =  0%      0/ 100 =  0%  192.168.2.1
                                            0/ 100 =  0%   |
2  ---     100/ 100 =100%    100/ 100 =100%  lo0-central10.ptn-ag04.plus.net [195.166.128.193]
                                            0/ 100 =  0%   |
3   13ms     0/ 100 =  0%     0/ 100 =  0%  link7-central10.ptn-gw01.plus.net[84.93.248.236]
                                            0/ 100 =  0%   |
4   14ms     0/ 100 =  0%     0/ 100 =  0%  xe-10-1-0.ptw-cr01.plus.net [212.159.1.44]
                                           100/ 100 =100%   |
5  ---     100/ 100 =100%     0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58
.239.6]
Trace complete.

[#9]

This is on ag02...
Packet loss too..

Tracing route to bbc.co.uk [212.58.251.195]
over a maximum of 30 hops:
  0  Finguz-PC.lan [192.168.1.65]
  1  192.168.1.254
  2  lo0-central10.pcl-ag02.plus.net [195.166.128.183]
  3  link2-central10.pcl-gw02.plus.net [84.93.249.34]
  4  50.core.plus.net [212.159.1.50]
  5  ae1.ptw-cr02.plus.net [195.166.129.2]
  6  ae2.ptw-cr01.plus.net [195.166.129.4]
  7  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  8     *        *        *
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           Finguz-PC.lan [192.168.1.65]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.254
                                1/ 100 =  1%   |
  2   28ms     2/ 100 =  2%     1/ 100 =  1%  lo0-central10.pcl-ag02.plus.net [1
95.166.128.183]
                                0/ 100 =  0%   |
  3   29ms     1/ 100 =  1%     0/ 100 =  0%  link2-central10.pcl-gw02.plus.net
[84.93.249.34]
                                2/ 100 =  2%   |
  4   25ms     3/ 100 =  3%     0/ 100 =  0%  50.core.plus.net [212.159.1.50]
                                0/ 100 =  0%   |
  5   24ms     5/ 100 =  5%     2/ 100 =  2%  ae1.ptw-cr02.plus.net [195.166.129
.2]
                                0/ 100 =  0%   |
  6   25ms     3/ 100 =  3%     0/ 100 =  0%  ae2.ptw-cr01.plus.net [195.166.129
.4]
                                0/ 100 =  0%   |
  7   22ms     3/ 100 =  3%     0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58
.239.6]
Trace complete.

Not wanting to be a whiner, but this is becoming extremely tedious.
I've had pet rabbits that hopped less than this  

[#10]

Ok.
Just fyi, Dave T will be collecting some more data tonight.

[#11]

KELLY I have ask numbers of times can you please check my ticket I want a reply today please on my ticket

[#12]

Let me/us know if there's anything I/we can do to help expedite a fix a for this.

[#13]

I just migrated to plusnet yesterday and speed was fine last night not sure which gateway i was on, but tonight, speed dropped big time and high ping so i disconnected and reconnected router and all is well ptn-ag03 gateway atm, hope PN sort the gateway soon.

[#14]

You made a mistake joining PN Mate

[#15]

Is anyone on a PTW-XXX gateway getting issues or is it just PCL-XXX gateways tonight?