AutomationProxies

How to Avoid IP Bans Using Rotating Residential Proxies

EV
Security Analyst
Published
May 14, 2026
Updated
November 14, 2026
Read Time
4 min read
Rate limits, fingerprints, and a burned IP are how bans start

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 seeUsual causeWhat to change
429 Too Many RequestsRate limit on one IP or one sessionRotate per request, slow down, honour Retry-After
403 Forbidden on the first requestIP reputation or a datacenter rangeMove to residential exits; Elite for strict anti-bot targets
403 after a few pagesBehaviour or fingerprint flaggedFix headers and TLS, keep one identity per session
CAPTCHA or JavaScript challengeAnti-bot vendor scoring the clientReal browser automation plus a sticky session
Cloudflare 1020 Access DeniedA firewall rule matchedSee fixing Cloudflare error 1020
407 Proxy Authentication RequiredWrong proxy credentials, not a banSee 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 Snippet
import 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.

Per-request rotation spreads volume. Sticky holds one identity.
Per-request rotation spreads volume across the pool. Sticky holds one rotating-pool IP for 1–1440 minutes, default 30.

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 Snippet
import 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:

  • Headers: send a current User-Agent with the matching Accept, Accept-Language and Sec-CH-UA headers.
  • 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.
Rotation is not enough if the session looks like a bot
Rotation is not enough if delays, cookies, and headers still look automated.

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.

Share this article

Guides, integrations & docs

Continue reading

Premium or Elite residential proxies

Join developers scaling scraping and automation with Aethyn Premium and Elite pools from €2.00/GB.

Back to all articles