A backconnect proxy, also sold as a backconnect rotating proxy, is one gateway address (a single host and port) in front of a pool of exit IPs. Your tool connects to the gateway, and the gateway connects out to the target through an exit it picks. With no session parameter, each new connection can get a new exit. With a session ID, the gateway holds one exit, which makes the session sticky.
Use it for stateless scraping, public product and stock monitors, and location checks, and add a sticky session for logins and multi-page flows. Do not use it for checkout, account, or ticketing work that needs one fixed IP, or for IP allowlists. Those jobs belong on static ISP proxies. If you want a rotating residential gateway, see residential plans.
How a backconnect proxy gateway works
"Backconnect" describes the path: you never connect to the exit IP directly. You connect to the gateway, and the gateway connects back out through the pool.
For an HTTPS request through an HTTP proxy, the flow looks like this:
- Your tool opens a TCP connection to the gateway host and port.
- It sends a
CONNECT target.com:443request with your credentials in theProxy-Authorizationheader. - The gateway reads the credentials. It checks your account and any parameters, such as session ID or location.
- The gateway picks an exit IP from the pool that matches those parameters.
- The exit opens a connection to the target. The gateway joins the two connections into one tunnel.
- Your tool and the target do the TLS handshake through the tunnel. The gateway cannot read the encrypted traffic.
With SOCKS5, the steps are the same in principle. The username and password go in the SOCKS5 login step (RFC 1929) instead of an HTTP header.
Rotation happens per connection
This detail explains most "my rotating proxy does not rotate" reports. For HTTPS, the gateway picks the exit when the tunnel opens. Every request sent through that open tunnel uses the same exit.
Most HTTP clients keep connections open and reuse them (keep-alive). A Python requests.Session, a browser, or a bot can send dozens of requests through one tunnel, so all of them leave from one IP. To get a new exit, open a new connection: use a new session object, or close the connection between requests.
Session parameters on a backconnect gateway
You control the gateway with parameters. Each provider puts them in a different place, but the parameters themselves are similar:
| Parameter | What it does | Where providers usually put it |
|---|---|---|
| Session ID | Pins one exit IP to every connection that uses the ID | Username or password suffix |
| Session lifetime | Sets how long the gateway holds that exit | Username flag, or fixed by the provider |
| Country | Limits exits to one country | Username flag, hostname, or port |
| State or city | Limits exits to a smaller area | Username flag or hostname |
| Mode | Chooses sticky or rotating behavior | Port, hostname, or session flag |
A common style puts flags in the username, for example user-country-us-session-abc123. That is only an example. Copy the syntax from your provider's dashboard, because one wrong character can send you to a random exit or return a 407.
With Unknown Proxies residential plans, the dashboard generator builds the lines for you:
- The location (country, US state, or city) is part of the hostname.
- Sticky and rotating lines use different hostnames and ports.
- Each sticky line has its own session ID at the end of the password. Generate 50 sticky lines and you get 50 separate sessions.
- A sticky session holds its exit for up to 2 hours. A rotating line can get a new exit on every request.
The generator exports ip:port:user:pass, user:pass@ip:port, and CSV formats for some bot tools. If your tool needs another layout, the proxy formatter converts the list.
What IP types sit behind a gateway
Backconnect says how you reach the pool. It does not say what the IPs are. The same gateway design can front residential, datacenter, or mobile pools, and some sellers front ISP pools too.
| IP type | Strength | Weak point |
|---|---|---|
| Residential | Looks like a home user, wide location choice | Usually billed per GB, slower than static IPs |
| Datacenter | Fast and cheap | Easier for sites to flag |
| Mobile | Carrier IPs shared by many real users | Costly and slower |
| ISP | Fixed IP that stays yours, fast | One IP per line, not a rotating pool |
For a deeper comparison, read datacenter vs residential proxies and ISP vs residential proxies.
Sticky vs rotating on one endpoint
Backconnect is the access pattern. Sticky and rotating are the session behavior. One gateway can do both:
- No session ID: each new connection can get a different exit. Use this for independent requests.
- Session ID A: every connection with ID A uses the same exit until the session ends.
- Session ID B: a different exit from A, held the same way.
You can check this in a minute. Save one rotating line and one sticky line from your dashboard, then run:
import requests
from urllib.parse import quote
def to_url(line):
host, port, user, password = line.strip().split(":", 3)
return f"http://{quote(user, safe='')}:{quote(password, safe='')}@{host}:{port}"
def exit_ip(proxy_url):
proxies = {"http": proxy_url, "https": proxy_url}
# A new Session opens a new connection, so a rotating line can pick a new exit.
with requests.Session() as session:
return session.get("https://api.ipify.org", proxies=proxies, timeout=20).text
rotating = to_url(open("rotating.txt").readline())
sticky = to_url(open("sticky.txt").readline())
print("rotating:", [exit_ip(rotating) for _ in range(3)]) # usually 3 different IPs
print("sticky: ", [exit_ip(sticky) for _ in range(3)]) # the same IP 3 times
If the rotating line prints the same IP three times, check that each call really opens a new connection. If the sticky line changes IP, the session expired or the exit went offline. For retry logic and session handling in larger scripts, see our guide to rotating proxies in Python.
When backconnect rotating proxies help
A backconnect gateway is easiest when you would otherwise manage a long list of IPs:
- Public-page scraping, where each URL stands alone.
- Search result and price checks across regions.
- Ad verification and localized QA.
- Product monitors that do not log in.
- Jobs that need many countries, states, or cities from one config.
- Tools that accept only one proxy setting but need many exits.
The gateway also handles pool health. When an exit goes offline, the gateway picks another one. With a static list, you find and replace dead IPs yourself.
When not to use a backconnect rotating proxy
Rotation is the wrong default in these cases:
- Login, cart, and checkout without a session ID. If the IP changes between steps, the site can log you out, drop the cart, or ask for verification. Add a sticky session or use a static ISP proxy. Our residential sneaker proxy setup guide shows how retail bots split sticky and rotating sessions by task.
- Sessions longer than the sticky window. If an account must keep one IP for days, a session that ends after 2 hours will change IP under it. Use a static ISP proxy.
- IP allowlists. If a partner API or your own firewall only accepts known IPs, you cannot allowlist a rotating pool. Use a fixed IP.
- Latency-critical work. A residential exit adds a hop through a consumer connection. For fast monitors and first-come checkouts, static ISP proxies are usually more predictable.
- Bandwidth-heavy jobs. Residential gateways are usually billed per GB. Full browser sessions with images and video add up fast. Estimate first with the data usage calculator.
- Fingerprint-based blocks. Rotation changes the IP. It does not change your cookies, browser fingerprint, or TLS signature, so a site that tracks those can still link your requests. See web scraping headers for the request side.
- Rate-limit problems. Rotation spreads requests across IPs, but it does not fix bad retry logic, account limits, or API-key limits.
Backconnect vs static proxies and proxy lists
| Feature | Backconnect rotating proxy | Static proxy |
|---|---|---|
| Endpoint | One gateway for the whole pool | One address per IP |
| Exit IP behavior | Rotates per connection or holds per session | Stays the same |
| Pool management | Provider replaces dead exits | You assign and replace IPs |
| Rotation logic | The gateway does it | You write it, if you want it |
| Best fit | Stateless scraping, monitors, geo checks | Accounts, checkout, allowlists, long sessions |
| Billing | Usually per GB | Usually per IP |
| Main risk | Breaking session continuity | Too much traffic on one IP |
A rotating proxy list works too. Your code picks an IP from the list for each request, drops dead ones, and retries. It costs more code, and you control every choice. A gateway moves that work to the provider.
If you need broad residential rotation, start with residential proxies by location. If you need fixed IPs, compare ISP proxy plans.
Setup and buying checklist
Before you buy or point a tool at a backconnect gateway, confirm:
- Host and port for the mode you want (sticky or rotating).
- Username and password format, including any session suffix.
- HTTP(S) or SOCKS5 support in your tool.
- Location syntax for country, state, or city.
- Sticky session lifetime.
- Whether your client reuses connections.
- Bandwidth limits and pricing.
- Whether the target allows your automation.
- How the provider sources its residential IPs, and whether device owners opt in.
- Concurrent connection limits, and whether unused bandwidth expires.
For the full residential setup, including headers, cookies, and task mapping, read how to use residential proxies. For choosing the session mode in general, read sticky vs rotating proxies.
Troubleshooting a backconnect gateway
| Symptom | Likely cause | Fix |
|---|---|---|
407 Proxy Authentication Required |
Wrong username, password, or parameter syntax | Copy a fresh line from the dashboard |
| Rotating line keeps the same IP | Client reuses one connection | Open a new connection per request |
| Sticky line changes IP | Session ended or the exit went offline | Generate a new sticky line and restart the task |
| Exit in the wrong country | Location parameter missing or misspelled | Check the hostname or username flag |
| Timeouts on some requests | Slow or dropped residential exit | Set timeouts and retry on a new connection |
| 429 from the target | Too many requests per IP or per account | Slow down before you add more exits |
For authentication errors, our guide to 407 Proxy Authentication Required lists the common causes by tool. Log the exit IP, session ID, target URL, and status code for every failure. Without that data, you cannot tell a bad exit from a bad request.
FAQ
What is a backconnect proxy?
It is one gateway address in front of a pool of exit IPs. Your tool connects to the gateway, and the gateway sends each connection out through an exit it picks, or through a pinned exit if you use a session ID.
Are backconnect proxies residential proxies?
They can be. Backconnect is an access pattern, not an IP type. Many residential proxy products use a backconnect gateway, and some datacenter and mobile products do too.
Do backconnect proxies rotate every request?
They rotate per connection. If your client sends many requests through one open connection, those requests share one exit. Open a new connection to get a new exit.
What is the difference between backconnect, rotating, and sticky proxies?
Backconnect describes the gateway. Rotating and sticky describe session behavior. A backconnect gateway rotates by default and turns sticky when you add a session ID.
What is a "reverse backconnect" proxy?
Sellers use the phrase loosely. In most listings it means the same thing as a backconnect gateway. Ask the seller what it does: how exits are chosen, how sessions work, and what the IP type is.
Are backconnect proxies legal?
The technology is legal in most places. What you do through it is what matters. Using a proxy to break a site's terms can get accounts banned or lead to legal trouble, so check the target's rules and local law. Also ask your provider how it sources residential IPs.
Can I use SOCKS5 with a backconnect proxy?
Yes, if the provider supports it. Unknown Proxies residential plans support HTTP(S) and SOCKS. The session and location parameters work the same way.
Final thoughts
A backconnect rotating proxy saves you from managing IP lists. The gateway picks exits, replaces dead ones, and holds a session when you ask it to. Rotation happens per connection and sticky sessions end, so pick the mode per task and test it before you scale. Keep monitors and public scraping on the gateway, and put checkout and account work on a fixed ISP proxy.
Technical references: MDN Proxy servers and tunneling, RFC 9110 section 9.3.6 (CONNECT), RFC 1928 SOCKS Protocol Version 5, and RFC 1929 Username/Password Authentication for SOCKS V5.