Skip to main content
Mobile proxies route traffic through mobile carrier networks. Only recommended in advanced stealth use cases.
Mobile carrier IPs often route through shared regional gateways. Country targeting is the most reliable option; city and US state targeting are best-effort and may not match every third-party geolocation database.

Configuration

Create a mobile proxy with a target country:

Configuration parameters

  • country - ISO 3166 country code. Must be provided when providing other targeting options.
  • state - US-only two-letter state code. Best-effort for mobile proxies.
  • city - Provider city alias, such as brooklyn or chicago. Best-effort for mobile proxies.
  • bypass_hosts (optional) - Array of hostnames that bypass the proxy and connect directly (max 100 entries)

Advanced targeting examples

Target by city

Route traffic through a specific city:
If the city alias is not matched, the API returns examples from the target state to help you find the correct value.

Target by state

Route traffic through a US state:

Restricted destinations

Mobile proxies don’t route restricted destinations automatically. Kernel attaches the provider that carries .gov, country government domains, and a set of banking, payment, and postal destinations to residential proxies only, so those requests from a mobile proxy fall back to the default provider, which carries some of them and returns a 502 on the rest. If your workload targets them, use a residential proxy with no targeting, country-only targeting, US state targeting, or city targeting.

Bypass hosts

Configure specific hostnames to bypass the proxy:
See the overview for full bypass host rules and examples.