06-06-2026 04:42 PM - edited 06-06-2026 04:55 PM
Hi,
I have been having trouble with my broadband for a little while, i thought it might be because i am using WIFI so had a electrician come out and fit ethernet cables to each room. I am still having issues, mainly with Youtube where it looks to be that my speeds are being throttled when it notices i'm streaming video from Youtube. I am paying for 900MBs but when i use the 'Stats for nerds' on Youtube to show my connection speeds it is around 3000kbps, which means it will only load 480p. If i turn on my VPN and essentially hide my traffic from EE my speeds immediately fly up to 500,000kbps+, this is very frustrating as i shouldn't need to run a VPN and the VPN is then causing connection errors on other websites making me refresh the page.
If this is not EE throttling what is causing this? I have tried resetting the BT fibre box, the EE modem, i have replaced the WIFI with ethernet, i have tried changing the DNS to both Google or Cloudfare to see if this fixes and nothing works.
EPDATE: I have just removed the ethernet and used WIFI and this is no longer happening on WIFI, is this something wrong with out the modem or my set up and the way its routing through a hardwired connection? Because it works fine with a VPN on wired
21-10-2026 07:38 PM
Has anyone else started having this issue again? I was having the problem, then it went away for months and now has returned. I’ve got a 1.6gb connection, WiFi is absolutely fine. We are now getting buffering again on YouTube, like it’s been throttled. Dodgy node again?
We are in the Midlands. I get over 1gb on WiFi to my phone and over 500mb on the Apple TV’s. All other streamings apps are fine.
21-10-2026 08:14 PM
@Gazwhereuat Surely a dodgy you tube stream then? You can try your hub off for a couple hours even overnight if you wish that may circumvent any dodgy node in the system.
21-10-2026 10:49 PM
Cheers for the reply. Sorry I meant Google Global Cache node not wifi node. Just wondered if others were experiencing the same thing, last time I was, others were too. Video quality keeps jumping from 4k down to 1080p.
21-10-2026 11:09 PM
@Gazwhereuat With you on that, but you are the first so far, and with all the FW updates going on for all the EE Hubs then nothing get's written off curently.
22-10-2026 11:09 AM
@SuarLFC EE Full Fibre 900 , EE Smart Hub 7 Pro , Wired Ethernet (EE supplied 10m Cat5e) Playback device Nvidia Shield 2017 , Pic 1 is a regular 4k\60FPS stream Pic 2 Is 4k Dolby vision stream definitely no traffic shaping there i got to be honest as far as full fibre goes ive not encountered traffic shaping in years , was something they used to do a lot in the old days & i think it is on certain mobile packages today but Home fibre Nahh , just wondering on that wired connection ?, do you have any kind of ad blocking DNS set up ?......if you do You tube will slow you right down if it detects an adblocker of any kind weather DNS based or not in fact i had to add you tube to my Adguard DNS exemptions as i was being slammed & i pay for Premium !! but they still slammed me regardless😂
4K60 (Shield 2017) EE FF 900 + EE Smart Hub 7 Pro (Wired)
4K60 Dolby Vision (Shield 2017) EE FF 900 + EE Smart Hub 7 Pro (Wired))
22-10-2026 12:05 PM
@Gazwhereuat - do you have a desktop/laptop you're able to replicate the problem on?
Previously, when similar issues have cropped up, people have been able to narrow it down to one or more cache locations. A couple of things that heped to do this: -
1. Check the stats overlay to see if it offers any clues, particularly in terms of speed etc. To access this, you play a video at your chosen quality and then right click the video and select the 'Stats for nerds' option: -
2. Open a browser inspector (CTRL, Shift and 'i' for Chrome), select the Network tab at the top of the overlay and load a Youtube video. Further down, right-click the colum headers and ensure 'Domain' is selected. Reload the page/play the video and look for domains in the list that look like the highlighted row below. They are an indicator of the cache you are hitting, and last time people were able to isolate it to one or two specific domains which helped get to the bottom of things: -