Is Your ISP Throttling IPTV, or Is It Just Congestion?
The difference between deliberate traffic management and ordinary peak congestion in Canada, how to tell which you have, and what the regulatory position actually is.
Almost everything reported as throttling in Canada is congestion on shared infrastructure. They look identical from the sofa and they need completely different responses.
Guides · 2026-09-09 · 6 min read
Two different things that feel the same
Throttling is a provider deliberately limiting a category of traffic. Congestion is too many households sharing a segment of infrastructure at the same time. From your sofa they are indistinguishable: the stream degrades in the evening and recovers overnight.
The reason to separate them is that one has a remedy and the other does not. Congestion is fixed by changing technology or provider; throttling would be a regulatory matter. Getting the diagnosis wrong means either complaining fruitlessly or switching providers for nothing.
The Canadian regulatory position
Canada has net neutrality provisions in the Telecommunications Act, and the CRTC's internet traffic management framework requires that any traffic management be disclosed and not unjustly discriminatory. The regulator has ruled against providers on this before.
That does not make throttling impossible, but it does make blanket throttling of a whole traffic category unlikely as a business practice here, and it means a provider doing it is expected to disclose it. Check your provider's traffic management disclosure before assuming — it is a published document.
How to tell them apart
The distinguishing test is whether other traffic degrades alongside your stream. Congestion slows everything on the segment: downloads, web pages, video calls, game latency. Throttling of a specific category would slow that category while everything else stays fast.
- Run a large download at the same time your stream is struggling. If it is also slow, that is congestion.
- Check whether the degradation happens at a consistent clock time. Congestion follows human schedules almost exactly.
- Test on a neighbour's connection with a different provider at the same moment, if you can. Same slowdown on a different network means the problem is not your provider.
- Test with a VPN for one evening only. If the VPN makes no difference, traffic-type management is not the cause — but expect it to be slower overall.
What congestion actually looks like in Canada
Cable is shared at the neighbourhood level: everyone on your node draws from the same capacity. That is why cable connections slow together between roughly 7pm and 11pm while fibre generally does not, and it is the single most common explanation for evening streaming problems in this country.
Fixed wireless is shared at the tower and additionally affected by weather. DSL is not shared in the same way but has much less headroom to begin with. Fibre is the only common Canadian technology where evening throughput closely resembles daytime throughput.
What to do about it
If it is congestion — and it usually is — the effective responses are moving to fibre where it is available, moving the viewing device to Ethernet to remove the one part of the chain you fully control, and being realistic about what a shared connection delivers at peak.
If you have genuinely ruled out congestion and your provider's traffic management disclosure does not explain what you are seeing, that is worth raising with the provider directly and, failing that, with the CCTS.
Questions
Will switching ISPs fix it?
Only if it changes the underlying technology. Moving from cable to fibre makes a real difference. Moving between two providers who resell the same last mile usually changes the bill and nothing else.
Does using a VPN prove throttling?
It is suggestive, not conclusive — a VPN changes your route as well as hiding your traffic, so an improvement could be either. Treat it as one data point alongside the congestion tests rather than as proof.