Throttling is the deliberate slowing or limiting of a system’s performance to prevent overload, manage resources, or control usage. The term shows up in several different contexts, from your internet connection slowing down during peak hours to your laptop’s processor dialing back its speed to avoid overheating. The core idea is always the same: something is intentionally restricting how fast a process can run.
How Internet Throttling Works
Internet throttling happens when your internet service provider (ISP) deliberately restricts your bandwidth. Your connection still works, but data moves slower than what you’re paying for. ISPs typically justify this in two ways.
The first is network congestion. During peak hours, when millions of people in a region are streaming video or downloading files simultaneously, ISPs may slow individual connections to keep the network functional for everyone. Think of it like a highway reducing its speed limit during rush hour.
The second is data caps. Many ISPs impose monthly limits on how much data you can use. Once you exceed that limit, your speed drops for the rest of your billing cycle. You might go from 200 Mbps down to 5 or 10 Mbps, making video streaming or large downloads painfully slow. Some ISPs also throttle specific types of traffic, like video streaming or file sharing, regardless of whether you’ve hit a cap.
How to Tell If Your ISP Is Throttling You
The simplest test involves a VPN. First, connect your computer directly to your modem with an Ethernet cable and run a speed test. Then turn on a VPN and run the same test again. If your speeds are significantly faster with the VPN active, your ISP is likely throttling your connection based on the type of traffic it detects. This works because a VPN encrypts your data so your provider can’t see what you’re doing online, which means it can’t selectively slow down specific activities like streaming or torrenting.
If your speeds are equally slow with and without a VPN, the issue is more likely general congestion or a problem with your equipment rather than targeted throttling.
CPU and GPU Thermal Throttling
Processors in computers, phones, and tablets generate heat as they work. When that heat crosses a safety threshold, the processor automatically reduces its clock speed to cool down. This is thermal throttling, and it’s a built-in protection mechanism, not a malfunction.
Intel describes it as a response that kicks in when the processor’s temperature exceeds its maximum junction temperature. For a current Intel Core Ultra 9 chip, that limit is 105°C (221°F). AMD’s Ryzen 9 processors have a slightly lower ceiling at 95°C (203°F). As a general rule, 100°C is the universal danger zone where throttling begins across most modern processors.
When thermal throttling activates, you’ll notice your system slowing down during demanding tasks like gaming, video editing, or running complex software. The processor is trading performance for survival. Sustained temperatures above these limits could permanently damage the chip, so the system forces itself to ease up. Poor airflow inside a PC case, dried-out thermal paste, a dusty heatsink, or running a laptop on a soft surface that blocks its vents are all common causes. Fixing the cooling problem stops the throttling.
API and Software Throttling
When you use an app or website, it’s often pulling data from a server through something called an API (application programming interface). Servers throttle how many requests any single user or app can make in a given time window. If you’ve ever seen an error message telling you to try again later, you’ve hit a throttle.
The specific signal for this is HTTP status code 429, which means “Too Many Requests.” It often comes with a Retry-After header that tells your device exactly how many seconds to wait before trying again.
Behind the scenes, servers use algorithms to manage this flow. Two of the most common approaches work like physical metaphors. In one model, the system generates “tokens” at a steady rate, and each request costs one token. When tokens run out, requests get denied until more accumulate. This lets the system handle occasional bursts of activity while still enforcing an average rate. In the other model, requests flow through at a constant rate like water dripping from a bucket. If new requests arrive faster than the bucket can drain, the overflow gets rejected. E-commerce sites lean heavily on these techniques during flash sales and holiday events to keep their servers from crashing under sudden demand.
Throttling vs. Bottlenecking
These two terms both describe performance problems, but they work differently. Throttling is intentional. A system deliberately limits its own speed for a reason: heat management, fair usage, server protection. A bottleneck is unintentional. It happens when one component in a system is too slow to keep up with the rest, creating a chokepoint. For example, pairing a powerful graphics card with a weak processor creates a bottleneck because the processor can’t feed data to the graphics card fast enough. No system chose to slow things down; it’s just a mismatch in capability.
The fix for each is different too. Throttling typically gets resolved by addressing the root cause (better cooling, upgrading your data plan, waiting for off-peak hours). Bottlenecks require upgrading or replacing the weakest link in the chain.
Net Neutrality and Throttling Legality
Whether ISPs can legally throttle your internet based on the type of content you’re accessing has been one of the most contested policy questions in tech. Net neutrality rules, when in effect, prohibit ISPs from slowing down specific websites, services, or types of traffic. The FCC has voted to restore net neutrality protections, establishing a national standard intended to keep the internet “fast, open, and fair.” Under these rules, an ISP can still manage general network congestion, but it cannot deliberately slow your connection to Netflix while leaving other services untouched, or charge streaming companies for faster delivery to customers.
The regulatory landscape has shifted multiple times over the past decade, so the specific protections in place depend on when you’re reading this and where you live. Some states have passed their own net neutrality laws independent of federal rules.