ISP Throttling and IPTV: Is It Your Provider or the Server?
·7 min read

If IPTV only buffers in the evening, the cause is in one of two places: on your broadband provider's network or on the stream server. Many people call this ISP throttling, but deliberate slowing is only one possibility and usually not the most likely one; plain congestion produces the same symptoms. The way to tell them apart is to repeat the same measurements over a few evenings, and this guide sets out that routine along with DNS and IPv6 checks.
Throttling or congestion?
Under the UK's open internet rules, which Ofcom enforces, broadband providers may not single out lawful traffic to slow it down, apart from narrowly defined traffic management that they have to be transparent about. EU rules (Regulation 2015/2120) say the same for EU countries. Congestion is different: nobody is targeting your stream, there is simply more traffic than capacity on one of the links between you and the server. Ofcom's own broadband performance reports measure the 8pm to 10pm window separately for exactly this reason: it is when lines are busiest.
Where evening slowdowns come from
Data between your home and a stream server passes through several links: your router, the provider's local network, the points where the provider connects to other networks, and the data centre hosting the server. In the evening peak any of these can fill up. If the provider's links towards the server's network are full, a speed test can look fine while the stream stutters.
That is because speed test apps pick the nearest server by default, and it often sits inside your provider's own network. What gets measured is the path from your home to your provider's front door, not the path to the stream server. Two UK providers can reach the same server by different routes, which is why one household can stream smoothly while the next one stutters.
A three-evening measuring routine
- 01Take your home network out of the pictureDuring the test, connect the TV or box by cable and pause heavy use at home such as large downloads and cloud backups. A Wi-Fi hiccup looks just like a provider problem.
- 02Test in the afternoon and in the eveningRun a speed test around 3pm and again around 9pm. Each time, test once with the default server and once with a server you pick manually in another country, ideally near where the stream server is hosted.
- 03Log each stutter with the timeOver three evenings, write down which channel stuttered and when. Try several channels and something from the on-demand library at the same moment.
- 04Switch to mobile data when it stuttersWhen the stream freezes, turn your phone into a hotspot and connect the TV to it. If the same channel plays smoothly on mobile data, the problem is on the path from your broadband line to the server. If it stutters there too, look at the server side.
- 05Send the results to supportShare your notes with IPTV support and, if needed, with your broadband provider. "At 9.10pm the foreign server test drops to half the afternoon figure, mobile data is fine" shows where the fault is in a single message.
| What you see | Most likely |
|---|---|
| Evening test to a foreign server drops, nearby server fine | Congestion on the provider's external links or the route |
| Everything slow in the evening, nearby server too | Congestion in the provider's local network |
| Speeds fine, only some channels stutter | Stream server or that channel's source |
| Smooth on mobile data, stutters on broadband | The path between your line and the server |
| Stutters on mobile data too | Server side; contact support |
What changing DNS does and does not do
DNS turns a server name into an IP address. If your provider's DNS answers slowly, channels take longer to start, and some content delivery networks pick a server for you based on the DNS answer. Switching the router or device to a public resolver such as 1.1.1.1, 8.8.8.8 or 9.9.9.9 can help with both. What DNS cannot change is the capacity of the path the data flows over: if the stutter comes from evening congestion, a DNS change will not fix it.
Check the IPv6 side
If your line has IPv6, a device may connect to a server over IPv6 rather than IPv4, and the two can take different routes. Some players are slow to fall back to IPv4 when an IPv6 connection fails, which adds a few seconds to every channel start. As a test, turn IPv6 off in the router or the device's network settings for one evening and repeat the measurements. If nothing changes, switch it back on.
A stream that runs smoothly over a VPN does not prove that your provider is slowing it on purpose. A VPN sends traffic along a different route, and the improvement usually points to congestion on the normal route. That is still useful information for support.
If your evening speeds are consistently far below what you were sold, that is a matter for your broadband provider. Providers that signed Ofcom's voluntary broadband speeds code of practice have to give you a minimum guaranteed speed and a way to leave without penalty if they cannot fix a persistent shortfall.



