Guide
Why does my IP address show the wrong location?
IP location is an educated guess, and it is often a city, a region or even a country off. Here is where the guess comes from, why it goes wrong, and what you can do about it.
By Mark Stoumann ·
No database knows where an IP address really is. Addresses are handed out to networks, not to places, so a lookup can only report where an address is registered, where its network connects to the internet, or where someone has said it is used. Most lookups get the country right and the city roughly right. Plenty don’t.
To see what websites currently guess for you, open the IPLookr homepage.
How IP location databases are built
Companies such as DB-IP and MaxMind publish databases that map blocks of IP addresses to places. Websites buy or download one of them and look up every visitor in it. The data comes from a handful of sources:
- Registration records. Every block is registered with one of five regional internet registries, with a holder and a country. That is a starting point, but it is where the holder is registered, not necessarily where the addresses are used. Our guide on who owns an IP address explains these records.
- Network data. Which network announces a block on the internet and where it has equipment, combined with measurements the providers don’t publish.
- Geofeeds. Internet providers can publish a simple file listing their address blocks and the area each one serves, in a format described in RFC 8805. Google, MaxMind and DB-IP all read them.
- Corrections. Users and network operators report mistakes, and the providers check and apply them.
Each provider weighs these sources differently, so two databases can place the same address in different cities. And each website updates its copy whenever it gets round to it.
Why your location is wrong
It shows your provider’s network, not your home
Your address comes from a pool your internet provider uses for a whole area, and databases usually place that pool where the provider connects it: a regional hub or the nearest large city. If you live outside a big city, seeing the nearest large town is normal.
Mobile data and shared addresses
Mobile networks usually send their customers’ traffic out through a few central gateways, and many share one public address between lots of customers (carrier-grade NAT, explained in public vs private IP addresses). When one address is in use by many phones in different places, a database can only pick one of them. DB-IP says its data is generally more accurate for fixed lines than for mobile networks.
VPNs, iCloud Private Relay and company networks
With a VPN, websites see the VPN server’s address and its location; that is the point. iCloud Private Relay gives you an address that matches your region and, by default, the nearest city, or only your country if you choose Use Country and Time Zone. Companies and schools often send all traffic out through one office, data centre or cloud security service, so a laptop at a branch office can show up at headquarters, or in another country.
A clue: if the Time zone row on IPLookr says your browser’s time zone differs from your IP address’s, your traffic is probably leaving the internet somewhere else.
Satellite internet
Satellite services connect you to the internet through a ground station that can be far away. Starlink says its addresses always come from the country of your service address, but the location can be several states, provinces or regions away from you.
The address changed hands
Most registries ran out of new IPv4 addresses years ago, so blocks are now sold and moved between providers, and sometimes from one region of the world to another. The RIPE NCC publishes every transfer in its region. Until the databases catch up, a block can keep the location of its previous holder. The same happens when a provider moves addresses from one city to another. DB-IP says it watches registry records for such changes, but its free databases are only published once a month.
One address, many places
Some addresses are used in many places at once, a technique called anycast. Cloudflare’s DNS resolver at 1.1.1.1 runs in hundreds of cities, but a database can only store one location per address: DB-IP’s free database says Australia, which is also the country in the block’s registration. Google’s 8.8.8.8 works the same way.
Where IPLookr’s location comes from
We’d rather be exact about our own data:
- The city, region, postal code, time zone and coordinates on the homepage are an estimate made by our host, Vercel, which passes them to us with each request. We can’t correct them ourselves.
- The network and its AS number next to them come from DB-IP’s free IP to ASN Lite database.
- On the IP lookup, the country comes from DB-IP’s IP to Country Lite database, which has no city data. The registration country in the WHOIS details is a third value: where the holder of the block is registered.
- We download DB-IP’s latest monthly edition every time the site is built, so a correction DB-IP makes shows up here once it is in a monthly edition and we have updated the site since.
So if the homepage and a lookup of your own address disagree, you are looking at separate estimates from separate sources, not a bug.
How to get a wrong location fixed
- Rule out the obvious. Turn off any VPN, proxy or iCloud Private Relay, reload the IPLookr homepage and see whether the location changes. Try once on Wi-Fi and once on mobile data, since they are different networks.
- Ask your internet provider. It is the only one that can fix the source: it can publish or update a geofeed for its addresses and correct its registry records. Give it your IP address, the location shown and your real town. Smaller providers may not know what a geofeed is; mentioning RFC 8805 helps.
- Report it to the geolocation providers. At DB-IP, look up your address on its website and use the report link on the result; network operators can also send it a geofeed or batch corrections. MaxMind has a correction form, reviews one-off requests within one to two business days and includes accepted ones in its next release.
- Tell the website. If one particular site gets you wrong, ask which database it uses, and give it time to load the corrected data. Google Search can use your device’s location instead of your IP address if you allow location access in your browser or on your phone.
What you can’t fix
- Shared and mobile addresses will rarely be pinned to your town, because they aren’t only yours.
- VPN and relay addresses show the server’s location, by design. To change the location websites see, you change the address; see how to change your IP address.
- Other people’s databases update when their owners decide to. You can report a mistake, but you can’t force an update.
- Your home isn’t something an IP database knows. Even the best result is an area, which is why IPLookr marks its coordinates as approximate. If that is what worried you, read what your IP address reveals.
Frequently asked questions
Why do different IP checkers show different locations?
They use different databases, and each website updates its copy on its own schedule. Even on IPLookr, the location on the homepage is an estimate from our host, Vercel, while the country in the IP lookup comes from DB-IP, so the two can disagree. Both are estimates, not measurements.
Can I change my IP location myself?
Not in the databases. You can only change which address you use, for example by connecting through a VPN or another network. To fix the location of your own address, ask your internet provider to update its records and report the mistake to the geolocation providers.
How long does a correction take?
It varies. MaxMind says it reviews one-off corrections within one to two business days and includes accepted ones in its next database release. DB-IP publishes its free databases once a month. After that, every website still has to load the new data, which can take weeks.
Why does Google think I am somewhere else?
Google Search estimates your location from several sources: your device’s location if you allow it, the home and work addresses in your Google Account, your past activity and your IP address. If the IP address is all it has, the result can be as far off as any IP lookup. Allowing location access usually fixes it.