Carl Gamutan
Updated: September 10, 2026
Published: July 31, 2022
When connecting to a proxy server, users are given one of two things: A proxy list or a backconnect proxy. A proxy list is for static proxies, and a backconnect proxy is for rotating proxies. In this article, we’ll be discussing what backconnect proxies are, how they work, their advantages, and their disadvantages.
A backconnect proxy is a single gateway address that connects you back out through a pool of many different IPs, instead of handing you the addresses themselves. You point your software at one host and port, and the provider decides which address in the pool actually carries each request.
The name describes the architecture; the behaviour you observe is usually called rotation, which is why "backconnect rotating proxies" is one product and not two.
Every request you make travels to the gateway first. The gateway authenticates you, selects an exit address from the pool behind it, and opens the outbound connection from that address. The response comes back along the same path. Your client never learns which address was used and never needs to.
That indirection is the entire benefit. Without it, using a thousand addresses means maintaining a list of a thousand host-port-credential triples, checking which are alive, retiring the dead ones and rebalancing traffic across the rest. With a backconnect gateway, your configuration is one line and stays one line whether the pool holds a hundred addresses or millions.
The pool itself is where the addresses come from. Geonode's residential network — the gateway most people mean by "backconnect" — reports 5M IPs online at any moment and 30–50M unique addresses cycling through monthly across 195+ countries on the residential proxies page. Country targeting is a parameter on the endpoint, so narrowing to one market does not change how you connect.
To the destination, each request looks like an unrelated visitor on a home connection, because that is literally where the exit address lives. There is no accumulating per-IP history for the site to rate-limit, which is why backconnect gateways are the standard tool for collection at volume.
What the gateway does not do is preserve state for you by default. If a flow needs the same address from beginning to end, you ask for a sticky session when you build the endpoint — the residential FAQ states these can be configured for up to 24 hours — and the gateway pins one address to your session for that window.
| Backconnect | Rotating | Static (ISP or dedicated) | |
|---|---|---|---|
| IP source | Pool behind one gateway | Pool behind one gateway | One assigned address |
| Static or rotating | Rotating, sticky on request | Rotating, sticky on request | Static |
| Shared or exclusive | Pool shared across customers | Pool shared across customers | Exclusive to your account |
| Detection risk | Low — no per-address history builds up | Low | Low, but the single address carries all your history |
| Price model | Per GB | Per GB | Per IP, unlimited bandwidth |
| Best for | Large crawls without managing IP lists | The same job, described by behaviour | Logins and anything that must stay recognisable |
The first two columns are the same product. "Backconnect" answers how is this built; "rotating" answers what does it do.
They fit when:
They are the wrong choice when:
The backconnect gateway at Geonode is the residential proxies endpoint — one host and port, country targeting, rotating or sticky mode, priced from $0.27 per GB with no monthly minimum on that page. Setting it up is a matter of choosing the location and session type, then pasting the endpoint string into your script; there is no address list to maintain on your side.
If the target does not care whether the exit address belongs to a home connection, the same gateway pattern is available on cheaper infrastructure through rotating datacenter proxies, from $0.144 per GB. You give up the residential appearance and keep the single-endpoint convenience. They remain the better option for most advanced use cases where throughput matters more than how the address looks.
Not in practice. Backconnect describes the gateway architecture and rotating describes the resulting behaviour; vendors use the terms for the same offering.
No, and that is the point. You get one gateway endpoint; the pool sits behind it and the provider handles which address serves each request.
Yes, by requesting a sticky session when you build the endpoint. The residential proxies FAQ states sticky sessions can be configured for up to 24 hours.
Yes — the gateway model is what makes large residential and mobile pools usable at all, since those addresses are too numerous and too short-lived to hand out as a list.
