Guides 4 min read

What Is a Backconnect Proxy? The Gateway Behind Rotating IPs

A backconnect proxy is one address that connects you out through many others. Here's what happens inside the gateway and how to steer it from your username.

A backconnect proxy is a single proxy endpoint that connects your traffic out through a large pool of other IP addresses. You always point your tools at the same host and port; behind it, a gateway picks an exit IP for each connection and relays your traffic through it. The name comes from how the exits work: the gateway connects back to the exit nodes and hands them your traffic, instead of you connecting to each node directly. Nearly every rotating residential and mobile proxy service is built this way.

Backconnect vs a Proxy List

The older model is a proxy list: you receive hundreds of lines of ip:port:user:pass and your code rotates through them. A backconnect proxy replaces the list with one line.

  • Proxy list: your code picks the IP, tracks which ones are dead or banned, and spreads load. Lists go stale as IPs drop off.
  • Backconnect: the gateway picks the IP, routes around offline exits and gives you access to the whole pool, which can be millions of addresses.
  • Proxy list: changing country means getting a different list.
  • Backconnect: changing country means changing a word in the username.

If a tool insists on a list format, you can still feed it the same gateway line many times with different session IDs, or convert formats with the proxy format converter.

What Happens Inside the Gateway

  1. Your client connects to the gateway (for NodeProxies, global.nodeproxies.xyz on 8080 for HTTP or 1080 for SOCKS5).
  2. The gateway authenticates you and parses the options embedded in your username.
  3. It selects an exit from the matching part of the pool: right product, right country, and the same exit as before if your session ID is already mapped.
  4. It opens the connection to the target through that exit and relays bytes both ways.
  5. It counts the bandwidth against your plan. If the plan is empty you get a 402; if the credentials are wrong or the plan is inactive, a 407.

Controlling a Backconnect Proxy Through the Username

Because there's only one host and port, options travel in the username. On NodeProxies:

# New IP every request, any country
USERNAME

# New IP every request, United States only
USERNAME-country-us

# One of several countries
USERNAME-country-us,gb,de

# Same German IP for 15 minutes under session id "job7"
USERNAME-country-de-session-job7-time-15

The proxy username builder generates these strings so you don't have to remember the syntax.

Why Providers Use Backconnect Gateways

  • Residential and mobile exits come and go as devices connect and disconnect. A gateway hides that churn from you.
  • The pool can be far larger than any list you could manage.
  • Targeting and sessions are applied centrally and consistently.
  • Billing by bandwidth is straightforward because all traffic passes through one place.

Things to Know When Using One

  • Latency is a bit higher than a direct proxy, since there's an extra hop through the gateway. For residential traffic it's small compared with the home connection's own latency.
  • Rotation is per connection. Keep-alive can keep you on one exit for several requests; see proxy IP not changing.
  • A sticky session can end early if the exit device goes offline. Build retries that open a new session instead of failing the job.
  • Errors can come from two places: the gateway (407, 402) or the target via the exit (403, 429, 502). Our proxy error 502 guide explains how to tell them apart.

Running Many Sessions Through One Gateway

Since sessions are just strings, you can run hundreds in parallel through the same host and port. A common pattern is one session ID per worker or per browser profile, such as worker-01 to worker-50, each with a time that covers its task. The gateway keeps each mapped to its own exit, so fifty workers look like fifty separate visitors, and you never maintain a list of IPs yourself.

Testing a Backconnect Proxy

for i in 1 2 3; do
  curl -s -x http://USERNAME-country-gb:[email protected]:8080 https://ipinfo.io/json | grep -E '"ip"|"country"'
done

Three runs, three different UK IPs, same endpoint. Add -session-t1-time-5 to the username and all three runs return the same IP. More checks are in how to test if a proxy is working.

Backconnect Proxies on NodeProxies

All NodeProxies products, from rotating residential to mobile and datacenter, use the same backconnect gateway and username options, so switching product means switching credentials, not code. Plans are pay as you go with no expiry on balance; see pricing or register.

FAQ

Is a backconnect proxy the same as a rotating proxy?

Almost always in practice. Backconnect describes the gateway architecture; rotating describes the behaviour it enables. See what is a rotating proxy.

Can I get a static IP from a backconnect proxy?

You can hold one IP with a sticky session for a set time, but the address isn't reserved for you permanently.

Why is it called backconnect?

Because the gateway connects back through exit nodes on your behalf, rather than you connecting to each proxy IP directly.

Do backconnect proxies support SOCKS5?

Many do. NodeProxies accepts SOCKS5 on port 1080 with the same username options as HTTP.

NodeProxies

Ready to get started?

90M+ residential, mobile & datacenter proxies. Datacenter from $0.30/GB, residential from $0.42/GB. No contracts.

Create free account