Working Around Streaming Throttling

Routers VPN, DNS, Leaks
1

I thought I'd share a solution I found to getting around ISP throttling of video streaming services without needing to worry about your VPN being blocked by the streaming service. Using GL.iNet's selective VPN tunneling abilities, I've been able to isolate VPN tunneling so only the CDN/video data stream domains run through the VPN tunnel while other traffic to the streaming service, which appears to include the domains they use to verify you aren't using a VPN, still pass over your ISP IP address. This is particularly useful if you use an ISP which, for example, limits your video streaming bandwidth to 2.5Mbps (T-Mobile/Calyx, in my case).

Anyway, it's pretty simple on the GL.iNet VPN dashboard, all you need to do is create a VPN tunnel with the "Travelling From" section set to "All Client" and the "Travelling To" section set to your streaming service domains. I've been able to test Disney+/Hulu (they use the same CDN for video data), Peacock, Apple TV, and Youtube. Youtube doesn't block VPNs and I had better luck with a broader domain selection there for some reason. I tested this configuration on both a desktop in the web browser and on an iPad using the apps for the respective services with great success, so I wanted to share in case anyone is looking to do something similar.

You'll also notice that I included nflxvideo.net, which is Netflix's video data streaming domain. I don't subscribe to Netflix, so couldn't test whether or not the service works, but I included it since it may work, and I used it for testing on Fast.com (which is partially broken with this configuration, but still works enough for me to see that the ISP bandwidth throttling was successfully defeated).

Here's what the VPN configuration looks like in the GL.iNet user interface:

CleanShot 2025-05-27 at 22.25.44@2x
CleanShot 2025-05-27 at 22.25.44@2x2540×1556 320 KB

The domain list in the screenshot above is:

nflxvideo.net
cdn.peacocktv.com
media.dssott.com
tv.apple.com
youtube.com
googlevideo.com
ytimg.com

Anyway, I hope that is helpful. One thing that tripped me up a little bit at first is that you must disable any DoH/secure DNS features on your network's client devices that you wish to be impacted by this configuration. If their DNS queries aren't being processed by the router, the selective tunnel won't work.

1 Like
2

Hello!
Same issue still no fix to this.

Best Regards,
Pamela
www-dqfanfeedback.com

3

Hello,

@pie is shared use experience in this thread.

@Pamela329Lac What VPN issue did you encounter? Please share more info about the issue.

4

Make sure that you don’t have a DNS configuration set up on your PC/device that routes your DNS queries around your router. Many browsers by default now set up DoH (DNS over HTTPS) which causes this solution to fail.

5

Please feel free to review my list, I've added a bunch of popular streaming services to it. While it isn't fully exhaustive, it does have all of the popular ones in it.

Keep in mind that with this policy, you don't have to put subdomains in there. My list does include some, but it isn't required.

I did use Gemini to help me make the list, so you may need to review in case there are domains you don't want.

aiv-cdn.net
aiv-delivery.net
amazon.com
amazonvideo.com
atv-ps.amazon.com
bamgrid.com
cbsi.com
cbsi.live.ott.irdeto.com
cbsinteractive.hb.omtrdc.net
cbsistatic.com
cbsivideo.com
completion.amazon.com
crunchyroll.com
discomax.com
disney-plus.net
disney.cqloud.com
disneyplus.com
discoveryplus.com
dssedge.com
dssott.com
espn.api.edge.bamgrid.com
espn.connections.edge.bamgrid.com
espn.com
espncdn.com
espncricinfo.com
espn.net
hallmark.com
hallmarkchannel.com
hbo.com
hbogo.com
hbogoasia.com
hbomax.com
hbonow.com
hlsvod-l3c-clt1.media.plus.espn.com.c.footprint.net
hmnow.com
hulu.com
hulu.playback.edge.bamgrid.com
huluim.com
hulustream.com
itunes.apple.com
max.com
media-amazon.com
mgmplus.com
netflix.com
netflix.net
nflxext.com
nflximg.com
nflxso.net
nflxvideo.net
paramountplus.com
peacocktv.com
peacocktv.com.c.footprint.net
play.hbomax.com
pluto.tv
plutopreprod.tv
plutotv.net
pplusstatic.com
prime-video.amazon.dev
pv-cdn.net
redirect-cdn.espn.com
saa.cbsi.com
saa.paramountplus.com
search-api-disney.bamgrid.com
ssl-images-amazon.com
starz.com
tubi.io
tubi.tv
tv.apple.com
video.a2z.com
youtube.com
ytimg.com
akamaihd.net
akamaiedge.net
akamaized.net
availability-fastly.syncbak-mediastore-cedexis.cbsaavideo.com
cdn.google.com
cdn.peacocktv.com
cdn77.com
c.youtube.com
cloudfront.net
cloudflare.com
crunchyrollcdn.com
edgecastcdn.net
edgekey.net
edgesuite.net
fastly.net
footprint.net
googlevideo.com
llnwi.net
m.media-amazon.com
media.video-cdn.espn.com
nucdn.net
vod-fy.crunchyrollcdn.com
vod-gcs-cedexis.cbsaavideo.com
vod-gcs-qwilt.cbsaavideo.com
6

This list appears to be more geared toward directing all traffic to streaming services over your VPN, which is a valid goal depending on your use case. What I did with my list was slightly different, though. Using the list I put together, the streaming services' IP-checking still see your real IP address, but the bulk of the streaming video data goes over the VPN. That allows people who use an ISP that throttles streaming service bandwidth (e.g., "streaming at 480p resolution" but on a plan that otherwise is 100Mbps+ for general traffic) to get around their ISP throttle while not having to worry about sending all traffic through a VPN that may be blacklisted on the streaming service's end.

Note: I put all Youtube traffic over the VPN because Youtube doesn't block VPN IP addresses anyway.

7

Good point! I might go your route then as it makes more sense then having all the traffic go around!

1 Like
8

This is awesome. Thanks. Ill give it a try