Gateway proxy
A single entry point that routes your traffic into a whole pool of exit IPs, so you connect to one address and reach many.
A gateway proxy is the connection model behind essentially every rotating residential service, and understanding it removes most of the confusion people have about how rotation works. Instead of handing you a list of individual addresses to manage, the provider gives you a single host and port. The entire proxy pool sits behind that one endpoint, and the gateway decides which exit each request leaves from.
This is what makes rotation effortless on your side, and it is a genuinely elegant piece of design. You configure one endpoint once and never touch it again. The switching happens on the provider's side, addresses can be added or retired underneath you with no effect on your setup, and a pool of thousands is operated through a single line of configuration.
The targeting rides along in the credentials rather than in the address, which is the part that surprises people. Country, city, ISP and session length are expressed as modifiers on the username, so requesting German traffic instead of American traffic changes a credential and leaves the host and port exactly as they were. One endpoint, every location.
The consequence that trips everyone up is that the gateway address is NOT the address a website sees. Your traffic enters at the gateway and leaves at a pool member, so the destination records the exit node. Looking up the gateway hostname tells you where the provider's infrastructure sits and nothing whatsoever about your apparent location, which is the single most common piece of mistaken testing we encounter.
It has a practical implication for reliability too. Because everything funnels through one endpoint, the gateway is a dependency in a way individual addresses are not: if it is unreachable from your network, the entire pool is unreachable, no matter how healthy the addresses behind it are. That is normally a non-issue, and it is worth knowing when a restrictive network blocks the port the gateway listens on.
Frequently asked questions
Why does the gateway IP differ from what websites see?
Because they are different points in the path. The gateway is where your traffic enters the network; the exit node is where it leaves for the destination. Sites only ever see the exit. Testing the gateway hostname tells you where the provider's infrastructure sits and nothing about your apparent location, which is why country targeting so often looks broken when it is working fine.
How does the gateway know which country I want?
From your credentials. Targeting is expressed as modifiers on the username, so a request for a specific country, city or session length is encoded there and read by the gateway when it selects an exit. That is what allows one unchanged host and port to serve every location a provider offers.
Is a gateway proxy the same as a backconnect proxy?
The terms are used interchangeably. Backconnect describes the behaviour, that you connect to one point and it connects onward on your behalf, while gateway describes the endpoint you connect to. Both refer to the same arrangement of one entry point in front of a rotating pool.
What happens if the gateway goes down?
You lose access to the whole pool, because everything reaches it through that one endpoint. This is the trade for the convenience of a single unchanging configuration. In practice gateways are redundant infrastructure, and the more common cause of unreachability is a restrictive network blocking the port on your side rather than an outage on theirs.
Back to the full glossary.