Plusnet package loss

GeX · 29 May 2017 at 11:33

edit: Yes, I did mean packet loss - not package!

I'd noticed that my connection is a bit.. I hate using the term 'laggy' but it is. DNS requests take time to be serviced, I see terminal lag via ssh/mosh. Throughput on downloads seems 'ok' once they've established. I wrote it off as it being just not as fast my old hyperoptic connection, but it's been bugging me more recently.

I ran mtr to see what is going on

Code:

                                                                    Packets               Pings
 Host                                                             Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. dsldevice.lan                                                  0.0%   778    1.4   1.5   1.4   4.5   0.2
 2. ???
 3. 133.hiper04.sheff.dial.plus.net.uk                            85.1%   778   10.5  10.9  10.2  13.7   0.3
 4. be3-3102.pcn-ir02.plus.net                                     0.0%   778   12.1  12.6  11.1 114.4   8.3
 5. 195.99.125.140                                                 0.0%   778   11.2  11.1  10.5  18.4   0.4
 6. peer1-hu0-19-0-2.slough.ukcore.bt.net                          0.0%   778   13.2  12.9  12.5  15.6   0.1
 7. peer5-te0-0-0-32.telehouse.ukcore.bt.net                       0.0%   778   12.9  13.0  12.2  59.7   2.7
 8. 108.170.246.193                                                0.0%   778   12.0  12.2  11.8  18.8   0.3
 9. 108.170.233.197                                                0.0%   777   11.8  11.9  11.6  14.0   0.1
10. lhr35s01-in-f14.1e100.net                                      0.0%   777   12.3  12.3  12.0  14.8   0.1

133.hiper04.sheff.dial.plus.net.uk is the problem then, firmly within Plusnet's systems.

I tried rebooting my modem to see if it'd give me a better route, but it hit the same hop.

I found a thread on Plusnet's forum https://community.plus.net/t5/Fibre-Broadband/DNS-Routing-issues-for-the-last-36-hours/td-p/1348275 from last year, people having similar issues. Some saying that if you have an IP in the 51.x range then this happens.

My IP is in that range, but I don't want to sit here hitting reboot until I get a more useful route.

Has anyone else here had similar issues, and knows how to sort this out?

Caged · 29 May 2017 at 13:01

You're reading a traceroute incorrectly. The fact you have zero packet loss to your target shows that there isn't a packet loss issue - the third hop just doesn't care about dealing with ICMP in a timely fashion.

GeX · 29 May 2017 at 13:51

I'm at a loss as to why I'm seeing lag (mosh underlines delayed input on an ssh terminal) on ssh connections then.

Caged · 29 May 2017 at 15:04

What's your latency/packet loss like to the server?

GeX · 29 May 2017 at 19:58

~30ms and 0% loss atm I'll have to try and catch it when it feels sluggish

bremen1874 · 29 May 2017 at 20:15

You've presumably tried changing your DNS servers?

GeX · 29 May 2017 at 20:43

No, because the problem isn't just on DNS - it's just the DNS request that makes the problem visible when browsing.

ChrisD. · 30 May 2017 at 09:54

What do you currently have as your DNS servers?

Have you tried another computer?

Steveocee · 4 Jun 2017 at 10:15

If the problem is visible when browsing and you aren't getting packet loss (which you have evidenced you aren't) try changing your DNS, ping a few public ones to find your fastest.

r7slayer · 4 Jun 2017 at 12:06

Plusnet did have issues on a certain rack last year in fact i think it was a couple not sure what the Ip range was though. Usually you have to drop your connection for 10 mins and reconnect to try and get a different rack or they can force it their end dropping your connection till it jumps on another rack.