Coronium Mobile Proxies
Proxy routing and network checks

Proxy Showing the Wrong Location? Country and City Checks

Find out whether the mismatch comes from routing, a GeoIP database or browser state, then collect the evidence needed to fix it.

Coronium Technical TeamSources checked 7 min read
Concept illustration of a mobile network route and two map databases assigning different pins.
A mobile network path and a database location are different observations. The workflow below separates them before you change a connection.

The practical answer

  • First record the exit IP from the affected application. The gateway hostname and the IP shown in another browser are not substitutes.
  • Compare country and city separately. Mobile IPs can cover a broad area, and databases can disagree about the same address.
  • Change one variable at a time: route, location permission or account state. Keep the IP and timestamp with every result.

Identify what is actually reporting the wrong location

A proxy showing the wrong location can describe three different failures. The application may not be using the intended route. A database may assign an unexpected country or city to the correct exit. Or a website may show a region based on browser permission, cookies or account settings instead of IP alone.

Write the requirement before testing: for example, โ€œthis worker must reach our test page from an exit classified as US,โ€ or โ€œthis browser session must receive the UK version of our own storefront.โ€ Those requirements need different observations. Record the actual country classification or storefront response your requirement names, rather than only a map pin.

MaxMind explains that mobile IPs can be used across wide areas and may have no meaningful city-level result. The browser Geolocation API is a separate permission-controlled feature. Neither the gateway hostname nor the browser's coordinates prove which public IP reached a particular website.

Start with the symptom table, then follow the corresponding check. Preserve the original result before clearing cookies or changing the endpoint.

Which evidence to collect first
SymptomFirst observationNext step
The application shows your usual home IPExit from that exact processCheck explicit proxy settings and bypass rules.
The exit changes, but a lookup shows another countrySame IP in two named datasetsRecord the disagreement and investigate with the network provider.
Country is right; city is unexpectedDatabase city and accuracy informationDecide whether the job truly requires a city-level match.
IP tools agree, but one site shows another regionSite result, account state and location permissionTest browser/account signals without changing the exit.
A DNS test shows a distant resolverHTTP exit and resolver as separate observationsInvestigate DNS routing separately; do not infer HTTP country from the resolver.

Measure a direct request and a proxied request

Separate the observed exit IP from database labels and browser location signals.
Compare the same exit address across datasets. Keep browser location and account state fixed while isolating the network result.Open full-size diagram

Use the same machine that runs the affected job. For a browser-only issue, also open an IP diagnostic inside that browser profile; a shell test proves only the shell request's route.

These curl options make the comparison explicit. Set PROXY_URL, PROXY_USER and PROXY_PASSWORD privately to the purchased connection. PROXY_URL should contain only its scheme, host and port.

bash
# Direct control: ignore proxy environment variables for this request.
curl --silent --show-error --fail --connect-timeout 10 --max-time 20 \
  --noproxy '*' 'https://api.ipify.org?format=json'

# Proxy check: do not let NO_PROXY bypass this diagnostic destination.
curl --silent --show-error --fail --connect-timeout 10 --max-time 20 \
  --noproxy '' --proxy "$PROXY_URL" \
  --proxy-user "$PROXY_USER:$PROXY_PASSWORD" \
  'https://api.ipify.org?format=json'

ipify returns the source address seen by its endpoint. Record both responses and the UTC time. If they differ, the requests used different public exits. If they match, inspect proxy application and network topology; a matching IP alone does not identify the cause. Do not publish command traces containing expanded credentials.

Then run the application's own IP check: HTTPX, aiohttp or Node.js fetch. A working curl command beside a failing application narrows the investigation to application routing, environment or session handling.

Keep IP versions explicit. The default endpoint above checks an IPv4-facing destination. A successful IPv4 path does not prove what a separate IPv6 connection will do. Test the family's actual route and record the returned address; do not interpret a failed IPv6 diagnostic as proof of a leak.

Interpret a mobile country or city result correctly

An IP lookup describes an address as represented in a dataset. It does not locate the physical modem with GPS precision. Mobile networks can carry traffic through gateways serving a wider area than the device's immediate location. Some databases intentionally omit a city when the evidence supports only a country or subdivision.

When a result includes an accuracy radius, read it as uncertainty around a location estimate, not as a promise that the device is at the map pin. When city data is absent, your application should be able to use a less precise location. MaxMind documents these limitations.

Private-side and public-side addresses are also different evidence. RFC 6598 reserves 100.64.0.0/10 for shared address space. An address in that range on a modem or network interface is not the globally routable exit the destination sees. Read the CGNAT guide if those two addresses are being confused.

For purchasing, separate country, carrier and region requirements. Our US mobile proxy and UK mobile proxy pages describe the country offering; confirm available regions in the dashboard and test the exact target requirement. A rotating pool needs more than one sample if the workflow depends on a location label staying consistent.

Test browser permission and account state independently

Keep the proxy endpoint and observed exit fixed for this test. In a fresh test profile, open your own or an authorized page and record its initial region before granting location permission. Record whether the page requested permission at all.

Then change one setting and repeat. Grant or deny location permission while keeping the same account state. In a separate run, sign in or apply a saved country preference while keeping location permission fixed. These comparisons reveal whether the displayed region changes without a network change.

For a site you develop, Chrome DevTools Sensors can emulate coordinates. This tests how your page responds to browser geolocation; it does not move the proxy exit. Label emulated coordinates in the QA record so they are not presented as measured device location.

A DNS resolver's city, browser timezone and website language are useful context but are not interchangeable with the HTTP exit. Use the WebRTC test and DNS leak guide when those channels are relevant. An extension can also change browser routing without changing the shell environment, which is why the first browser IP check matters.

Turn a database disagreement into a specific support request

Look up the same exit IP in each dataset and record the provider name, country, region, city, timestamp and database version if available. Repeat the lookup before changing the session. Comparing yesterday's rotated exit against today's browser result does not establish a database disagreement.

Consider this illustrative case: the purchased region is US; the browser's observed exit is unchanged; database A returns US; database B returns GB; the site displays GB. This shows disagreement, not proof that either dataset is right or proof that the site uses database B. Send the observations to the network provider and ask it to investigate that address's assignment and location data.

MaxMind has a correction process for its own data. An accepted correction does not update every database or every website cache at once. A network operator may also have better evidence about an address block than a customer using one temporary exit.

For a city-only disagreement, first ask whether the data supports that precision. Requesting a specific city just to satisfy a test can make the record less accurate. If the workflow truly requires a city-level result from a named target, confirm that requirement before buying a large number of ports.

Keep an acceptance record that survives rotation

Use the downloadable CSV worksheet for one row per observation. It keeps the purchased country separate from observed database labels. Store the proxy password elsewhere; the endpoint alias is enough to correlate a private support record with your own configuration.

A useful acceptance sequence is:

  1. Record the intended country, carrier and any target-specific region requirement.
  2. Capture the exit from the affected application and the UTC timestamp.
  3. Look up that exact address in named datasets without rotating between lookups.
  4. Record the target's result and the browser permission/account state.
  5. Repeat after a planned reconnect or rotation, keeping the other variables unchanged.
  6. Mark which requirement passed or failed and what evidence supports that result.

For a support handoff, be specific: โ€œAt this UTC time, this worker returned this exit. These two datasets disagree on its country. Our target showed this region with location permission denied.โ€ That gives support a reproducible investigation instead of only a screenshot of a map pin.

The commands and worksheet are diagnostic procedures. The examples in this guide are explicitly illustrative; we have not measured a carrier-wide location accuracy percentage. Continue with IP allowlisting if the route is correct but a gateway or destination denies the source address, or with the mobile proxy guide when choosing a different connection model.

Sources and review scope

Sources reviewed October 15, 2026. Primary documentation and diagnostic procedures are identified separately from measured results. These guides do not claim carrier-wide location accuracy or universal support for an authentication feature.

Frequently asked questions

Check the other side of the connection

Separate the client source, proxy gateway, public exit and location signal before changing configuration.

Related workflows

IP allowlisting and source addresses

Separate the IP connecting to a gateway from the exit presented to a site.

ASN lookup

Check network registration alongside location evidence.

Mobile proxies for ad verification

Define the location and test conditions for an authorized campaign check.

Compare mobile connection options

Select a country and carrier, then confirm the available configuration.

Where to get a dedicated line

A Coronium mobile proxy is one physical device with its own SIM, rented to one customer. It connects over HTTP or SOCKS5, the IP changes by dashboard button, API link or timer, and data is not metered on dedicated lines. Brazil lines are the exception: 20 GB of data a month and a new IP on request only, with no timer. Stock and prices differ by country and carrier.