Quick answer
Why do IP databases show different cities for the same ISP proxy?
Because IP geolocation is an estimate. Each database combines registry records, provider data, network measurements and user corrections, and they weigh them differently; a data-center address near a large metro is easy to place in the wrong suburb. PinnedIP shows the city of each US ISP IP when known. Availability by state, city and internet provider varies; the checkout shows what is online.
Where does IP geolocation come from?
No registry publishes the city of an IP. Commercial and free databases build it from several signals:
- Registration: the address and organization in the regional registry (ARIN for most US addresses).
- Provider feeds: some providers publish geolocation feeds for their ranges (the RFC 8805 format).
- Network measurements: latency from probes in known places, and the names of routers on the path.
- Corrections: reports from users and site owners.
Each database updates on its own schedule. A block that moved from one city to another can stay at its old location in one database for weeks.
Why are ISP proxies harder to place than home IPs?
A home IP is usually placed close to its subscriber because the provider’s own data and user corrections point there. An ISP proxy address is registered to a consumer provider but hosted in a data center, so the signals can disagree: the registration may point to one city, the latency to the building where the server sits. That is why a server in Secaucus can appear as Secaucus, Newark or New York, and why many proxy IPs in Northern Virginia appear as Ashburn. Our city pages note these local quirks metro by metro.
How do I check the city of an IP?
Pick two databases
Use two independent services, for example a commercial database’s free lookup page and an open one. Do not rely on one answer.
Look up the exit IP
Use the IP the proxy actually shows (check that it is static first), not the one you expect.
Compare country, state and city
Country and state almost always agree. If the city differs, note both.
Test the target site
Open the page you care about through the proxy: a store locator or a local-results page shows which city that site thinks you are in. That is the answer that matters for your check.
What should I do when databases disagree?
Decide what your check needs. For statewide tasks (tax, privacy notices, state rules), a state match is enough, and it is usually consistent. For city-level tasks (local search, delivery fees), trust the target site’s own reading over any database, and choose IPs it places in the right city. If an IP lands in the wrong metro for your purpose, contact support: when another IP in stock fits better, it can be swapped under the refund policy during the first 24 hours.
Can a browser reveal a different location?
Yes. A browser can expose your own time zone, language and, with permission, GPS position, and WebRTC can reveal local network details. A US IP with a browser set to another time zone looks inconsistent to sites that compare the two. For QA of your own site, set the browser’s time zone and language to match the city you test.
Geolocation: FAQ
Can you guarantee the city of an IP?
No. The city of an ISP IP is what geolocation databases report; databases can disagree, and no city or provider is promised before the checkout shows it. The checkout shows the city we have on record for each IP; test it in two databases.
Can I report a wrong city to a database?
Most databases accept corrections from network operators. As a customer, tell our support: we can pass the correction upstream, but database updates take time and are not in our control.
Does the city change during my rental?
The IP does not change; a database can move it after an update. Re-check monthly if your work depends on the city.
Sources (2)
- RFC 8805: A format for self-published IP geolocation feeds — IETF (2026-10-19)
- ARIN Whois search — American Registry for Internet Numbers (2026-10-19)