A backconnect proxy is a single gateway address you connect to while the provider assigns the actual exit IP behind it. Your client always talks to one host and port; the pool of real devices or servers behind that host changes per request, per timer, or per session, according to how you configure it. "Backconnect" describes the connection model, not the IP quality: the exits behind a gateway can be datacenter, residential, or mobile.
How a backconnect proxy works
On every request, the same sequence runs:
- Your client opens a connection to the gateway host and authenticates (username and password, or an IP allowlist).
- The gateway reads your targeting and session instructions from the credentials you sent.
- The gateway forwards the request through a node in the pool and returns the response. The target site sees the node's IP, not the gateway's.
Because the routing decision is made per connection, you never touch individual IPs. You do not receive a list of addresses, you do not manage node failures, and you do not reconfigure anything when the pool changes. That is the entire value proposition: one endpoint, thousands of exits.
The trade-off is real: you give up direct control over individual IPs. You cannot pin a specific IP by address, only ask for the same IP again by session ID, and you cannot see which node served a request unless you check your exit IP yourself.
Backconnect gateway vs a proxy list
A classic proxy list gives you ip:port pairs, one per IP, and your code picks one. A backconnect gateway gives you one host:port and moves the selection logic server-side.
| Backconnect gateway | Static proxy list | |
|---|---|---|
| What you configure | One endpoint plus parameters | Every IP individually |
| Rotation | Server-side: per request, per interval, or sticky | Your own code cycles the list |
| Pool changes | Invisible, no client changes | Dead IPs must be pruned manually |
| Same IP twice | By session ID, for a limited window | By address, indefinitely |
| Debugging a bad exit | Requires logging the exit IP yourself | You already know which IP failed |
Both models can be rotating. Both can be sticky. "Backconnect" and "rotating" get used interchangeably in marketing copy, but they answer different questions: backconnect is where you connect, rotating is how often the exit changes.
Types of exits behind a backconnect gateway
- Datacenter: fast and cheap, easy for platforms to classify by ASN.
- Residential: home ISP addresses, harder to classify, sourced from consumer devices. See what a residential proxy is for the sourcing and trade-off detail.
- Mobile: real 4G/5G devices behind carrier NAT, so hundreds of real subscribers share the same public address as you.
The exit type, not the backconnect architecture, decides whether a request survives. The three types differ in cost, speed, and how a platform reads them, which is covered in the datacenter vs residential vs mobile comparison.
Controlling rotation and geo through the gateway
On VoidMob's shared mobile pool, the gateway is proxy.voidmob.com:10092 and every instruction rides in the proxy username as underscore parameters:
curl -x "http://<username>_c_US_s_run1_ttl_30m:<password>@proxy.voidmob.com:10092" \
https://ipinfo.io/json
_c_UStargets a country using an uppercase ISO code._city_New-York,_zip_, and_asn_narrow it further._s_run1pins the session: every request carrying that ID exits from the same device. Change the string to get a new device._ttl_30msets how long the pin holds. Without a TTL, a session expires after 60 minutes of inactivity.- Leave
_s_off entirely and you get per-request rotation, a different device on every call.
Flex credentials are issued per package from the API, so a gateway string is not usable until the package is provisioned. If you prefer configuration over per-request parameters, named proxy lists set geo and rotation once as fields (rotation_period_seconds of 0 for per request, -1 for sticky, or N seconds) and hand back ready-made credentials on port 10000. Do not mix the two mechanisms in one setup: a username suffix on a list credential is not how a list resolves geo.
For login flows, checkout flows, and anything multi-step, use the sticky path. Sticky sessions on a mobile proxy covers how long to hold a pin per workload. For independent page fetches, per-request rotation is the default and the cheaper option, detailed in USA rotating proxies.
What a backconnect gateway hides from you
This is the part vendor pages skip. Because one hostname fronts the pool, three failure modes look identical from your side:
- A bad exit, not a bad target. A 403 can mean the site blocked you or that the gateway handed you a node with poor reputation. Log the exit IP on every request. Without it you cannot tell a systemic block from one unlucky node.
- Silent re-pinning. If the device holding your sticky session drops off the carrier network, the gateway assigns a new one and your IP changes mid-flow. Verify the exit at the start of a session and again mid-run. The
_rotm_parameter sets what happens when a node drops (0 for an instant swap, 1 for a five-second delay, 2 for no rotation); it does not control how often exits rotate. - Geo drift inside a country. Country-level targeting can put you on a different city and carrier between requests. If the response depends on locale (prices, local search results, ad placement), pin the session and target the city, not just the country. Ad checks in particular need a stable city plus carrier, which is why mobile proxies for ad verification treats pinning as mandatory rather than optional.
Decision rule: gateway or a fixed device
Use a backconnect gateway when the work is many short, independent requests across many IPs: crawling, price checks, search result sampling, survey routing, QA across regions. Metered GB pricing fits that shape, because you pay for traffic rather than for idle IPs.
Use a dedicated device instead when one identity must keep one IP for weeks: a social account, a marketplace seller login, a payment profile. On a dedicated 4G/5G device you own the rotation trigger, so every session is sticky until you rotate it. The full split is in dedicated vs shared mobile proxies.
What backconnect proxies cost
Backconnect pools are usually sold by traffic, so the meaningful number is price per GB, and it drops as the package grows. VoidMob shared packages start at $3.99 for 1 GB and fall to $2.50 per GB at 100 GB. Dedicated devices are billed per device per term instead, starting at $49 per month depending on country.
Mobile proxy pricing
Shared pools from $3.99/GB, dedicated devices from $49/mo.
| Data | Price | $ / GB | Valid |
|---|---|---|---|
| 1 GB | $3.99 | $3.99 | 30 days |
| 25 GB | $81.25 | $3.25 | 30 days |
| 100 GB | $250 | $2.50 | 30 days |
Prices updated
If you are pricing a gateway against other vendors, per-GB rate alone is misleading: check whether sticky sessions, city targeting, and concurrency are included or metered separately. That comparison, vendor by vendor, is in best Decodo alternatives.
1Is a backconnect proxy the same as a rotating proxy?
Not quite. Backconnect describes the single gateway endpoint you connect to. Rotating describes how often the exit IP changes. Most backconnect gateways rotate by default, but the same gateway can also hold one IP for a session, which makes it sticky rather than rotating.
2Can I control rotation manually on a backconnect gateway?
Yes. Attach a session ID to your credentials and every request with that ID uses the same exit until the session TTL expires. Change the ID and you get a new exit. On a dedicated device you rotate on demand via an API call or your own timer instead.
3Can I choose the geolocation of a backconnect proxy?
Yes, at country level and usually narrower. On the VoidMob flex gateway you chain country, city, ZIP, or ASN parameters onto the username; on a named proxy list you set the same targeting as fields when the list is created.
4How do I enable a backconnect proxy in my client?
Point the client at the gateway host and port and supply the username and password issued with your package. Anything that accepts an HTTP or SOCKS5 proxy works, including browsers, Playwright, Selenium, and HTTP libraries. The SOCKS5 port is issued per order with your credentials rather than fixed.
5Do backconnect proxies work for logged-in accounts?
Only with a sticky session. Per-request rotation changes the IP mid-flow, which platforms read as session hijacking. Pin one session per account, or use a dedicated device so the IP stays constant between logins.
One gateway, real 4G/5G exits
Pay-per-GB pools with per-request or sticky sessions, or a dedicated device you rotate on your own schedule.