City targeting and fallback rules for proxies
City targeting is more specific than country targeting and can reduce the number of usable exits. Treat a selected city as an availability request.
Separate mandatory and preferred cities
If the workflow truly requires one city, specify it in the order. If a whole country works, choose country-level targeting to preserve a larger pool and usually faster fulfillment.
Understand the network difference
A rotating pool may offer city selection in the username or configurator. A static IP order asks for a city at purchase time and depends on assignable addresses. Do not reuse rotating syntax for a dedicated IP.
Test the delivered exit
Inspect the IP, location and session behavior. If a city lookup differs, compare multiple databases before concluding the assignment is wrong; then share the evidence with support.
Worked example
Set three levels before ordering: the exact city, any city in the required country, and another acceptable country. Decide which fallback moves are permitted. This prevents a location that looks close on paper from being useless for the actual task.
Common questions
Why does a city filter reduce availability?
Only addresses assigned to that city remain eligible. A narrower region means fewer candidates; availability varies by network and current inventory.
What if the city is unavailable?
Choose only a preapproved alternative or ask support. Broadening to the whole country can change the outcome of your tests.