Why Net Neutrality Debates Keep Bringing Up VPNs

What net neutrality actually means, in plain terms

Net neutrality is the principle that internet service providers should treat all data traveling over their networks roughly the same way, regardless of its source, destination, or type. Under a net-neutrality rule, your ISP isn't supposed to deliberately slow down traffic from one streaming service while leaving another at full speed, charge extra for access to certain categories of website, or strike deals that give some companies' traffic priority delivery over others'. The core idea is that an ISP's job is to move your bits from point A to point B, not to decide which bits matter more based on who sent them or what business relationship the ISP has with the sender.

The debate is old, contentious, and unsettled in a lot of places. In the United States it has swung back and forth across different administrations and regulatory bodies for over a decade — rules have been adopted, repealed, and revisited multiple times, and the legal and political fight over whether the Federal Communications Commission even has the authority to enforce broadband as a regulated "common carrier" service is still not permanently resolved as of this writing. Other countries have taken different, sometimes more stable, approaches: the EU has baseline net-neutrality protections written into regulation, while some other countries have few or no formal rules on the subject at all. The practical result is that whether you have any enforceable net-neutrality protection today, and how strong it is, genuinely depends on where you live and what the current regulatory and legal situation happens to be in that jurisdiction at that moment.

None of that variation changes what a VPN is or does. A VPN is a piece of software and infrastructure; net neutrality is a rule about ISP conduct. They sit at different layers of the problem, which is exactly why understanding both separately — rather than treating "get a VPN" as a blanket answer to "is net neutrality dead" — matters if you actually want to understand what's going on with your connection.

A short history of how net neutrality and VPNs got linked together

The connection between the two topics isn't abstract — it grew out of a handful of real, publicly documented incidents that made "my ISP might be interfering with specific traffic" feel like a concrete risk rather than a hypothetical one. In 2007, Comcast was found to be interfering with BitTorrent peer-to-peer traffic on its network, using a technique that sent forged reset packets to disrupt those connections specifically, without disclosing it to customers. The FCC took action against the practice, Comcast eventually stopped it, and the episode became one of the foundational examples cited in later net-neutrality rulemaking as evidence that ISPs would, in fact, selectively interfere with specific traffic types if left unregulated. In 2012, AT&T restricted FaceTime video calling over its cellular network to customers on specific data plans, a move consumer advocates argued was exactly the kind of traffic-type discrimination net-neutrality rules were meant to prevent. In 2014, a public dispute between Verizon and Netflix over network interconnection coincided with a period of measurably degraded Netflix streaming performance for Verizon customers — a case that's frequently cited in net-neutrality discussions even though it technically involved interconnection and peering disputes rather than classic on-network throttling, a distinction that matters to how it actually got resolved but rarely survives in the shorthand version of the story.

The US formally adopted strong net-neutrality rules under Title II common-carrier authority in 2015, then repealed them in 2017 following a change in FCC leadership and a new majority vote, a reversal that itself became a major news event and a period when VPN adoption and VPN-provider marketing around "protect yourself from ISP throttling" both increased noticeably. Since then, the US policy picture has kept shifting — some states passed their own state-level net-neutrality laws in the wake of the federal repeal, the FCC voted to restore federal rules again in 2024, and that restoration was itself struck down by a federal appeals court in 2025 on the grounds that the FCC lacked the authority to classify broadband as a Title II common-carrier service in the first place — a legal question that, as of this writing, remains genuinely unsettled rather than resolved in either direction. That back-and-forth, more than any single incident, is why the topic keeps resurfacing in the news, and why VPN providers' marketing around it keeps resurfacing along with it.

It's worth being precise about what this history does and doesn't establish. It establishes that ISPs have, in specific documented instances, interfered with specific traffic types when they had a business incentive to and weren't clearly prohibited from doing so. It does not establish that this is happening broadly, continuously, or to a specific ISP right now — that's a separate, current, and provider-specific question, not something settled by pointing to a nearly-two-decade-old case involving a different company.

What kinds of things does a lack of net neutrality actually let an ISP do?

The concrete practices that net-neutrality rules are meant to prevent generally fall into a few overlapping categories:

Throttling specific traffic types

Deliberately slowing down traffic that an ISP can identify as belonging to a particular category — video streaming, peer-to-peer file transfer, or a specific competing service — while leaving other traffic at normal speed. This requires the ISP to be able to tell what kind of traffic it's looking at, which is the part a VPN interferes with, as covered below.

Paid prioritization ("fast lanes")

An ISP offering, or requiring, payment from a content or service provider in exchange for faster or more reliable delivery of that provider's traffic to end users — effectively creating a tiered internet where deep-pocketed companies' traffic arrives faster than a smaller competitor's, regardless of either company's actual technical needs.

Blocking

Outright preventing access to specific sites, services, or protocols — the most blunt version of non-neutral behavior, and the one most directly comparable to government-level internet censorship, just implemented by a private ISP instead of a state.

Zero-rating

Exempting specific services from counting against a data cap while every other service does count. This is more common on mobile plans than fixed broadband, and it's a genuinely contested case in the net-neutrality debate: it can look consumer-friendly ("free data for this app") while functionally advantaging whichever services the ISP chose to zero-rate over every competitor that wasn't included in the deal.

All four of these depend on the ISP being able to distinguish one kind of traffic from another. That's the technical hook a VPN gets pulled into the conversation through — not because a VPN changes any of these ISP business practices, but because it can change how much of your traffic the ISP is able to see clearly enough to sort in the first place.

How does a VPN actually interact with ISP traffic management?

When you connect through a VPN, your device encrypts its outgoing traffic and sends it to the VPN provider's server, which then forwards it on to its actual destination. Your ISP still sees that you're sending and receiving data, still sees roughly how much of it, and still sees the IP address of the VPN server you're connected to — but it can no longer see the contents of that traffic, and in most cases it can no longer easily tell what type of traffic it is, because the identifying characteristics that traffic-shaping systems typically rely on are hidden inside the encrypted tunnel.

ISPs that throttle specific traffic types usually rely on a technique called deep packet inspection, or on simpler heuristics like which IP addresses and ports a connection is using. A streaming video connection to a known service's servers, for instance, has a recognizable signature that traffic-shaping equipment can flag and target. Once that same traffic is wrapped inside an encrypted VPN tunnel headed to a VPN server's IP address, the ISP mostly just sees "encrypted traffic going to this VPN provider" — it can no longer easily tell whether you're streaming video, downloading a file, or loading a plain webpage. If a specific throttling policy is keyed to recognizing that particular traffic pattern, hiding the pattern can mean the throttling doesn't get applied.

That is a genuinely useful, well-documented effect, and it's the honest version of why VPNs come up in net-neutrality discussions. But it comes with real limits worth being precise about, rather than treating "VPN defeats throttling" as a universal rule.

What a VPN can't do about a lack of net neutrality

It doesn't stop traffic-agnostic throttling

If an ISP throttles everyone's connection during a specific time window because the local network is congested, or slows down a customer's overall connection after they cross a data cap, that kind of throttling isn't identifying your traffic by type — it's applied at the account or network level regardless of what you're doing. A VPN doesn't change your total bandwidth usage or exempt your account from a data cap, so it does nothing against this category of slowdown. This distinction matters because a lot of what gets described informally as "my ISP is throttling me" is actually general network congestion or a data-cap policy, not selective traffic-type discrimination — and only the latter is something a VPN can plausibly route around.

It doesn't restore a competitive market for ISPs

A lot of what makes weak net-neutrality enforcement consequential in practice is that many people have only one or two realistic broadband options where they live. Net neutrality debates are partly a proxy for a deeper structural problem — limited ISP competition — that a VPN does nothing to address. If your only realistic ISP decides to make a specific service perform badly and there's no regulation stopping it, a VPN might restore that service's performance in many cases, but it doesn't change the market structure that let the ISP make that call with limited customer recourse in the first place.

It doesn't make paid prioritization deals disappear

If an ISP has struck a commercial deal to prioritize a specific large content provider's traffic over general traffic, a VPN changes how visible your traffic is to the ISP's traffic-shaping systems — it doesn't change whether a competing, non-prioritized service's servers are architecturally getting a faster path through the network. Depending on exactly how a given prioritization arrangement is implemented, a VPN may or may not have any effect on it at all.

It can add its own overhead

Routing traffic through an additional server, with encryption and decryption at both ends, adds some latency and can reduce throughput compared to an unthrottled, direct connection. In a genuine throttling scenario a VPN's overhead is usually far smaller than the throttling penalty it's helping you avoid, so the net effect is still faster — but on a connection that wasn't actually being throttled, a VPN can make things measurably slower, not faster, purely from its own overhead. This is why "try a VPN" isn't automatically the right troubleshooting step for every slow-connection complaint; it's specifically useful when the slowdown is tied to traffic identification, and not otherwise.

It doesn't hide the fact that you're using a VPN

An ISP that wanted to treat VPN traffic itself less favorably — as opposed to trying to identify what's inside it — generally still can, because a VPN connection's destination (the VPN server's IP) and its general characteristics as encrypted VPN traffic are usually visible even when its contents aren't. This has come up in some markets: an ISP that isn't bound by net-neutrality rules could in principle throttle or deprioritize VPN traffic as a category, rather than only being able to throttle by traffic type. Whether a given ISP actually does this varies a great deal and isn't something we can state as a general fact one way or the other — it's a jurisdiction- and provider-specific question, and a genuinely important limit on how far "just use a VPN" can be trusted as an answer.

Does a VPN actually stop ISP throttling? What the evidence realistically supports

The honest answer is: it can, for the specific and fairly narrow case of traffic-type-based throttling that depends on the ISP being able to identify the traffic in the first place. Independent reporting and user-run testing over the years — comparing measured speeds to a specific service with and without a VPN active on the same connection — has periodically found cases where a VPN measurably restored throughput to a service that appeared to be throttled without one. That kind of test is meaningful evidence for the specific connection and time period it was run on, but it isn't a permanent, universal finding — ISP practices, network conditions, and the specific services affected all change over time, which is exactly why we don't cite a specific historical statistic here as if it still holds true today. If you want to know whether your own connection is being selectively throttled, the reliable way to find out is to run your own speed comparison — the same service, same time of day, with and without your VPN active — rather than relying on someone else's test from a different network, in a different country, at a different point in time.

It's also worth being clear that a single before/after speed test isn't proof of deliberate throttling by itself. Speeds vary for a lot of reasons unrelated to ISP policy — server-side congestion on the streaming service's end, your home Wi-Fi, peak-hour network load shared by every customer in your area, or a VPN server that's itself overloaded. A consistent, repeatable pattern across multiple tests, multiple times of day, and ideally multiple VPN servers is a much stronger basis for concluding something specific to a service is being targeted than a single measurement.

Does using a VPN actually count as "fixing" net neutrality?

No, and this is worth stating plainly because the framing matters. A VPN is a private, individual workaround that a given user has to know about, choose to pay for or use, and actively run. Net neutrality, as a regulatory principle, is about setting a baseline rule that applies to everyone on a network automatically, without requiring each individual customer to take a technical countermeasure. A world with strong net-neutrality enforcement and a world where everyone individually adopts a VPN to route around throttling are not equivalent outcomes, even where a VPN happens to produce a similar practical result for the traffic types it can actually help with. The VPN workaround also doesn't address blocking, paid prioritization deals between ISPs and large content companies, zero-rating, or any of the structural market issues that make weak net-neutrality protection consequential in the first place — it addresses one specific symptom (selective throttling of identifiable traffic) for the specific individual using it, and nothing else on the list.

There's also a real equity dimension worth naming honestly. A VPN workaround requires awareness that the option exists, some technical comfort setting it up, and in most cases an ongoing subscription cost. Treating "just use a VPN" as a sufficient answer to a net-neutrality rollback quietly shifts the cost and effort of dealing with ISP traffic discrimination onto individual consumers who can afford and know how to use the workaround, rather than addressing the underlying practice for everyone. That's a reasonable thing to keep in mind if you see "VPN" offered as a complete solution to a net-neutrality policy debate rather than as one partial, individual mitigation for one specific symptom of it.

Why do VPN providers themselves talk about net neutrality so much?

It's worth being clear-eyed about the incentive here: VPN providers are commercial companies, and a live net-neutrality controversy is genuinely good marketing material for a product whose core pitch is "hide what your ISP can see about your traffic." That doesn't make the underlying technical point false — a VPN really can help against traffic-type-based throttling, for the reasons covered above — but it's reasonable to read a VPN company's net-neutrality messaging with the same skepticism you'd apply to any other marketing claim, and to separate what's a genuine technical capability from what's framing chosen because it resonates with a topical news cycle. When a net-neutrality rule change makes headlines, it's a predictable, recurring pattern that VPN providers' marketing content and search-ad spend around throttling-related keywords increases around the same time — worth knowing simply so you recognize the pattern rather than mistaking topical marketing volume for a change in the underlying facts about what a VPN does.

How do I know if I'm actually being throttled right now?

A practical, low-effort way to check: pick a service you suspect is being slowed down, run a speed or performance test to that specific service without a VPN active, then reconnect through a VPN (ideally to a server reasonably close to you geographically, to minimize the VPN's own added latency) and repeat the same test under similar conditions — same time of day, same device, same network. If performance to that specific service is meaningfully better with the VPN active while your general, non-VPN internet speed to other destinations is normal, that's a reasonably strong signal that something about that specific traffic was being treated differently. If performance is roughly the same with or without the VPN, or if everything on your connection is slow regardless of destination, that points toward general congestion, a data cap, a problem with your home network, or an issue on the service's end rather than selective ISP throttling — and a VPN isn't the right tool for any of those. Repeating the comparison a few times across different days strengthens the conclusion either way; a single test on a single evening can be misleading in both directions.

What should I actually look for in a VPN if throttling avoidance is my goal?

If selective ISP throttling of a specific traffic type is the actual problem you're trying to address, a few practical factors matter more than general marketing claims about "beating throttling":

Server locations close to you

Since a VPN's own routing overhead works against you on a connection that wasn't actually throttled, and reduces (though doesn't eliminate) the benefit on one that was, a provider with a server reasonably close to your actual location minimizes that overhead compared to routing your traffic across a continent unnecessarily.

Strong, modern encryption and protocol support

Since the mechanism that helps against throttling is hiding traffic characteristics inside encryption, a VPN using current, well-regarded protocols is doing the actual work here — this isn't a feature specific to any one provider, but it's worth confirming a provider supports a modern protocol rather than something outdated.

Consistent, adequate speeds on its own servers

A VPN that's itself slow, congested, or unreliable will undercut any throttling benefit with its own bottleneck. This is a genuinely provider-specific, testable quality — one worth checking via a trial period or short-term plan against the specific service you care about, rather than assuming any VPN performs identically.

We can't respond to VPN-specific throttling scenarios with a scored, ranked recommendation here, since real-world performance against a specific ISP's specific traffic-management policy varies by location, provider, and over time in ways a general guide can't responsibly promise. Our individual reviews of NordVPN, Proton VPN, PureVPN, and FastestVPN go into more detail on each provider's protocol support and server footprint if you want to evaluate a specific option against your own connection.

Does net neutrality status affect whether I need a VPN for other reasons?

Not really — it's worth keeping this separate from the throttling question specifically. Most of the common reasons people use a VPN — hiding browsing activity from an ISP for privacy reasons, encrypting traffic on public Wi-Fi, accessing region-specific content, or reducing the amount of metadata an ISP can log and potentially sell or hand over — apply regardless of whether strong net-neutrality protections exist where you live. Net neutrality specifically concerns whether an ISP treats different types of traffic differently; a VPN's privacy and security benefits exist independent of that question, and they don't go away in a jurisdiction with strong net-neutrality rules, nor do they only appear in one without them. If you're evaluating whether you personally need a VPN at all, it's worth thinking through the privacy, security, and access reasons on their own merits rather than treating the current state of net-neutrality regulation as the deciding factor either way.

Do ISPs that also own content or streaming companies have a conflict of interest here?

This is one of the more substantive arguments made in favor of net-neutrality rules, and it's worth understanding on its own terms rather than folding it into the general throttling discussion. A number of large ISPs are also, through mergers and acquisitions, owners of media and streaming businesses — AT&T owned WarnerMedia (and its streaming service) for several years before spinning it off, and Comcast has owned NBCUniversal, including its Peacock streaming service, since 2011. When the same corporate parent owns both the pipe your traffic travels through and a competing streaming service, the incentive to treat that owned service's traffic more favorably — or a rival's traffic less favorably — is structurally present even without any specific proven instance of it happening. Net-neutrality rules are partly meant to foreclose that incentive from ever being acted on, regardless of whether a specific company currently is or isn't doing so.

A VPN's relevance to this specific concern is limited and indirect. Hiding your traffic's type from your ISP can help if the mechanism of concern is identification-based throttling of a competing service. It does nothing about a more sophisticated form of favoritism — for instance, an ISP simply under-investing in network capacity or peering arrangements in ways that degrade a competitor's service performance without ever technically "throttling" identifiable traffic, which is a documented category of concern in some of the historical interconnection disputes referenced earlier. This is a case where the structural, ownership-level conflict of interest is the actual issue, and a technical workaround at the individual-connection level addresses only the narrowest slice of it.

How does this interact with mobile data plans and zero-rating specifically?

Zero-rating deserves its own treatment because it works differently from throttling, and a VPN's effect on it is close to the opposite of helpful. Where a mobile carrier zero-rates a specific service — commonly music or video streaming apps that don't count against your monthly data allowance — that exemption is typically implemented by the carrier recognizing that service's specific traffic, the same kind of traffic identification that a VPN is generally good at defeating. That means routing a zero-rated app's traffic through a VPN can actually cause you to lose the zero-rating benefit, since the carrier can no longer recognize it as the exempted service and instead sees generic encrypted VPN traffic, which counts normally against your data cap. If you're on a plan with a meaningful zero-rated service you rely on, it's worth checking whether routing that specific app's traffic through a VPN changes how it's billed against your data allowance before assuming a VPN is a net positive for your situation — in this one case, the VPN can work against you rather than for you.

The net-neutrality objection to zero-rating itself is a separate point worth understanding: critics argue that even though zero-rating feels like a consumer benefit (free data for a specific app), it functionally disadvantages every competing service that wasn't included in the zero-rating deal, since using a competitor's service still counts against your cap while the carrier's chosen partner doesn't. A new, smaller streaming or communication service trying to compete against an established zero-rated incumbent starts at a real disadvantage that has nothing to do with the quality of either product. Some countries' net-neutrality frameworks explicitly prohibit zero-rating for this reason; others allow it; still others simply haven't addressed the question in formal regulation at all, leaving it to individual carriers' discretion.

Does my ISP's terms of service actually prohibit using a VPN?

Almost always, no — for ordinary residential and mobile broadband service, using a VPN is not something typical ISP terms of service prohibit, and it isn't illegal in most countries either (see our guides on VPN legality by country if you're specifically concerned about a particular jurisdiction). Where this gets genuinely more complicated is business, enterprise, or certain mobile carrier plans that include specific clauses about network usage, tethering, or bypassing plan-specific traffic management — some mobile plans, for instance, have historically included terms about video-quality throttling or hotspot data that a VPN could interact with in ways worth checking your specific plan's terms for, rather than assuming residential-ISP norms automatically apply. If you're on a standard home internet plan, VPN use itself isn't the kind of thing that risks your account being flagged or terminated; if you're on a specialized plan with unusual data or tethering restrictions, it's worth actually reading the relevant clause rather than assuming either way.

Common myths about VPNs and net neutrality

Myth: A VPN makes ISP throttling impossible

Fact: a VPN can defeat throttling that depends on the ISP identifying your traffic type, but it does nothing against traffic-agnostic slowdowns like general congestion, data caps, or an ISP that chooses to deprioritize VPN traffic itself as a category.

Myth: Net neutrality and VPN privacy are the same issue

Fact: net neutrality is about whether an ISP treats different traffic types equally; VPN privacy benefits — hiding browsing activity, encrypting traffic on public Wi-Fi — are a separate set of benefits that exist regardless of net-neutrality policy in your jurisdiction.

Myth: If net neutrality is repealed, every ISP will immediately start throttling

Fact: repeal removes a legal prohibition; it doesn't automatically mean every ISP starts throttling traffic the moment it takes effect. Whether a specific ISP actually changes its traffic-management practices is a business decision that varies by company, and isn't something a general guide can responsibly claim is happening universally without evidence specific to that provider.

Myth: A VPN protects you from every possible ISP traffic-management practice

Fact: it specifically helps against traffic-type identification. Blocking based on destination IP (rather than content type), paid prioritization arrangements between an ISP and a large content provider, zero-rating structures, and account-level data caps either aren't affected by a VPN at all, or are affected in ways that depend heavily on exactly how the specific practice is implemented.

What can I do about suspected throttling besides using a VPN?

A VPN is a workaround, not the only option, and it's worth knowing the other paths available if you think your connection is being treated unfairly. Independent network-measurement tools exist specifically to help ordinary users document what's happening on their connection — running repeated, methodical measurements over time builds a record that's far more persuasive than a single anecdotal impression that "Netflix has felt slow lately." If you find a consistent pattern, contacting your ISP's support line directly and asking specifically about traffic management policies for the affected service is a reasonable first step — some ISPs will acknowledge network management practices when asked directly, even if they don't advertise them prominently.

Where formal regulatory protection exists in your jurisdiction, filing a complaint with the relevant regulator is a legitimate path that a purely technical workaround doesn't replace — a regulator investigating a pattern of complaints about a specific ISP practice can produce an actual policy consequence for that ISP, which is something an individual VPN subscription never will. In the US, that's currently the FCC, though its authority to act on broadband specifically has been the subject of the ongoing legal disputes described earlier; state attorneys general and state-level regulators have also become a more active avenue in states that passed their own net-neutrality laws following the federal repeal. In the EU, national telecom regulators handle net-neutrality enforcement under the EU's regulation, with the Body of European Regulators for Electronic Communications coordinating a consistent approach across member states.

Switching providers, where you actually have another realistic option, is the most direct market response to an ISP's traffic-management practices — though, as covered earlier, a meaningful number of people don't have a genuine second choice for wired broadband at their address, which is exactly why this option isn't always available in practice even when it's the theoretically correct answer. Where a real second option exists, an ISP's specific throttling or blocking practices are a legitimate and directly relevant factor to weigh alongside price and speed when choosing between them.

None of these alternatives are mutually exclusive with using a VPN — you can run a VPN for the immediate, practical benefit on your own connection while also documenting the pattern, contacting your ISP, and filing a complaint if the evidence supports it. The VPN addresses your own experience today; the other steps are what actually has a chance of changing the underlying practice.

A realistic way to think about the relationship

Net neutrality is a policy question about what an ISP is allowed to do to your traffic; a VPN is a technical tool that changes what your ISP can see well enough to act on. They intersect at exactly one point — an ISP generally can't selectively throttle traffic it can't identify — and that intersection is real and, in the right circumstances, genuinely useful. But it's a narrow intersection. A VPN doesn't restore competition among ISPs, doesn't stop blocking or paid-prioritization deals that don't depend on identifying your specific traffic, doesn't exempt you from data caps or general congestion, and in jurisdictions without net-neutrality protection, doesn't necessarily stop an ISP from simply treating VPN traffic as its own deprioritized category if it chooses to. Treat a VPN as one useful, testable mitigation for one specific symptom — not as a substitute for the underlying policy debate, and not as a guarantee against every way a lack of net neutrality could affect your connection.