
An IP ban is a block a website applies to an address after deciding the traffic from it is automated or abusive, so every later request from that IP gets an error, a challenge or an empty page. Most bans are not about one request. Sites score an IP on request rate, on its network owner (datacenter ranges are blocked in bulk), on what other traffic it has sent, and on whether the browser behind it looks real. Rotating residential proxies fix the first three by spreading requests across household IPs from consumer ISPs, so no single address builds up volume or carries a datacenter label. They do not fix the fourth. If your headers, TLS fingerprint or timing look scripted, a fresh IP only delays the block. The rest of this guide shows how to tell which kind of ban you have, then how to rotate, hold sessions and retry without burning the pool.
Which ban are you getting?
Read the response before changing anything. Each symptom points to a different cause.
| What you see | Usual cause | What to change |
|---|---|---|
429 Too Many Requests | Rate limit on one IP or one session | Rotate per request, slow down, honour Retry-After |
403 Forbidden on the first request | IP reputation or a datacenter range | Move to residential exits; Elite for strict anti-bot targets |
403 after a few pages | Behaviour or fingerprint flagged | Fix headers and TLS, keep one identity per session |
| CAPTCHA or JavaScript challenge | Anti-bot vendor scoring the client | Real browser automation plus a sticky session |
Cloudflare 1020 Access Denied | A firewall rule matched | See fixing Cloudflare error 1020 |
407 Proxy Authentication Required | Wrong proxy credentials, not a ban | See fixing proxy error 407 |
For a full decision tree on status codes, use the 403 and 429 troubleshooting guide.
Rotate per request for independent pages
When each page stands alone, such as product pages, search results or listings, give every request a new exit. On Aethyn that is the default: the plain username rotates.
Code Snippetimport requests # Plain username = a new residential IP on every request proxy = "http://aethyn-XXXXX-country-us:PASSWORD@proxy.aethyn.io:2099" proxies = {"http": proxy, "https": proxy} for url in urls: r = requests.get(url, proxies=proxies, timeout=30)
Rotation spreads volume, but it does not excuse a burst. Keep concurrency at a level the site would see from real visitors, and add jitter between requests rather than a fixed interval.
Hold a sticky session when the site expects one visitor
Logins, carts, paginated searches and anything that sets a cookie need the same IP for the whole flow. Switching IP mid-session is itself a ban signal. Add -session- and an ID to the username; requests with that ID share one exit for 30 minutes by default, and -lifetime- sets anywhere from 1 to 1440 minutes.
Code Snippet# One identity for a checkout flow: same exit for every request with cart42 proxy = "http://aethyn-XXXXX-country-us-session-cart42-lifetime-30:PASSWORD@proxy.aethyn.io:2099"
Keep the User-Agent, cookies and Accept-Language constant inside a session. Changing the IP under a stable browser identity is normal; changing the browser identity on one IP is not.

Retry on a new session, not the same one
A retry that reuses the blocked session hits the same blocked IP. When a sticky request gets a 403 or 429, open a new session ID for the retry, back off, and give up after a few attempts so a hard block does not eat bandwidth.
Code Snippetimport random, time, requests def fetch(url, base_session, attempts=3): for n in range(attempts): sid = base_session if n == 0 else f"{base_session}r{n}" # new id = new exit proxy = f"http://aethyn-XXXXX-country-us-session-{sid}:PASSWORD@proxy.aethyn.io:2099" r = requests.get(url, proxies={"http": proxy, "https": proxy}, timeout=30) if r.status_code not in (403, 429): return r time.sleep(int(r.headers.get("Retry-After", 2 ** n)) + random.random()) return r
Session IDs cannot contain a dash, which is why the retry appends r1, r2 instead.
Look like a browser, not a script
Rotation is only half the work. Sites that run Cloudflare, Akamai or PerimeterX (HUMAN) score the client as well as the IP:
- TLS: Python's default TLS handshake does not look like Chrome's. See TLS fingerprinting for scrapers.
- Timing: randomise delays and do not fetch assets a browser would never request in that order.
- Cookies: send back what the site sets, inside the same sticky session.

Premium or Elite?
Use rotating residential proxies on the Premium pool for most sites; it rotates by default and is billed per byte. Move a target to Elite when it keeps returning challenges on Premium. Elite is a curated pool with city and ISP targeting for hard anti-bot targets, on port 5499 for HTTP. For flows that need one IP, see sticky residential proxies, and for how the rotation itself works, read how rotating residential proxies work.
Guides, integrations & docs
Continue reading

What Is a Residential Proxy? Complete Beginner Guide (2026)
Learn everything about residential proxies: how they work, why they are more reliable than datacenter IPs, and how to use them for your business in 2026.

Residential vs Datacenter Proxies: Which One Should You Use?
A residential proxy is an ISP-assigned household IP; a datacenter proxy is a cloud-hosted server IP. Compare trust, speed, cost, and when to switch — Aethyn sells residential only.

Aethyn ProxyVero Benchmark: Independent Residential Proxy Performance Test
ProxyVero recorded 100% success and a 0% block rate for Aethyn on Google, Instagram, TikTok, Nike, and Amazon. The 90/100 score is a dated snapshot, set next to the August cohort.
Premium or Elite residential proxies
Join developers scaling scraping and automation with Aethyn Premium and Elite pools from €2.00/GB.