Country, city and ASN targeting in a proxy order

Choose between country, city and ASN proxy targeting by defining the exact geographic or network signal your application needs.

A red cord connects a globe to a city street map beside stacked network switches.

Choose the narrowest requirement the project can justify

A French-language campaign may need a French network view, while a pickup offer may depend on a particular store. A telecom promotion may depend on the network operator. These are three different acceptance conditions. Ordering city and network targeting together can narrow the available choice without improving a test that depends mainly on a postal code stored in the application.

Document the source of each label

A country or city estimate can differ between geolocation databases. An autonomous system number identifies a routing domain and can be checked through established network records. A matching ASN is evidence about the network path, with limited power to identify a particular household, street or device. Record the database and date used by the application under test when those labels affect business behavior.

A market-research team comparing two national store editions can begin with country-level evidence. An agency checking a carrier-sponsored landing page should instead include the expected operator in the same written acceptance rule. MaxMind IP geolocation accuracy comparison.

Put a disagreement rule in the brief

Decide whether the authoritative result comes from your service's regional response, an agreed geolocation database or an observed network identifier. Keep the decision with the order. When requesting an XtremeProxy location, include the target market, the precision that genuinely affects the job and an example of the expected application response. This makes comparison possible even when two location databases disagree.

The app chooses by country while the requirement asks for a city

A team wants to test a policy applied to an entire country. A sales brief also mentions a particular city and autonomous system. Ask which product decision depends on each field. A country-level fixture can satisfy the policy test, while investigation of a carrier-specific issue may need the documented network operator. Keep those purchases distinct. Compare the provider's targeting label with the application's observed decision and retain both if they disagree.

State what each location source can support

A provider's label, number registration data and the destination's own geolocation decision describe different observations. Keep each with its date and source. If an application authorizes by ASN, a city match is irrelevant to that rule. If it authorizes by country, document how disagreements will be investigated.

Ask how the plan handles a target that is temporarily unavailable. Returning an error and falling back to another region have very different consequences for a regional acceptance test. Require an observable outcome for that case, and mark samples with an unknown or fallback route before calculating a coverage rate.

Use one requirement per acceptance row

A national catalog test needs a country decision. A carrier-support investigation needs a named operator. A city-specific test may need a different data source altogether. Write one row per requirement and let a result pass one row while remaining unconfirmed in another. One successful country observation cannot resolve the operator or city questions automatically.

Take a selection described as “Paris, France” and ask whether the contract promises a city classification, a physical facility, or the application experience aimed at Paris shoppers. Those are different acceptance conditions. An owned store can deliver Paris-specific content because a saved pickup branch selects it, even when the route is elsewhere. Conversely, a route classified in Paris can show a national catalog. Write one desired outcome and the evidence that would establish it before selecting the targeting granularity.

A city-specific request is easier to evaluate when the customer can describe exactly what will happen differently in that city. For example, a store locator may select a depot from an entered postcode, while the site's default language uses the network's inferred country. Those are different decision inputs in the same visit. Write both expectations down and choose a known fixture for each. A test that passes the national language rule while leaving depot selection unexplained should receive two separate findings.

Treat the purchasing brief as a set of individually testable geographic requirements. Capture the application's actual decision and the evidence behind each requested level of precision. Dealer locator territory assignments illustrates a territory-dependent result on an owned service. Why two IP geolocation databases show different cities explains what to do when two city-level sources disagree after the order is fulfilled. Technical references include IANA number resource registries. Review XtremeProxy plans and allowances.

Frequently asked questions

Is an ASN a city identifier?

An autonomous system identifies a routing administration and can cover many locations. Pair network evidence with a suitable location source when both are relevant. Avoid inferring a service area from an ASN alone.

Related articles