Troubleshoot Proxy Location Targeting

Location targeting controls which pool Thunderproxy routes a rotating proxy request through. If targeting is unavailable or not behaving as expected, test a simpler location first and confirm the product supports the selected level.

Quick answer: Rotating Residential can support country, state, and city targeting where available. Rotating Datacenter supports country targeting. If a specific location fails, switch to ANY, copy the regenerated username, and test again.

Product targeting levels

Product	Supported targeting
Rotating Residential	Any country, country, and available state/city options
Rotating Datacenter	Any country or country
Static ISP	Uses assigned Static ISP entries, not rotating pool geotargeting

Residential Premium has the broadest targeting catalog. Residential Standard has a smaller catalog with fewer countries, states, and cities available.

Start with ANY

When a targeted proxy fails, test the broadest pool first:

Open the rotating subscription.
Set location to Any.
Copy the regenerated username or proxy string.
Test with cURL.

If ANY works but a specific location fails, the issue is probably location availability, app caching, or an old exported username.

Copy the regenerated username

For rotating products, geotargeting is encoded in the username:

base-res-US
base-res-US_CALIFORNIA
base-res-US_CALIFORNIA_LOSANGELES
base-dc-DE

Changing the dashboard selector is not enough if your app still uses an old username. Copy the updated value or export a fresh list after changing location.

Check product limits

Rotating Datacenter supports country targeting only. State or city-style usernames are for Rotating Residential where those locations are available.

Static ISP entries are dedicated proxy rows. They do not use rotating residential or datacenter geotargeting suffixes.

Check sticky sessions

Sticky sessions stay inside the selected location scope as long as the session can be served. If the current peer goes offline, Thunderproxy may route the same session ID to another available exit IP in that scope.

If location behavior looks stale:

Generate a fresh sticky session.
Re-export the list after changing location.
Test a rotating username without -sid- to isolate session behavior.

Check your app cache

Some browser profile tools and scrapers cache proxy lines after import. If you change location in Thunderproxy, the app may still use the old imported username.