A request for "a proxy with an exact city" is one of the most common queries support receives, but the real need for it shows up less often than it seems at first. Here's when city-level targeting is justified, why narrowing the segment shrinks the pool of live addresses, why mobile channels need a separate carrier selection, and why the dashboard city doesn't always match an independent check.
When city-level targeting is actually needed
City matters where it directly shapes what the end user sees: local ad delivery targeted to a district, a classifieds board where visibility and sort order depend on the seller's declared city, or a local search ranking check — the position a site holds for a specific settlement, not the country as a whole.
The same applies to services with prices and stock tied to a zip code or city: shipping cost and local promotions vary within one country more than between neighbouring countries. If the task is to reproduce what a resident of a given city sees, country-level targeting simply doesn't fit.
When country-level targeting is enough
Most monitoring, scraping and account-management tasks aren't tied to a city at all. A platform usually checks country, ASN and address reputation — the check never reaches down to a specific settlement, so city-level targeting adds no reliability there. It only narrows the address selection for no benefit.
The rule is simple: if no interface element or site-side check is tied to a city, use country targeting and narrow the segment only once the task genuinely requires it.
How narrowing the segment shrinks the pool and raises repeats
The pool of residential and mobile addresses is built from live subscriber connections inside the segment. At country level that's tens or hundreds of thousands of addresses at once; at city level it drops to hundreds or thousands depending on size, and a small town's pool can be dozens. The narrower the segment, the faster the rotation inside it.
The practical consequence: narrow city targeting returns the same address noticeably more often than country targeting, raising the risk of an address already flagged on the target platform — by your own activity or someone else's, if the IP cycled through the pool between sessions. For tasks with frequent repeat visits to one resource, factor this in before choosing a segment, not after the first bans.
Carrier targeting for mobile channels
For mobile proxies, the carrier often matters more than the city. Each cellular carrier keeps its own address pool and NAT gateways, so ASN and address reputation are determined primarily by the carrier, not the geographic point of issue. For more on choosing a carrier, see how to choose a mobile proxy carrier.
Hundreds of live subscribers of a given carrier sit behind a single mobile IP through NAT, which is why such an address is extremely hard to block without collateral damage to everyone else on the same cell — the mechanics are in why mobile proxies are hard to ban because of NAT. When several carriers operate in one direction, targeting a specific carrier gives more control for sensitive tasks than targeting a city: carriers in the same city can carry very different address reputations.
Mismatch between the declared city and what the geo database shows
The city in your dashboard when an address is issued is the provider's declared attachment point, not a guarantee that an independent geo service on the target site reports the same city. Subscribers physically move, carrier IP blocks get reassigned between cells, and geo databases update with a lag — a mismatch to a neighbouring city in the same region or state is normal, not a defect.
The verification order is the same regardless of channel type: country first, through any geolocation service; then city, cross-checked against the geo database's own response rather than the dashboard field; then ASN — the autonomous system the address belongs to, covered in what an ASN is and why it matters; and separately, address reputation. If a task is sensitive to precision, verify the assigned address before starting the session instead of relying on the declared targeting.
Frequently Asked Questions
Can I set both a city and a carrier at once?
Some mobile proxy directions support a "city plus carrier" combination; others allow only one of the two, because of pool size. Check the catalogue before purchase for the granularity available for a given country and carrier.
Why does the assigned IP resolve to a neighbouring city in the same region?
Geo databases tie the address to the carrier's distribution point, which doesn't always match the subscriber's physical connection city. A mismatch within a region or state is normal for mobile and residential pools, not a delivery error.
Should I always pick the narrowest targeting available?
No. Narrow targeting is justified only when city or carrier precision actually affects the outcome. Otherwise it just shrinks the address pool and raises the repeat rate without benefiting the result.
The proxy catalogue with targeting by country, city and carrier is in the proxy section. The same page shows which directions support city-level detail and which support only carrier or country level.