← Back to the blog Engineering 
How smart routing balances success rate, latency, and customer exclusions
Inside the selector: how each connection is weighted using live health, latency, and your own rules.
· 7 min · ProxyAPI
01
One endpoint, multiple routes
You always connect to the same gateway. Behind it, the selector maintains a current view of available exits and chooses a route that matches proxy type, country, provider, and session.
02
Health beats chance
Each exit receives a weight based on success rate, latency, active load, and recent health checks. A weak exit gradually leaves rotation instead of making the whole pool unreliable.
03
You still stay in control
Add modifiers to the proxy username when you need a particular type or a sticky session. You can also exclude an exit that consistently fails against your specific target.
curl -x 'https://sk_live_YOUR_KEY-country-se-type-isp-session-job42:@proxy.proxyapi.se:443' https://example.com