28-09-2026 02:55 PM
Hi I was moved to EE from Plusnet due to wanting to retain a landline.
I was supplied with a EE Smarthub Plus and have been experiencing periods on traffic issues where the latency beyond the LAN goes high >1000ms and packets start to be dropped.
I have tried a second Smart Hub Plus and am experiencing the same thing.
I suspect something is happening with in the hub itself rather than a change in the connection between the hub and the cabinet, as the lan itself stays stable under load but the traffic through the hub really struggles, it is making streaming services unusable at times.
is there any traffic shaping and QOS occurring in this hub? There is very little to configure on the hub setup pages themselves, are there options CS can enable/disable to help with traffic?
I simply didn’t have these issues on the Plusnet router/modem
Thanks
28-09-2026 03:11 PM - edited 28-09-2026 03:26 PM
@Chiliblue Have a look at the other posting and see if it works out similar with your reported issue. Reach out to @f00n and see where it stands currently, CH100 was the suspect on wifi causing problem. The FW is currently getting updated so this is were your hub is heading, you may wish to see were it is at currently.
FW: r5.19.1-R-2036010-PROD-83002 and the gui is at App version 3.17.5 17/09/2026
Lag spikes over 1000ms approximately every 38 seconds - The EE Community
28-09-2026 03:30 PM
Thanks Jim
Will have a look.
fyi
28-09-2026 03:32 PM
@Chiliblue Your posted picture has to be approved for general viewing so it may take time for it to appear to others.
28-09-2026 03:37 PM
in my setup this isn’t a WiFi issue as all the main elements affected are wired.
TV, Mediaserver, PS5.
It does effect the traffic on wifi but only as it passes through the hub it doesn’t affect the LAN traffic, wired or wireless. So this seems an adjacent issue.
28-09-2026 03:40 PM - edited 28-09-2026 03:46 PM
@Chiliblue Ok why not just run the ping test on your Lan connection, you will see it in that linked post. It's a 10 minute ping and only post your result's at the end off the test. To eliminate any wireless wifi connection issues, just turn the wifi off completely then Lan only you may need to reboot or wait for the EE Hub to disable and switch the wireless off.
28-09-2026 03:47 PM
Thanks for the headsup
it was just a screenshot of my router info page.
fw = r4.26.3-R-1923144-PROD-83002
28-09-2026 03:49 PM
@Chiliblue No problem, the FW is out and about, it's a waiting game until EE pushes it to your hub.
28-09-2026 04:27 PM
Hi Jim
--- 8.8.8.8 ping statistics ---
600 packets transmitted, 600 received, 0% packet loss, time 599931ms
rtt min/avg/max/mdev = 6.150/9.679/400.194/19.884 ms
this is a ‘good day’ result. Will do another when it all falls over again.
I have done a lot of pinging to try and resolve this, unfortunately it is also intermittent. Will be quite happy with a ping of 7ms when things are quiet but when downloading sizable data like a streaming service it goes high 1000ms or even 4000ms. Again not all the time but enough to be disruptive.
28-09-2026 04:38 PM - edited 28-09-2026 05:02 PM
@Chiliblue Is your wireless wifi on or off, when you run the test? Something is either hanging up the network and it can be Internal for you, so a process of elimination... There is no way to BQM any off the EE/BT hubs so you have no idea what it is doing. Everything has to be serviced and if your Lan is showing that just now it's not going to get any better, Let me run a ping for google like you have done and post, will do it wireless wifi that show's hangs and interupt's best.
Edit as below:-
C:\Windows\System32>ping -n 600 -4 google.com
Pinging google.com [142.250.140.113] with 32 bytes of data:
Reply from 142.250.140.113: bytes=32 time=34ms TTL=115
Ping statistics for 142.250.140.113:
Packets: Sent = 600, Received = 600, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 34ms, Average = 19ms
And a 1 minute one below this.
C:\Windows\System32>ping -n 60 8.8.8.8
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=18ms TTL=119
Ping statistics for 8.8.8.8:
Packets: Sent = 60, Received = 60, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 23ms, Average = 17ms
""rtt min/avg/max/mdev = 6.150/9.679/400.194/19.884 ms"" If this is a good day then boy do you have trouble big time....