Packet loss...

[#1]

Packet loss seems to be through the roof again. Not sure if it's Openreach or Plusnet's side of things:

WinMTR Statistics

Host	%	Sent	Recv	Best	Avrg	Wrst	Last
192.168.0.1	0	99	99	2	6	34	4
No response from host	100	20	0	0	0	0	0
No response from host	100	20	0	0	0	0	0
be3-3106.psb-ir02.plus.net	0	99	99	14	25	46	21
195.99.125.138	15	63	54	13	26	38	26
peer1-et-10-1-0.telehouse.ukcore.bt.net	15	63	54	15	31	42	31
195.99.126.105	15	63	54	15	27	49	20
216.239.48.143	15	63	54	18	32	43	36
209.85.241.169	12	67	59	17	30	43	36
lhr26s05-in-f14.1e100.net	0	99	99	17	26	45	30

[#2]

Different story from here, but routing is different as well.

>pathping lhr26s05-in-f14.1e100.net

Tracing route to lhr26s05-in-f14.1e100.net [216.58.214.14] over a maximum of 30 hops:
0 AriesPC.my.home [192.168.1.27]
1 home.gateway.my.home [192.168.1.254]
2 lo0.16.Central16.pcl-bng01.plus.net [195.166.130.211]
3 irb.16.pcl-cr02.plus.net [84.93.249.178]
4 ae1.ptw-cr02.plus.net [195.166.129.2]
5 ae2.ptw-cr01.plus.net [195.166.129.4]
6 72.14.222.97
7 216.239.48.77
8 209.85.241.169
9 lhr26s05-in-f14.1e100.net [216.58.214.14]

Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 AriesPC.my.home [192.168.1.27]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% home.gateway.my.home [192.168.1.254]
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% lo0.16.Central16.pcl-bng01.plus.net [195.166.130.211]
0/ 100 = 0% |
3 21ms 0/ 100 = 0% 0/ 100 = 0% irb.16.pcl-cr02.plus.net [84.93.249.178]
0/ 100 = 0% |
4 21ms 0/ 100 = 0% 0/ 100 = 0% ae1.ptw-cr02.plus.net [195.166.129.2]
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% ae2.ptw-cr01.plus.net [195.166.129.4]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% 72.14.222.97
0/ 100 = 0% |
7 21ms 0/ 100 = 0% 0/ 100 = 0% 216.239.48.77
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 209.85.241.169
0/ 100 = 0% |
9 20ms 0/ 100 = 0% 0/ 100 = 0% lhr26s05-in-f14.1e100.net [216.58.214.14]

Trace complete.

Where the 100% packet loss appears is almost certainly because those devices do not respond to pings.

[#3]

Looks like something wrong around Sheffield.