Proxy provider selection
KERNEL routes residential proxy traffic across multiple providers. This expands destination coverage and makes the proxy network more reliable. For each session, KERNEL chooses one of the proxy providers to be the preferred provider for that session, based on KERNEL’s desired proxy traffic split. When making a connection through the proxy network to a target site, KERNEL will choose a different provider for this connection than the session’s default if the default does not support the target destination or provider has an outage. Different destinations within a browser session may use different providers.IP consistency
- Open connections stay on their current provider and exit IP. Routing updates affect new connections rather than interrupting open ones.
- New connections may use a different exit IP because of failover, routing updates, sticky-session expiry, or residential device availability.
- Different destinations may use different providers and exit IPs within the same browser session.
Configuration
Create a residential proxy with a target country:Configuration Parameters
country- ISO 3166 country code. Must be provided when providing other targeting options.state- Two-letter state code. Only supported for US.city- City name (lowercase, no spaces, e.g.,sanfrancisco,newyork).zip- US ZIP code (5 digits). Can only be used withcountryset toUS. Cannot be combined withcityorstate.asn- Autonomous System Number. Conflicts with city and state.bypass_hosts(optional) - Array of hostnames that bypass the proxy and connect directly (max 100 entries)
Advanced Targeting Examples
Kernel recommends using the least-specific targeting configuration that works for your use case. The more specific a configuration, the less available IPs there are, increasing the chance of a slow connection or no available connection (no_peer connection error).
Target by City
Route traffic through a specific city:If the city name is not matched, the API will return the best 10 city names from the state to help you find the correct city identifier.
Target by State
Route traffic through a specific state:If the state name is not matched, the API will return the most-available 10 states.
Target by ASN
Route traffic through a specific Autonomous System Number (ISP):If the ASN is not matched, the API will return the most-available 10 examples.
Target by ZIP code
Route traffic through a specific US ZIP code area:ZIP code targeting is US-only and cannot be combined with
state or city. The exit IP will be in the geographic area of the requested ZIP code, but the IP’s exact ZIP may differ slightly (e.g., requesting 90210 may route through 90401 in the same metro area)..gov support
Residential proxies with no targeting, country-only targeting, or US state targeting automatically route.gov requests through a compatible upstream provider. ZIP, ASN, and non-US state targeting may return restricted_route_unavailable.
You may check proxy health against a .gov URL before starting a browser.