Net neutrality is dead: how ISPs throttle services

The 2017 FCC repeal of net neutrality rules in the United States ended formal regulatory protection against ISPs throttling specific services. Most of the consequences were predicted; some were not. Six years later, the throttling picture is documented and quantifiable.

This is the technical version of how ISPs identify and throttle specific services, the documented cases, how to detect throttling on your own connection, and what a VPN can and cannot do about it.

How ISPs identify specific services

An ISP that wants to throttle Netflix specifically (versus throttling all video, or all traffic) needs to identify Netflix traffic in real time. Several techniques:

Destination IP. Netflix's CDN uses well-known IP ranges from its peering partners (Open Connect appliances colocated with ISPs, plus Akamai and CloudFront). An ISP can build a list of "Netflix IPs" and throttle traffic to those IPs. Easiest technique; defeated by Netflix using new IPs or by the user using a VPN.

SNI in TLS handshakes. As covered in What your ISP sees, SNI is sent in plaintext at the start of every TLS connection. The ISP sees Host: netflix.com in the SNI and can throttle from there. Defeated by Encrypted Client Hello (when deployed) or by VPN routing.

Deep packet inspection on traffic patterns. Even encrypted traffic has identifiable patterns. Netflix's video stream has characteristic packet sizes and timing that differ from generic HTTPS browsing or from email or from gaming. A DPI-capable network can identify "this is Netflix video" without seeing the SNI. Harder to defeat without protocol-level obfuscation.

Application-layer analysis. Some ISPs have visibility into HTTP headers (for unencrypted HTTP, increasingly rare in 2026) or use commercial threat-intelligence feeds that map IPs to services. Provides additional matching capability beyond raw network analysis.

Customer-segment data. ISPs know which customers have which plans. T-Mobile's video-throttling on certain plans was applied based on the customer's plan tier — the throttling was per-account, not per-traffic-pattern.

The combination determines what the ISP can throttle. Most commercial ISP throttling uses some combination of IP, SNI, and DPI.

Documented throttling cases

Specific incidents that have been investigated and confirmed:

AT&T video throttling (2018). AT&T capped video streaming to 480p on its mobile plans. Confirmed by independent measurement (the Wehe app from Northeastern University). Affected Netflix, YouTube, and other major video platforms. AT&T's framing: a "feature" reducing data usage on mobile. User experience: video quality artificially limited.

Verizon Netflix throttling during 2018 peering dispute. Verizon and Netflix had a peering disagreement; during the dispute, Netflix performance for Verizon customers degraded substantially. Verizon framed this as Netflix's responsibility (insufficient capacity); Netflix framed it as Verizon refusing to upgrade peering interconnect. The user experience was buffering during peak hours. Resolved when both parties reached a new commercial agreement.

T-Mobile "Binge On" video throttling. T-Mobile "Binge On" capped video to 480p. Marketed as a "data-free" feature; net effect was video throttling. EFF and others raised concerns; FCC at the time cleared the program; later analysis confirmed that the throttling was not optional for many customers despite marketing language.

Wehe app data (Northeastern University, 2018-2024). The Wehe app continuously measures throttling by simulating various services and measuring whether the ISP applies different bandwidth limits. Findings have included documented throttling of Netflix, YouTube, Vimeo, Skype, NBCSports, and others by various ISPs over the years. The data is publicly available.

Comcast / Xfinity peering throttling history. Multiple disputes with Netflix and others over peering arrangements that produced visible degradation. Resolved through commercial agreements that some commentators described as paid prioritisation in everything but name.

International examples. Brazilian and Indian ISPs have been documented throttling specific services during peering disputes. UK ISPs have historically engaged in less visible throttling under the cover of "traffic management" provisions in BT's older terms.

How to detect throttling on your connection

The honest tests:

1. Speed test to multiple destinations. Run speedtest.net, fast.com (Netflix's own speed test), and a third independent test. If all three show similar speeds, your ISP is not throttling those endpoints. If fast.com (Netflix-routed) is much slower than speedtest.net (different infrastructure), there is something happening on the Netflix path specifically.

2. Same speed test through a VPN. Run the same speed test with VPN active. If VPN-routed test is meaningfully faster than direct test for a specific service, your ISP is throttling that specific service. The VPN encrypts the traffic so the ISP cannot identify it as Netflix; the ISP applies general traffic management instead, which is faster.

3. Wehe app. Free tool from Northeastern University that automates the comparison testing. Detects throttling for major services and produces a report.

4. Compare across ISPs. If you have access to multiple connections (your home, your phone's mobile data, a friend's connection on a different ISP), test the same service across all three. Significant variation often indicates one or more of the connections is throttling.

The math you want: VPN-routed test should be SLIGHTLY slower than direct test for unrelated services (because VPN adds 5-15% overhead). If VPN-routed test is FASTER for a specific service, your ISP is throttling that service and the VPN is restoring normal speed.

What a VPN does about throttling

A VPN encrypts your traffic between your device and the VPN provider. The ISP sees encrypted traffic to a single IP — your VPN provider. The ISP cannot identify the specific service inside the tunnel.

Implications:

Service-specific throttling is defeated. The ISP cannot identify Netflix vs YouTube vs Zoom inside the tunnel; they treat all VPN traffic the same. If the ISP only throttles Netflix specifically, your Netflix performance through the VPN should match other unthrottled services.
General throttling is not defeated. If the ISP throttles all traffic during peak hours regardless of identification, the VPN does not help. The throttling applies to your VPN tunnel just like everything else.
Per-account caps are not defeated. If your plan has a 50GB monthly cap, VPN does not increase it. The cap applies to total usage; VPN does not reduce the count.
Peering-related slowdowns may or may not be defeated. If your ISP has poor peering with Netflix specifically but good peering with your VPN provider, VPN-routed Netflix performance is better than direct. If your ISP has poor peering generally, VPN does not help.

The clean test: if your unthrottled speed test (to a generic server) is meaningfully different from your throttled-service speed test (to Netflix or YouTube), VPN will restore the unthrottled rate. If both tests are equally slow, your problem is general congestion or capacity, and VPN does not solve it.

Net neutrality status by country

Quick survey:

United States. No federal net neutrality regulation since 2017. Some state-level laws (California's SB 822 specifically) provide partial protection. The FCC has signaled willingness to revisit; political-cycle dependent.

European Union. Net neutrality is enshrined in the 2015 Open Internet Regulation (Regulation 2015/2120). ISPs are prohibited from throttling specific services. Enforcement is decent; specific complaints get investigated.

United Kingdom. Post-Brexit, the UK retained the EU framework substantially. Ofcom enforces. Less aggressive than EU enforcement but still meaningful.

Canada. CRTC's Telecom Decision 2009-657 and subsequent rulings provide net neutrality protection. Strong.

Australia. No specific net neutrality law. ISPs operate under broader telecommunications competition framework with limited per-service-throttling visibility.

India. TRAI's 2018 net neutrality rules prohibit discriminatory pricing and throttling. Strong in principle; enforcement uneven.

Most of Latin America and Africa. Highly variable. Some countries have explicit rules; some have nothing.

For users in countries with active net neutrality rules, large-scale per-service throttling is uncommon. For users in countries without (notably the US), it is documented and ongoing.

What VPN cannot solve

Worth being honest:

Bandwidth-intensive home use overall. If your home connection has a 100 Mbps plan and you and four other family members are streaming simultaneously, VPN does not give you more bandwidth. It encrypts the traffic; it does not multiply it.
Overhead on already-slow connections. On a 5 Mbps mobile connection, VPN's 5-15% overhead is meaningful. Adding VPN to an already-slow connection can make it slower, not faster.
CGNAT and IPv4 exhaustion problems. Some ISPs (mobile especially) put users behind CGNAT, which causes various issues that VPN does not fix. VPN does not address these.

The clean rule: VPN helps when your ISP is selectively slowing specific services. It does not help when everything is slow due to capacity, distance, or congestion.

Frequently asked

Is my ISP throttling me?

Test it. Wehe app or VPN-comparison testing answers this. Speculation is not useful; measurement is.

Why would my ISP throttle Netflix?

Multiple reasons over the years: peering disputes, capacity management, attempts to favour the ISP's own competing video product, attempts to push customers to higher-tier plans. Different ISPs at different times for different reasons.

Will VPN make my internet faster?

Usually no, sometimes yes. If your ISP throttles specific services, VPN restores normal speed for those services. If your ISP does not throttle, VPN adds slight overhead (5-15%) and is slightly slower.

Is throttling legal?

Depends on country. EU, UK, India, Canada have explicit rules against discriminatory throttling. US, Australia, most of Latin America have lighter or no rules. ISPs typically frame throttling as "traffic management" which most regulatory frameworks permit in some form.

What about mobile carriers?

Mobile carriers throttle more aggressively than fixed-line in most markets. Plan-based video throttling is widespread. Per-service throttling exists but is less documented because mobile measurement is harder. VPN on mobile usually helps with mobile-specific throttling.

Does T-Mobile still throttle video?

The "Binge On" framework existed under various names (then "Plus On Demand"); current details depend on plan and have evolved. Some plans cap video; others do not. Read your plan terms or test directly.

Try Fexyn free for 7 days — WireGuard for low-overhead encryption that defeats service-specific throttling. The does VPN slow internet blog covers protocol overhead in detail; What your ISP sees covers the broader ISP-visibility picture.

Last reviewed 2026-05-09.