Why your IP address shows the wrong city

Your IP address does not contain your location. Sites look it up in a database that mostly knows where your internet provider registered the block your address came from, so the pin lands on a network hub – often a different city, sometimes hundreds of miles away. A wrong city is normal and usually harmless. A wrong country, or your own city still showing while a VPN is on, is worth a closer look.

Updated 11 August 2026

Where that city on the map comes from

An IP address is a routing number, not a coordinate. Nothing inside it says where you are sitting. When a site names your city, it has looked the address up in a geolocation database – a big table that maps ranges of addresses to a country, a region and a best guess at a city.

Those tables are built from indirect clues:

• registration records – which company owns a range of addresses, and the postal address it gave when it received them;
• information providers publish about where each range joins the rest of the internet;
• timing tests – how long a signal takes to reach a range from measuring points around the world;
• location data people hand over themselves, for example when a browser reports a precise position and it gets tied back to the address it came from.

None of that is a direct look at your device. Different companies build their tables from different clues, which is exactly why one site names one city and another names a different one for the same connection at the same moment.

Why the pin lands on your provider, not on you

Your internet provider does not own an address for every customer. It owns blocks of addresses and hands them out from a pool, often giving you a different one when your router reconnects. A block is registered once, usually to the company's head office or to the regional hub that serves a whole area – sometimes several regions at once.

So the pin marks the point where your traffic joins the wider internet, not the building you are in. On a large network that gap can easily be a hundred miles or more. Small providers make it worse: if yours rents capacity from a bigger operator, the database may name the bigger operator and its city, and your own provider will not appear at all.

Addresses also change hands. A block sold from a company in one city to a company in another keeps its old entry in some databases for months, so a perfectly ordinary home connection can be labeled with a place it has never been near.

Mobile data is the worst case

If you are reading this on mobile data, expect the location to be well off. Mobile operators do not give every phone its own public address – hundreds or thousands of subscribers share one, through equipment that sits in a handful of large data centers.

• The address describes that shared exit point, not the cell tower your phone is talking to.
• An operator may route a whole country through two or three of them, so most customers show up in the same one or two cities.
• Addresses get moved between regions as capacity is reassigned, and the databases lag behind.
• Some mobile ranges are registered for the country as a whole, with no city at all – the database then falls back to the largest city or the geographic center.

Being shown a city hundreds of miles away on a phone is completely ordinary. Your phone still knows where it is – from satellites and nearby Wi-Fi networks – but that is a separate signal, and only apps you have given permission can use it.

When a wrong city is nothing to worry about

Most of the time the explanation is boring: the database is imprecise and everything on your side is fine. That is the likely answer if:

• the country and the provider are right and only the city is off;
• you are on mobile data, or sharing a phone's connection with a laptop;
• you are on a work or school network – that traffic often leaves through a central office in another city;
• you are using a VPN or a proxy and see the location of that server instead of your own, which is what it is for;
• two sites show two different cities – they simply use different databases;
• the city changed after you restarted your router and got a different address from the pool.

When it is worth a closer look

A few results deserve a second glance:

• The country is wrong and you are not using a VPN. Usually a stale or mislabeled range, but it is worth checking your system and browser settings for a proxy you did not set up yourself.
• The provider is a company you have never heard of, and it is not the parent of your own. Same check: something may be sending your traffic through someone else first.
• You turned a VPN on and a site still names your home city. Then your real address is reaching that site by another route: the browser feature used for voice and video calls (WebRTC) can reveal it, a newer IPv6 connection can run alongside the tunnel and slip past it, or your clock's time zone can quietly contradict everything else. IPgeo runs all three of those checks on the main page.

The last one is the only case here that is a real problem rather than a database quirk: you believe your address is hidden, and it is not.

What a wrong city changes on the sites you use

Mostly small things. Sites use the guess to pick a language and a currency, to show local weather, to suggest a nearby pickup point, and to connect you to the closest server so pages load faster. A wrong guess means a wrong default, and you can nearly always change it by hand.

It gets more annoying in two places. Payment and account systems watch for sudden changes of location, so an address that jumps between cities can trigger an extra confirmation step or a warning email when nothing unusual has happened. And online stores may quote delivery dates from the wrong warehouse.

What it never does is prove anything about you. IP location is a rough hint, not evidence of where a person was, and it should not be treated as one by anyone – including a site that tells you otherwise.

What your address really tells a site

Since the city is such a weak guess, it is worth being clear about what is solid. Any site you open can see the address itself, the country behind it, the provider that owns it and the network it belongs to. That is enough to place you in a rough area and to recognize you again on a later visit, on its own or combined with other things the browser gives away.

It is not enough to find your home. There is no street address hidden in the number, and no public lookup turns one into a person. The one exact link – which customer had which address at which moment – sits with your provider, and it is handed over only on a lawful request.

So the honest summary: the city on the map is a bad guess and usually harmless. The part that is real is that your provider's address is on record with every site you visit.

What you can do about it

1. Set your city on the site itself. Almost every store, delivery service and weather page lets you choose it by hand, and that choice overrides the IP guess from then on.
2. Allow precise location where you actually want accuracy. The browser uses satellites and nearby Wi-Fi, which is far better than any address database – and it works only for the sites you specifically allow.
3. Check what sites really see. Open IPgeo and you get your address, country, provider and network, plus the WebRTC, IPv6 and time zone checks in one place. Everything is worked out on our own servers, visitor addresses are never stored, and there are no ads and no third-party trackers on the page.
4. Report the mistake. The main geolocation databases have correction forms, and your provider can ask for a range to be relabeled. Fixes take weeks to spread, but they do spread.
5. Automate the check if you need it often. api.ipgeo.ru returns the same data in machine-readable form, with no key and no sign-up.

And if what actually bothers you is not the wrong city but the fact that every site you open sees your provider's address at all, that is a privacy question rather than an accuracy one – and it has a different answer.