An IP location is a database estimate, and each database can be wrong differently.

Why does my IP address show the wrong location?

Read each named location source side by side. Each row is a separate source lineage, and disagreement is shown rather than averaged. A wrong estimate is corrected by your provider’s geofeed or by the vendor whose database is wrong, never by an IP lookup.

Source availability depends on the current deployment and each returned record. These review dates do not establish when a particular IP was observed. Method feodo-dated-absence-2026-10-08 · Score ipjury-score-v3.

An IP location is not a reading from your device. It is a database's estimate for a block of addresses, and every database that answers can be wrong in its own way. The useful questions are which source says what, and who can correct it.

Where an IP location comes from

Geolocation vendors combine several kinds of evidence and weigh them differently: locations that network operators publish for their own ranges, registry records naming who holds a block, routing and latency measurements, and corrections that users and operators submit. Each vendor refreshes on its own schedule, and the website you are using may run a copy that is weeks or months old. Two answers for one address can therefore both be honest outputs and still disagree.

Why your address shows the wrong place

• Your provider's gateway, not your street. Mobile carriers and providers that share IPv4 addresses (carrier-grade NAT) send many customers out through a few gateways. The estimate follows the gateway, which can sit in another city.
• A tunnel changes the exit. A VPN, a proxy, a privacy relay built into a browser or operating system, or a company network sends your traffic out from somewhere else. The location belongs to that exit.
• Satellite and fixed-wireless links leave the provider's network at a ground station or regional point of presence, which can be far from the dish.
• Reassigned blocks. Providers move ranges between regions and customers, and address space is transferred between holders. Databases carry the old location until their evidence changes.
• Two addresses, two answers. A dual-stack connection has an IPv4 and an IPv6 address. They are separate entries in every database and can be placed differently.
• Coarse records. When a vendor knows only the country or the provider's registered office, it may still return a city, such as the capital or the provider's office address.

Reading the LOCATION rows

Run a check and IPJury lists each location source by name, with its country and, where the source has one, its city. Each row is a separate source lineage, so one vendor's database cannot appear as several agreeing witnesses. Disagreement is shown rather than averaged into one place. Coordinates are a database's point for the whole block, rounded to two decimals, and no accuracy radius is drawn because no source publishes one. The registration country is a different record, kept separate: registry versus geolocation explains that comparison.

The rows answer one practical question: which named source is wrong. That decides where a correction has to go.

Who can correct which record

Your network provider

The most effective route for a whole range. Operators publish a geofeed, a file mapping their prefixes to locations in the RFC 8805 format, and point to it from their registry record as RFC 9632 describes. Ask the provider whether it publishes one and whether your range is in it.

MaxMind

A public correction form takes an address or network and the correct location. Submissions are reviewed against other data and may be declined.

IPinfo

A corrections page handles one-off submissions; operators can also send geofeeds.

DB-IP

Its FAQ describes a report link on each address lookup, accepts geofeeds, and says registry record updates are detected. Its database downloads are refreshed monthly.

IP2Location

Publishes a contact page rather than a dedicated correction form.

Vendor processes above were read on 2026-10-08 and can change. A correction reaches a website only after the vendor accepts it, publishes a new release and the website installs that release; some sites also run their own location data. If a specific service misplaces you, ask that service which source it uses. If IPJury misreads a source, that is ours to fix through evidence corrections; if the source itself is wrong, only its vendor or your provider can change it.

What this cannot establish

No IP lookup can say where a person or device is. IPJury cannot tell which database a particular website consults, whether a submitted correction was accepted, or when a site will pick it up. It reports what each named source returned, when, and where they disagree, so the correction goes to the right place with a dated record.