Residential Proxies: Why Your Bot Blocklist Stopped Working
The blocklist has ten thousand IPs on it, the bot traffic keeps coming, and the new addresses have never done anything wrong. That is not a failure of maintenance. It is a failure of the idea. The bots are no longer coming from data centers you can recognize. They are coming from living rooms.
What a residential proxy actually is
A residential proxy routes traffic through a real consumer's internet connection. The exit IP belongs to a household or a small business on a normal broadband or mobile line, not a hosting provider, and it carries the trustworthy IP reputation of a real home connection. When a fraudulent click leaves a residential proxy, it does not appear on any datacenter blocklist, because it is not a data center. The FBI warned about exactly this in an Internet Crime Complaint Center notification dated August 18, 2022: criminals use residential proxies to run large-scale credential-stuffing attacks without being tracked, flagged, or blocked.
The scale is the point. A 2019 IEEE Symposium on Security and Privacy study catalogued more than 6 million residential proxy IP addresses spread across more than 230 countries. Imperva attributed roughly a quarter of bad-bot traffic to residential ISPs in its 2024 report and found 21 percent of bot attacks using residential proxies in 2025. Imperva's 2026 Bad Bot Report puts automated traffic at 53 percent of all web traffic, with humans down to 47 percent, and a large and growing share of the bad half no longer comes from data centers at all.
Why blocklists cannot win this fight
There are three concrete reasons a list of IPs cannot win. Rotation: residential proxy networks cycle through millions of distinct exit IPs, and a defense that works by enumerating bad addresses is playing a game it mathematically cannot finish. Staleness: by the time you have identified and excluded an address, the operator is on a different one, and the flagged address may already belong to a real customer again. And caps: Google Ads lets you exclude up to 500 IP addresses per campaign and requires you to list every version of an address, IPv4 and IPv6. Five hundred slots against millions of rotating IPs is not a contest.
The proof that even the largest takedown does not fix it came on January 29, 2026, when Google's Threat Intelligence Group announced it had disrupted IPIDEA, one of the largest residential proxy networks in the world, with more than 550 distinct threat groups observed using its exit nodes. Google's own explanation reads like an indictment of IP blocking: by routing traffic through an array of consumer devices all over the world, attackers can mask their malicious activity by hijacking these IP addresses. The surviving pool is too large and too indistinguishable from real users for any static exclusion list to keep up.
What replaced the blocklist
Detection moved down the stack. TLS fingerprinting, JA4 and its predecessor JA3, reads the handshake: every TLS client announces which cipher suites it supports, which extensions it sends, and in what order, and those choices differ between implementations. A headless browser modified for automation has a different handshake from a real Chrome build, and the fingerprint catches it even when the IP is a clean residential address. HUMAN Security's Q1 2026 testing found JA4+ fingerprinting alone identified 67 percent of the bot traffic that passed IP reputation checks, and Cloudflare's 2026 Bot Management Report found it detected 73 percent of the agentic bot traffic that passed IP reputation and behavioral checks.
The second layer is latency. A proxied request has to traverse more hops than a direct one, and Cloudflare found it could characterize residential proxy traffic with a high true positive rate on that basis alone. Its v8 bot management model analyzes over 46 million HTTP requests per second and classifies more than 17 million unique IPs per hour as participating in residential proxy attacks, across more than 45,000 ASNs in 237 countries. The third layer is behavior: how the session moves, what it does, and whether the same device fingerprint appears across many unrelated accounts. None of these layers asks where the connection came from. That is the point. The address is now one of the weaker signals, and the defenses that still start there are defending the last war. The botnet that made this concrete is BADBOX 2.0: The Botnet in Living Rooms.
Frequently asked questions
What is a residential proxy?
A proxy that routes traffic through a real consumer's internet connection, so the exit IP belongs to a household or small business on a normal broadband or mobile line, not a hosting provider. It carries the IP reputation of a real home.
Why do IP blocklists fail against residential proxies?
The networks rotate through millions of exit IPs, lists go stale within hours, and the flagged address may belong to a real customer the next day. Google Ads also caps exclusions at 500 IPs per campaign, against millions of rotating addresses.
What is JA4 fingerprinting?
A TLS fingerprinting method that reads the handshake: which cipher suites a client supports, which extensions it sends, and in what order. Modified browsers have different handshakes from real ones, so the fingerprint catches automation even from a clean residential IP.
How much web traffic is automated now?
Imperva's 2026 Bad Bot Report puts automated traffic at 53 percent of all web traffic, with humans down to 47 percent. In 2024, automated traffic had already passed human traffic at 51 percent, with bad bots alone at 37 percent.