Menu
Reply
  • 1
  • 0
  • 0
james6394
Joining in
102 Views
Message 1 of 3
Flag for a moderator

Superhub 2 needing to be constantly rebooted (High latency etc)

For a long time now, I've been experiencing issues with my internet connection. I phoned up support before and they said they would monitor it but they said they found no faults.

The issue is that there are random latency spikes, which happen more regularly if the Superhub has not been rebooted. It can normally last a day or two before it starts becoming extremely problematic. These latency spikes obviously affect gaming, and sometimes video steaming, in a major way. 

I have tried using multiple PC's with wired and wireless connections but the problem still persists. Before I reset the Superhub today it had been up for 5 days. I pinged the router continuously and the pings average was around 10ms but it was quite erratic. After rebooting the router, the ping is back to <=1ms.

Here is a snippet of the before and after reboot:

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=12ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=17ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=11ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64

Am I right in assuming the issue is simply the Superhub 2? If so is it possible to get a replacement?

Thanks,

James

 

0 Kudos
Reply
  • 10
  • 0
  • 1
kelvindh
Tuning in
67 Views
Message 2 of 3
Flag for a moderator

Re: Superhub 2 needing to be constantly rebooted (High latency etc)

Hi James,

I've had the same issue with my super hub 2 for a number of years. Below are my ping stats just now (from my laptap via a short ethernet cable into the hub, pinging 192.168.0.1). You can see it constantly creeps up over time and regularily spikes sometimes over 1 seconds. This all goes back to 1-2ms if I reboot the router. I've phoned support on a number of occassions who tell me to simply reboot. This looks like a software issue with the router. I've finally decided to pay £14 for an upgrade to the super hub 3 (hopefully won't have the same problem).

superhubping.JPG

0 Kudos
Reply
  • 3.88K
  • 120
  • 203
Forum Team (Retired) Adam_L
Forum Team (Retired)
37 Views
Message 3 of 3
Flag for a moderator

Re: Superhub 2 needing to be constantly rebooted (High latency etc)

Hi james6394, 

Thanks for posting! I am sorry to hear that your Super Hub needs to be rebooted constantly due to high latency, I apologise for any inconvenience caused.

I have tested things from here and I can see that 2 of your upstream power levels are too high and will require an engineer to attend and resolve this for you.

I will send you a PM (purple envelope at the top) detailing what's required to proceed with making the booking. Please respond to me there and I'll get this sorted for you.

Take care, 

Thanks, 

Adam.


Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply