Skip to content

Networking & IPs

Geolocation databases

Learn what IP geolocation databases actually report and how corrections reach banks and CDNs.

Updated Aug 29, 20263 min read11 reads
Geolocation databases
How IP geolocation databases work

IP geolocation is a vendor database that maps IP prefixes to a likely country or city. Companies such as MaxMind and IP2Location sell those guesses so sites can show a flag, apply a rule, or check a payment form. It is not GPS, not WHOIS, and not the city name on a datacenter brochure. A leased prefix does not change overnight just because you ordered it. LogicWeb updates geo data on leased space after the order is live, not as a pre-sale list of cities you can shop.

What an IP geolocation result really means

A /24 we announce from New York can still read as the United States in one database and as a prior lessee’s country in another until both refresh. Treat the result like a confident hint, not a fixed coordinate. If you need a specific country for a payment processor, tell us on the order. We will say what we can file with the registries and vendors we work with. We cannot promise the timing of MaxMind’s next weekly update or any other third-party drop.

When a VPN or NAT is not a geo failure

A user on a VPN in another country will show that other country on purpose. That is the VPN doing its job, not a broken geolocation record. The same is true for a cloud jump box or a mobile carrier that NATs across regions. Corporate offices that egress through a cloud region will look like that region as well. Your app should not treat an unexpected country as fraud when you already know the traffic path. Spend your time on real routing or account issues instead of chasing VPN clients as geo bugs.

How a correction moves through the system

We file updates at the registries and at the geo vendors where we have a process. If you are the registered user of a prefix, you can also submit a correction to MaxMind yourself. After that, you wait. Banks, CDNs, and ad networks cache the old guess, so a fix filed on Tuesday can still appear wrong on a processor on Friday. Wrong country on checkout is a support queue item, not a routing outage. CDNs and banks often lag behind the vendor’s own self-serve form.

Look up the prefix in the same vendor your processor uses. A looking glass shows the route; it does not show the flag those products display. Paste the vendor lookup, the prefix, and the country you expected. Saying only that you are in New York is not a lookup. Note the old country and the new one with a UTC timestamp. File once and leave it alone, because weekly toggles keep you stuck in the last cache. Send us the prefix, the vendor result, current country, desired country, and whether a payment processor is involved so we do not have to guess which database they bought.

Share

Send this article

Need someone else to do this? Send them the link — the commands are in the article.

Was this article helpful?

Be the first to rate this article.