Beating Bandwidth Throttling: When a VPN Stops It and When It Cannot
Does a VPN stop throttling? It depends on what triggers the slowdown
Most articles on this subject answer yes and move on. Whether it works depends on why the ISP is slowing you down, and there are only two kinds of reason.Bandwidth throttling is a deliberate reduction in connection speed by a network operator, triggered either by what the traffic is or by how much of it the customer has used. That one sentence is the whole decision tree. If the trigger is what the traffic is, say video, file sharing or a rival’s calling app, the ISP has to identify the traffic before it can slow it. An encrypted tunnel takes that ability away. If the trigger is how much you have used, the ISP does not need to know what anything is. It slows the whole line, tunnel included.
This page tests that rule against the record. Below are 14 cases where a regulator, a court or a measurement lab documented an ISP blocking or throttling traffic, with the mechanism and the source for each, and a verdict on whether a VPN would have changed the outcome. If you want the practical walkthrough instead, we keep that in a separate guide to dealing with ISP throttling in 2026.
Which ISPs have been caught throttling, and how?
Every row below rests on a primary document or on a measurement study with published methods. Allegations that were never tested are left out.| Year | ISP, country | What was slowed or blocked | Trigger | Would a VPN have helped? | Source |
|---|---|---|---|---|---|
| 2005 | Madison River, US | Ports used by a competing internet phone service, blocked outright. Settled with the FCC for $15,000. | Application | Yes | FCC consent decree DA 05-543 |
| 2007 to 2008 | Comcast, US | BitTorrent uploads, interrupted with forged reset packets. The FCC ordered it to stop in August 2008. A court vacated the order in April 2010 on jurisdiction, not on the facts. | Application | Yes | FCC order 08-183 |
| 2008 | Bell Canada | Peer to peer file sharing, slowed from 4:30 pm to 2 am, including on lines Bell wholesaled to rival ISPs. The regulator allowed it. | Application | Yes | CRTC Telecom Decision 2008-108 |
| 2011 to 2012 | Rogers, Canada | World of Warcraft, misclassified as peer to peer by the throttling system, which also slowed unidentified traffic on common peer to peer ports. Rogers ended traffic shaping in phases during 2012. | Application | Not reliably | CBC News; Globe and Mail |
| 2011 to 2014 | AT&T, US | All data on "unlimited" plans after a monthly threshold. More than 3.5 million customers affected. $60 million settlement in 2019. | Usage volume | No | FTC |
| 2013 to 2014 | Five large US ISPs | Anything arriving over congested links with transit carrier Cogent. Peak hour throughput on Comcast and Verizon fell below 0.5 Mbps by January 2014. | Congestion between networks | Sometimes | M-Lab interconnection study |
| 2014 to 2015 | T-Mobile and MetroPCS, US | Heavy users on "unlimited" plans, pushed to the back of the queue during congestion once they passed 17 GB in a month, a threshold the FCC found was not adequately disclosed. $48 million settlement in 2016. | Usage volume | No | FCC |
| 2015 to 2016 | T-Mobile, US | All video it could identify under Binge On, held to about 1.5 Mbps whether or not the provider had joined the programme. | Content | Yes | EFF test |
| 2017 | Verizon Wireless, US | Netflix and YouTube, capped near 10 Mbps for several days in July. Verizon called it a video optimisation test. | Content | Yes | MacRumors, with Verizon's statement |
| 2018 | Verizon Wireless, US | A fire department command vehicle on an "unlimited" plan, cut to 1/200 of normal speed or less after 25 GB, during the Mendocino Complex Fire. | Usage volume | No | Fire chief's court declaration, via Ars Technica |
| 2018 to 2019 | AT&T, Sprint, T-Mobile and Verizon, US | Video apps, held to fixed rates between 1.5 and 4 Mbps at all hours. AT&T slowed 70% of Netflix tests and 74% of YouTube tests. | Content | Yes | Wehe study, SIGCOMM 2019 |
| 2018 | Sprint and Boost Mobile, US | Skype video calls. The only throttling outside streaming apps that the Wehe team found among US carriers. | Application | Yes | Wehe study, SIGCOMM 2019 |
| 2020 (ruling) | Telenor, Hungary | Everything except a set of zero rated chat and music apps once the customer's data allowance ran out. Ruled unlawful on 15 September 2020. | Usage volume, with app exemptions | No | CJEU, C-807/18 and C-39/19 |
| 2021 (ruling) | Telekom Deutschland, Germany | All video streaming under the StreamOn option, capped at 1.7 Mbit/s. Ruled unlawful on 2 September 2021. | Content | Yes, but tunnelled video lost its zero rating | CJEU, C-34/20 |
Read down the VPN column. Nine of the 14 cases were triggered by the identity of the traffic. In eight of them a tunnel would have hidden that identity. The exception is Rogers, whose system also slowed traffic it could not classify on the ports it watched, so an encrypted tunnel could have been caught in the same net. It is the one case here where hiding the traffic was no guarantee. Four were triggered by volume, and in those a VPN would have changed nothing, because the carrier was not looking at the traffic at all. It was looking at the meter. The remaining case, the 2013 to 2014 interconnection dispute, was not throttling in the strict sense. The ISPs and Cogent left the links between their networks congested during a commercial standoff, and a VPN helps with that only when its route happens to avoid the congested link.
The pattern over time matters as much as the count. The content based cases in the record end in 2021, which partly reflects when the measuring stopped. The usage based kind never went away. Slowing the whole line after a threshold is written into most mobile contracts today, it is lawful nearly everywhere as long as it is disclosed, and no privacy tool touches it.
What did the largest throttling measurement find?
Most of what is known about throttling in practice comes from one project. Wehe is an app built at Northeastern University that replays recorded traffic from real apps, then replays a copy with the payload scrambled so that it no longer looks like anything. If the recognisable copy is consistently slower, the network is treating that app differently.The team’s 2019 paper analysed 1,045,413 tests run by 126,249 users across 2,735 ISPs in 183 countries and regions. It found throttling in 30 ISPs in 7 countries. Nearly all of it was on mobile networks and nearly all of it targeted video. The most common limit was 1.5 Mbps, detected in 12 cases, which is roughly what a 480p stream needs.
Two findings carry the argument of this page. First, the researchers checked whether throttling followed the clock, as it would if it were a response to busy networks. Of the 71 throttled pairings of ISP and app that had tests from both day and night, 60 showed no time of day effect. The limits applied at 3 am as they did at 8 pm. Second, they streamed video on the four large US carriers with and without an encrypted VPN tunnel, and reported that VPN tunnels evade content based throttling. With the payload hidden, streams ran at whatever rate the network could carry.
The paper also explains how carriers identify traffic. They read the parts of a connection that stay visible, such as the server name a device sends in the clear when it opens a secure session. That is why encryption in the app alone does not prevent throttling, and why a tunnel that wraps the whole connection does. France’s telecom regulator Arcep adopted Wehe as its own detection tool, which is a fair indication of how regulators rate the method.
Which kinds of throttling can a VPN bypass?
The cases reduce to a short list of mechanisms. This table is the one to keep.| Mechanism | What the ISP looks at | Does a VPN help? | Why |
|---|---|---|---|
| Throttling by app or content type | Server names, traffic signatures | Yes | The classifier sees one encrypted stream to one server and has nothing to match. |
| Port or protocol blocking | Port numbers, protocol fingerprints | Yes | Everything travels inside the tunnel's own port and protocol. |
| Slowdown after a threshold on an "unlimited" plan | Your monthly byte count | No | It applies to the line, and tunnelled bytes count like any others. |
| Data cap with overage fees or a hard stop | Your monthly byte count | No, slightly worse | Tunnel overhead adds to the count. |
| Deprioritisation on a busy cell or node | Your plan tier and the local load | No | Every packet on the line waits in the same queue. |
| Zero rating, where some apps do not count toward the cap | App identity | No, worse | A zero rated app inside a tunnel is not recognised, so it starts counting. |
| Congested links between your ISP and another network | Nothing. It is a capacity dispute. | Sometimes | A VPN server reached over a different path avoids the bad link. It is luck, and it can change from week to week. |
| Throttling or blocking of VPN protocols on a managed network | The VPN handshake | Depends on the protocol | A disguised handshake or TCP port 443 is harder to single out. |
Two rows of eight are a clear yes. Both describe an ISP that discriminates by what the traffic is, which is also the behaviour net neutrality rules were written to stop. For everything the ISP does to your line as a whole, a VPN is the wrong tool, and the fixes are dull: a different plan, a different provider, or using less data.
Can a VPN bypass ISP data caps?
No, and the mechanism is simple enough to check for yourself. A cap is a byte counter on your line. The ISP does not need to know what the bytes are in order to count them. A VPN changes what the ISP can read and leaves how much it can measure untouched.It moves the number slightly in the wrong direction. Every packet in a tunnel carries extra headers. For WireGuard over IPv4 that is 60 bytes per packet, about 4% on full size packets and proportionally more on small ones. Protocols with more framing, such as OpenVPN, add more. On a 1.2 TB home cap that is background noise. On a 10 GB mobile allowance it is a few hundred megabytes a month.
Zero rating is the one place where a VPN changes cap accounting, and it does so against you. If your plan exempts a music or video app from the cap, that exemption depends on the carrier recognising the app. Inside a tunnel it cannot, so the app starts counting. That is the footnote on the StreamOn row above. A VPN would have lifted the 1.7 Mbit/s video limit and handed the customer the data bill for it.
The caps themselves are in slow retreat on fixed lines. Comcast, which introduced a 250 GB cap in 2008 and later raised it to 1.2 TB, launched national plans with unlimited data in June 2025. The FCC opened an inquiry into data caps on 15 October 2024 and has not acted on it since. On mobile, thresholds remain the norm.
Is throttling legal where you live?
| Jurisdiction | Rule on throttling specific traffic | Status in September 2026 | Source |
|---|---|---|---|
| United States, federal | None. The FCC's 2024 order was struck down on 2 January 2025, before its conduct rules were ever enforced. | ISPs must disclose their practices. The FTC can act on deception, as it did against AT&T. | Congressional Research Service |
| California | SB 822 bans blocking, throttling and paid prioritisation. | Enforceable since a federal court declined to block it on 23 February 2021. Washington, Oregon, Colorado and Vermont have their own laws. | California Legislature |
| European Union | Regulation 2015/2120 bans slowing specific apps or categories, with exceptions for congestion, security and legal orders. | In force. A replacement was proposed on 21 January 2026. | BEREC implementation report |
| United Kingdom | The same regulation, retained after Brexit. | Ofcom's guidance of 26 October 2023 allows more room for premium tiers and traffic management. | Ofcom |
| Canada | No blanket ban. Each practice is judged under the 2009 traffic management framework and must be disclosed. | In force. Complaints go to the CRTC. | CRTC 2009-657 |
| India | Licence conditions ban blocking, degrading, slowing down or giving preferential speeds to any content. | Binding on every licensed operator since 2018. | Government of India, Press Information Bureau |
Four of these six jurisdictions ban content based throttling outright. The US at federal level has no rule, and Canada judges each case on its merits. None of the six bans slowing a whole line after a disclosed threshold, so the law and the VPN stop at the same place. Both protect you from an ISP that picks on particular traffic. Neither protects you from the terms of the plan you bought. In the US cases above, the penalties for usage based throttling were for misleading customers about what “unlimited” meant.
Do ISPs throttle VPN traffic itself?
The public record cannot say, because nobody has measured it at scale. Wehe's tests replay video, music and calling apps. VPN protocols are not among them, so the largest dataset on throttling is silent on the point. None of the 14 cases above involved an ISP slowing VPN protocols as a class.Managed networks are different. A university, a hotel or an employer can shape or block any category of traffic on its own network, and VPN protocols are easy to recognise from their opening handshake. If a VPN connects but crawls on one such network and works normally elsewhere, try another protocol before blaming the provider. OpenVPN over TCP port 443 resembles ordinary secure web traffic. Stealth WireGuard, which Le VPN offers in its Windows, Android and iOS apps, disguises the handshake so that inspection equipment has less to match. The full list is on our protocols page.
How do you test whether you are being throttled?
- Pick the thing that is slow: one streaming service, one game download, one video call app.
- Measure it directly. Note the resolution the player settles on, or the download rate the client reports. A general speed test is a poor witness, because a throttle aimed at video does not touch speed test traffic.
- Connect to a nearby VPN server and repeat within a few minutes, on the same network.
- Read the result. Clearly faster through the tunnel means content based throttling, and the VPN is the fix. The same or slower means the limit is on your line as a whole: the plan, the cap or local congestion. Check your usage against the plan's threshold before doing anything else.
- For a second opinion, run Wehe. It needs no VPN and makes the same comparison with replayed traffic.
What changes next?
- EU Digital Networks Act. The Commission's proposal of 21 January 2026 would absorb the Open Internet Regulation and restate the ban on blocking and throttling with reworded exceptions. Digital rights group EDRi argues that the new text opens the door to paid fast lanes. Parliament and Council positions are the next milestone, and the wording of the congestion exception is the part to watch.
- US federal law. After the Sixth Circuit ruling only Congress can restore a national rule. Bills have been introduced in the 2025 to 2026 Congress and none has advanced. State laws are the working rules until that changes.
- Measurement. The most recent large scale public figures on carrier throttling date from 2019. Any new Wehe release or regulator measurement campaign would update the top table.
- Fixed line data caps. Comcast's 2025 plans removed the cap for new customers. Whether the other large cable ISPs follow, and whether the FCC's 2024 inquiry is formally closed, are both open.
About the author
Le VPN Blog Editor
Alan Summers has been writing and editing for the Le VPN blog for years, covering online privacy, cyber security, and the best ways to get the most out of a VPN. He keeps a close eye on the news that affects internet freedom around the world and turns it into practical advice for Le VPN readers.
Articles by Alan Summers →