A backconnect proxy is a single gateway address that sends each of your requests out through an IP from a pool behind it. You connect to one host and port with one login. The gateway picks the exit: a new one per request, or the same one for a held session. Researchers who studied five such services in 2017 described the same design. The client receives "a gateway's IP address or URL", and the gateway "forwards the client's requests to different residential hosts".
What is a backconnect proxy?
It is the setup most rotating proxies use: one endpoint in front, many exit addresses behind. The word names an arrangement. The gateway itself speaks ordinary HTTP or SOCKS5, the same protocols any proxy speaks.
Backconnect proxy
a proxy setup
One gateway address in front of a pool of exit IPs. You connect to the gateway with one login, and it sends each request out through an exit it picks, for every request or for a held session.
From your side, nothing about the pool is visible. Your tool talks to the same host and port all day, while the address a website sees keeps changing behind it.
Why is it called backconnect?
The gateway connects you back out through one of its exits. A request arrives at the gateway, which forwards it to an exit node, and the exit sends it on to the website. The answer travels back along the same path.
Your client
one host, one port, one login
Gateway
picks an exit from the pool
Exit node
sends the request on
Website
sees the exit's IP address
Where exits are home devices, the connection has to start from the device. A device behind home NAT, or behind a carrier's carrier-grade NAT, cannot be reached from outside unless it connects out first. The IETF found exactly that when it tested applications behind carrier NAT for RFC 7021. Designs that use home devices therefore have the device connect to the gateway first and keep that connection open. The name describes this direction: the connection comes back from the exit to the gateway, which sends your requests down it.
How is a backconnect proxy different from a proxy list?
A proxy list is a set of IP:port lines you load into your tool and rotate through yourself. You also test which ones still answer, drop the dead ones and find new ones. A backconnect proxy moves that work behind one endpoint that stays the same.
A proxy list
A file of IP:port lines
you load and rotate them yourself
You test which still answer
and drop the dead ones
You find new addresses
as the list goes stale
Your code does the rotating
per request or per batch
A backconnect gateway
One endpoint that stays the same
one host stands in for the pool
The seller tests the exits
you see only the line
The gateway rotates
per request or per session
Any tool works
it never sees the exit change
The upkeep is real. On our free proxy list, we followed the proxies that answered between 04:00 and 05:00 UTC on October 17, 2026. Half of them did not answer in the same hour a day later. Our page on proxy rotation shows the full measurement.
Does a backconnect proxy always rotate?
No. Rotation is one behavior a gateway offers, and holding a session is another. The 2017 study found three kinds of gateway. A sticky gateway "always tries to use the same RESIP", meaning the same exit. A non-sticky one "changes RESIP each time after a request is forwarded". A half-sticky one lets the client switch between the two.
Sellers still work this way. Oxylabs and Decodo rotate on every request unless you ask for a session, and hold a session for 10 minutes by default. Seven of the ten sellers we read on October 22, 2026, allow a session of up to 24 hours. Our page on sticky vs rotating proxy sessions compares them. Our page on rotating vs static residential proxies covers when a fixed address is the better buy.
At HProxy a line rotates unless you set a session length. Residential Premium takes any length from 3 to 1,440 minutes, and Residential Lite holds its address while you keep using the line.
Is a backconnect proxy the same as a rotating proxy?
They describe two sides of one product. Backconnect names the setup, a gateway in front of a pool. A rotating proxy names what you buy, an address that changes for you. A rotating proxy sold as one host and port runs on a backconnect gateway. A gateway that holds sticky sessions can also give you one steady exit for a while.
Is a backconnect gateway a reverse proxy?
No, despite the word gateway. RFC 9110 calls a proxy "a message-forwarding agent that is chosen by the client". That describes a backconnect gateway: you choose it and point your tool at it. RFC 9110 uses gateway, or reverse proxy, for something else: an intermediary that stands in front of a website's own servers. Sellers call their entry point a gateway, but it works for you, the client.
How do you connect to a backconnect gateway?
You need a host, a port and a way to prove who you are. Two ways are common:
- A username and password sent with each connection. Most sellers put the session and the country into the username, so each line carries its own settings.
- An IP allowlist. You register your server's address, and the gateway accepts connections from it without a password.
At HProxy you copy a full line from the dashboard. You can also generate lines through the API with the country, session length and protocol you want. Residential Premium also accepts an allowlist of up to 150 IP addresses per plan. A line looks like this, with your own login in place of the placeholders:
curl -x http://YOUR-LOGIN:YOUR-PASSWORD@premium.hproxy.com:10000 https://icanhazip.com
Lines come as HTTP or SOCKS5. The 2017 study notes one more setting some gateways offer: whether the target's name is looked up by the gateway or by the exit. With SOCKS5, RFC 1928 lets the client hand over a host name for the proxy side to resolve.
How many IPs are behind a backconnect gateway?
You cannot count them from outside, and sellers count in different ways. Oxylabs explains its own method: it multiplies its "Residential Proxy pool, unique exit node number per day, and days in quarter". Bright Data quotes a monthly figure. Archived copies of sellers' homepages show how fast the quoted numbers have grown:
- Earliest archived claim
- Claim in 2026
The one outside count we know of is old. The 2017 study sent 62 million requests through five services and saw 6,183,876 different exit IPs in about four months. For one seller that then claimed 30 million IPs, the researchers "only found 4 millions using 16-million probings". They also found that "a significant portion (90%) of the RESIP IPs exhibit a short relaying time (870 seconds)". Many exits, they reported, ran on likely compromised hosts, including IoT devices.
A pool size is a count over a time window that each seller chooses. What you can check is narrower: whether your target accepts the exits you get, in the country you need.
When is a backconnect proxy the right choice?
A gateway suits any job that sends many requests and benefits from spreading them: price and stock monitoring, search results, ad checks across countries. Your code stays simple, because the rotation happens behind one address.
It is the wrong choice when you need one identity that never moves. An account that must look like the same person every day is the usual case. A static ISP proxy keeps one address for as long as you hold it. Exits behind a gateway can also drop mid-request, so build retries into your code from the start.
Our backconnect residential proxies page lists what our gateway offers. Our residential proxies are billed per GB from $0.44/GB at 2,000 GB+, or $1.00/GB at 1,000 GB+ on Residential Premium. Check which address a line exits from with our proxy checker. Our guide to what a residential proxy is covers the address side. Our page on what a rotating proxy is covers the product most gateways sell.
What this page could not check
- No gateway tests. We did not test any seller's gateway, ours included, so nothing here measures how often a gateway changes exits.
- Claims, not counts. The pool sizes in the chart are what sellers' pages say. We cannot verify them, and each seller counts over its own window.
- An old outside count. The only independent measurement we cite is from 2017, published in 2019.
- Check by January 22, 2027. Session defaults, pool claims and sellers' authentication options change.
Sources
- Resident Evil: Understanding Residential IP Proxy as a Dark Service. Mi and others, IEEE Symposium on Security and Privacy, 2019.
- RFC 7021: Assessing the Impact of Carrier-Grade NAT on Network Applications. IETF, September 2013.
- RFC 1928: SOCKS Protocol Version 5. IETF, March 1996.
- Residential proxy pool FAQ (Oxylabs), read October 22, 2026.
- Sellers' archived and live homepages (Bright Data, Oxylabs, Decodo, DataImpulse, Webshare, NodeMaven), read September 26 to October 14, 2026.
- Session documentation of ten sellers, read October 22, 2026, for our page on sticky vs rotating proxy sessions.
- HProxy API documentation and residential product page, read October 22, 2026.
- HProxy free proxy list, checks of October 17 to 22, 2026.
