Skip to main content
Targeting is controlled entirely through username modifiers. No separate endpoints per country.

Format

Each level is independent — stop wherever you need to. To get a random IP at a broader level, just omit the narrower modifier.

Country targeting

Use any ISO 3166-1 alpha-2 country code. Lowercase.
Match the regional gateway to your target country for lowest latency.

State targeting

Available for countries with state / regional subdivisions (US, Canada, Australia, Germany, Brazil, etc.).
Omitting city- means “any city in that state” — the network picks one at random.

City targeting

Append -city-<n> for a specific city. Lowercase and concatenated. City targeting works with or without state-:
Add state- only when two cities share a name across states (e.g. “Springfield”).

City name format

  • All lowercase
  • No spaces, apostrophes, or hyphens (concatenate): westlakevillage, sanfrancisco, newyorkcity
  • Accents stripped: zurich not zürich

ASN targeting

asn-<number> pins your IP to a specific ISP by its Autonomous System Number. Useful for ad verification on specific carriers, CDN peering tests, or simulating traffic from a particular network.

Common US ASNs

Find the ASN for any IP using whois, bgp.he.net, or ipinfo.io.

Stacking ASN with geo

The narrower the combined targeting, the smaller the pool. For high-concurrency workloads, keep at least one level wide.

Targeting granularity cheat sheet

Combining with sessions

Pins a Westlake Village IP for 15 minutes. See Sessions.

Quick-copy host:port:user:pass

Troubleshooting

Country code isn’t recognised. Use lowercase ISO 3166-1 alpha-2 (us, not US or usa).
State code not recognised for that country. Use standard subdivision codes (e.g. ny, ca for US states; on, qc for Canadian provinces).
City isn’t recognised, or no IPs available. Check the city name is lowercase and concatenated. If valid but low availability, drop the city- modifier.
ASN not in supported set, or no IPs for the combined geo + ASN. Verify with whois or bgp.he.net and try widening geo targeting.
Narrow targeting = smaller pool. Widen to state or country level, or split workloads across regional gateways.