Intermitant slow traffic.

[#1]

Hi everyone,

Just looking for some initial advice. I was having some wifi dropouts on my own router so went back to using the Plusnet supplied Hub One connected directly into the master socket. Fibre connection has mostly been stable and reliant. However since moving back to the Hub One, I am finding the connection very slow to the point that it's mostly unusable. Websites take 20+ seconds to load and often images dont appear. This is the same for any device on the network.

C:\Users\noz>tracert www.bbc.co.uk

Tracing route to uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.237.254]
over a maximum of 30 hops:

  1    18 ms   10 ms    26 ms  dsldevice.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *       20 ms  133.hiper04.sheff.dial.plus.net.uk [195.166.143.133]
  4  3733 ms  1917 ms   312 ms  132.hiper04.sheff.dial.plus.net.uk [195.166.143.132]
  5  1805 ms  1488 ms  2400 ms  peer2-et-0-0-4.slough.ukcore.bt.net [109.159.252.118]
  6  3023 ms   701 ms   147 ms  195.99.126.225
  7    27 ms    16 ms    14 ms  ae3.cr02.thdow.bbc.co.uk [132.185.249.12]
  8    21 ms    12 ms    22 ms  ae1.cr02.rbsov.bbc.co.uk [132.185.254.13]
  9    12 ms    11 ms    11 ms  ae0.er02.telhc.bbc.co.uk [132.185.254.105]
 10    16 ms    18 ms    13 ms  132.185.255.148
 11    24 ms    12 ms    55 ms  212.58.238.5
 12  2846 ms  2929 ms   286 ms  212.58.237.254

Any suggestions as to what I should be looking at to resolve this? Plusenet services status says all is fine.

Thanks for any advice 🙂

noz

[#2]

Hi @wayyoung 

18 ms   10 ms    26 ms  dsldevice.lan [192.168.1.254]

I would expect the Hub One to respond quicker than shown above.

I see

Tracing route to www.bbc.co.uk.pri.bbc.co.uk [212.58.233.252]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.lan [192.168.1.254]
2 11 ms 9 ms 8 ms 252.core.plus.net [195.166.130.252]

Are you testing on a wireless device? 

Dan.

Edit:- my test is from a wireless laptop

[#3]

Further testing suggests the wifi router is having an issue. Directly from the Hub One it seems ok as you suggest -

Tracing route to uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.237.251]
over a maximum of 30 hops:

  1     4 ms     1 ms    82 ms  dsldevice.lan [192.168.1.254]
  2     6 ms     5 ms     6 ms  172.16.10.90

Thanks for the pointer 🙂

[#4]

5Ghz signals get weaker more than 2.4Ghz signals the further away from the router you go. You could try removing the sync of the two wireless channels to force your device to use 2.4Ghz.

Log into the Hub One by pointing a web browser to 192.168.1.254

From the home page navigate to Advanced Settings >Wireless (you will need the admin password)

Click on 5 GHz wireless tab

Change the Sync with 2.4 GHz to No

Append the current SSID name by adding -5.

This way you can select either signal.

HTH

Dan.

[#5]

Hi @wayyoung

I've just tested your line for good measure and the tests aren't showing any issues, but it looks like you've got to the bottom of the problem already. Let me know if you have any further issues. 

Also, long time no see 

[#6]

@Gandalf  Appreciate you checking that, thanks.

Nice to see you've made it through the last 2 years. Hope you're well 🙂

[#7]

I haven't made any changes at alll, but whatever was causing the issue is not there now.

Tracing route to uk.www.bbc.co.uk.pri.bbc.co.uk [212.58.237.254]
over a maximum of 30 hops:

  1     1 ms     1 ms     3 ms  dsldevice.lan [192.168.1.254]
  2     6 ms     5 ms     5 ms  172.16.10.90
  3     *        *        *     Request timed out.
  4    11 ms    11 ms    12 ms  132.hiper04.sheff.dial.plus.net.uk [195.166.143.132]
  5    10 ms    10 ms    10 ms  peer2-et-0-0-4.slough.ukcore.bt.net [109.159.252.118]
  6    21 ms    33 ms    13 ms  195.99.126.225
  7    12 ms    12 ms    11 ms  ae3.cr02.thdow.bbc.co.uk [132.185.249.12]
  8    12 ms    12 ms    12 ms  ae1.cr02.rbsov.bbc.co.uk [132.185.254.13]
  9    15 ms    14 ms    12 ms  ae0.er02.telhc.bbc.co.uk [132.185.254.105]
 10    13 ms    13 ms    18 ms  132.185.255.148
 11    13 ms    11 ms    13 ms  212.58.238.5
 12    11 ms    12 ms    12 ms  212.58.237.254

[#8]

No problem @wayyoung 

Aye I’m well, I hope you are too. 

Traceroute looking good, it’s a bit of a mystery but fingers crossed the issues don’t return.