Operations

What is Backconnect Proxy?

A backconnect proxy is a single hostname and port that fronts a pool of many IP addresses. The client keeps one connection string while the provider's gateway assigns a different exit IP per request, per session or on a timer. Rotation and pool health checks happen upstream, where the client cannot see them.

The client's configuration points at one hostname and port, something like gw.provider.net:10000, with a username and password. That gateway terminates your TCP connection and relays traffic through an exit node it picks from the pool. Two addressing styles are common. Port-based gateways map each listening port to a policy, such as a country or a rotation interval, so you change behaviour by changing ports. Credential-based gateways encode the same parameters inside the username string, in fields for country, city, ASN or a session identifier that the provider parses when you connect.

Rotation happens at connection boundaries, not at arbitrary points inside a stream. For plain HTTP the gateway can choose a new exit per request. For HTTPS the client issues a CONNECT and everything after that rides one tunnel bound to one exit, because the TLS session belongs to that upstream socket. Keep-alive changes the arithmetic again, since several requests reusing an open tunnel share an address. If you want a different IP on every request, close the connection between requests or ask the gateway for a fresh session token.

Debugging is harder than with a static proxy because you cannot see the exit address directly. Call an IP echo endpoint through the same session, or read whatever response header the provider stamps with the assigned IP. You also cannot allowlist an exit at the target site, so IP allowlisting covers only the hop between you and the gateway, and the rest runs on username authentication. The gateway enforces concurrency caps and geo filters of its own, which means an error you receive may have come from the gateway rather than the site.

Learn to separate those two error sources early. A 407 is the gateway rejecting your credentials. A 502 or an abrupt reset usually means no healthy exit was available, while a 403 or 429 carrying the target's own HTML is the site talking. Billing splits along a similar line, between metered traffic and whatever the provider charges for access points. PROXIES.SX meters gigabytes only, from $4/GB down to $2.40/GB at volume, with endpoints and rotation included and no per-port fee.

Where you meet it

You meet a backconnect gateway the first time you buy from a rotating provider and receive one host, one port and a credential pair instead of a list of IPs. The decision it forces is how much control you hand upstream, because rotation policy, geography and session length now live in the connection string. Your retry logic has to work with the gateway's behaviour rather than around it, so test with an IP echo call before wiring it into a running job.

Common questions

How is a backconnect proxy different from a proxy list?

A proxy list gives you many host:port pairs and leaves you to rotate them and health-check them yourself. A backconnect gateway does that work upstream. You trade visibility into individual IPs for a configuration that stays valid when the underlying pool changes, which it does constantly on mobile and residential networks.

How do I keep the same IP on a backconnect proxy?

Ask for a sticky session. Most gateways accept a session identifier inside the username or publish separate sticky ports, and they hold one exit for a fixed window that ranges from a few minutes to around an hour depending on the provider. The address can still change early if the underlying device leaves the network.

Why does my exit IP stay the same across several requests?

Connection reuse. HTTP keep-alive and an open CONNECT tunnel both keep traffic on one upstream socket, and the gateway picks the exit when that socket opens. Close the connection between requests, or change the session token if you need a new address each time.

Related terms

Rotating Proxy
A rotating proxy changes the exit IP address it presents to the target, either on every request or on a timer, without the client changing its configuration. Your code keeps pointing at one host and port; the provider swaps the address behind it, spreading traffic across a pool of many IPs.
Proxy Pool
A proxy pool is the set of IP addresses a provider can route your traffic through. Its usefulness comes from composition as much as from size: how many distinct subnets and autonomous systems it spans, how many countries it reaches, how heavily each address is reused, and how clean those addresses look to the sites you target.
IP Rotation
IP rotation is the practice of changing the outbound address a client uses, on every request, on a timer, or on demand. It spreads traffic so no single address builds up enough volume to be rate limited or banned, and it is the defining behaviour of rotating and backconnect proxy services.
Session
In proxy usage, a session is a span of requests that all exit through the same IP address. It begins when you open a connection or claim a session identifier, and it ends when that identifier's timer expires or the network reassigns the address underneath you. Session control is what separates rotating traffic from a continuous identity.
Sticky Session
A sticky session is a proxy configuration that pins your traffic to one exit IP for a fixed window instead of rotating on every request. You request it through a session identifier in the username or through a dedicated port, and the gateway routes each matching request back to the same node until the timer runs out.
Geotargeting
Geotargeting is choosing which country, region, city or carrier your proxy traffic exits from, so a site sees a visitor located where you want. You select it through parameters in the proxy username, a country-specific hostname, or a dedicated port, and the site reads that exit IP against whichever geolocation database it uses.
Geo-Restriction
Geo-restriction is a service limiting access or content by the visitor's apparent location. The site maps the client IP to a country through a geolocation database, then blocks the request or quietly swaps in a regional catalogue with local pricing. Content licensing, sanctions rules, tax registration and commercial strategy are the usual reasons.
Concurrent Connections
Concurrent connections are the number of proxy connections open at the same moment, counted across your workers rather than over a period. It is a capacity limit, separate from requests per second and from bandwidth. Ten connections can carry thousands of requests an hour when each is short, or almost none when each holds a slow page open.

Real 4G/5G mobile and residential IPs

PROXIES.SX runs carrier IPs in 100+ countries with HTTP and SOCKS5 on every endpoint. $4/GB down to $2.40/GB at volume, free endpoints and rotation, and your GB never expire.

View pricing Browse the glossary