Proxy backconnect
Una arquitectura de proxy donde un único endpoint gateway enruta las solicitudes a través de un pool rotativo de IPs backend.
Un proxy backconnect (también llamado proxy gateway) te da un endpoint al que conectarte, mientras que el backend del proxy rota por un pool de IPs en cada solicitud. Configuras un host y un puerto; la rotación ocurre de forma invisible en la infraestructura del proveedor.
Sin backconnect, los proxies rotativos requerían gestionar una lista de cientos o miles de IPs de proxy individuales, comprobar cuáles siguen funcionando y programar tú mismo la lógica de rotación. La arquitectura backconnect traslada todo esto al lado del servidor.
El término "backconnect" describe la arquitectura: tu cliente se conecta hacia delante al gateway, y el gateway se conecta hacia atrás a través de una IP distinta de su pool en cada solicitud. Desde la perspectiva del sitio objetivo, cada solicitud viene de una IP diferente - pero tú solo te conectas a un endpoint.
Los proxies backconnect son lo que la mayoría de los proveedores modernos ofrecen como su producto estándar. Cuando alguien dice "proxies residenciales rotativos", normalmente se refiere a una arquitectura backconnect con un pool de IPs residenciales.
La implicación práctica: nunca necesitas conocer las IPs individuales del pool, nunca necesitas probar cada una, y nunca necesitas gestionar los fallos de IP en tu código. El gateway maneja la conmutación por error automáticamente.
One door, many exits
A backconnect proxy is a single entry point that hides a pool behind it. You always connect to the same hostname and port. The gateway then chooses an exit device according to whatever targeting you asked for and forwards your traffic through it. Your address changes; the address you dial does not.
The alternative is a list: a file of individual addresses, each of which you connect to directly. Lists give you exact control over which exit you use and require you to manage rotation, health checks and replacement yourself. Backconnect trades that control for the pool being someone else's problem.
The design exists because residential exits are unreliable by nature. A home device drops off, and a list entry pointing at it becomes dead weight. A gateway simply picks a different device on your next connection, and you never learn that anything happened.
Control comes back through parameters rather than address selection. Instead of choosing an exit, you describe one: this country, this city, hold it for fifteen minutes. The gateway matches your description to whatever is online.
Our gateway and what you can ask it for
The residential endpoint is a backconnect gateway. Everything you control lives in the login string:
Same door, different exits
proxy.sotaproxy.com:10000 the door, always the same
login any exit, new one per request
login_c_DE an exit in Germany
login_c_DE_city_Berlin an exit in Berlin
login_c_DE_s_7_ttl_1h hold one Berlin-area exit for an hour
# Our ISP, datacenter and IPv6 products are the opposite model:
# a list of addresses you connect to directly.- Because the gateway address never changes, firewall rules and antidetect profiles keep working when your exit address rotates.
- Concurrency is not limited by the number of addresses you own. Hundreds of parallel connections through one gateway is normal usage.
- A 502 from the gateway means it could not find an exit matching your description, which is a stock problem rather than a fault in your setup.
- If you need to know your exact exit address, ask for it: request api.ipify.org through the same session before you start the real work.
Backconnect versus a list
One gateway line is not one proxy
Ten copies of the same line in an antidetect browser give ten profiles the same treatment, and without different session ids they can land on the same exit.
You cannot pin a specific IP
Sticky sessions hold whatever the gateway picked, not an address you chose. If you need a known, unchanging address, buy an ISP or datacenter proxy instead.
The gateway address is not your exit
Whitelisting proxy.sotaproxy.com at a destination does nothing, because your traffic arrives from the exit device, not from us.
Rotation is not automatic in the way people expect
A new exit is chosen per connection, not per request in a keep-alive session. Long-lived connections stay where they started until they close.
Términos relacionados
Ver esto en práctica
¿Listo para usar proxy backconnect?
SotaProxy te da acceso a proxies residenciales rotativos, móviles, de centro de datos e ISP. Sin compromiso mínimo.
Empezar