In my experience, some of them use
[
maxmind](https://www.maxmind.com/en/home), as the widely used geoip was
built upon a free version from them. You can correct them at their
[
site](https://support.maxmind.com/geoip-data-correction-request/).
As for the sites behind Cloudflare, they can get two letter location
code from the CloudFlare. Other CDNs may have their own version.
As for the Google overlord, they have their own GeoIP db, unfortunately
it's next to impossible to change GeoIP for them. Yes, I know they have
a webform where you can submit correction data to them, but for me it
never worked. To update your GeoIP for Google you will need to register
at their [Peering Portal](https://peering.google.com), wait for
approval, and wait another weeks for your update to take effect.
I think the easiest and quickest way is to announce the prefix by
yourself. It looks most GeoIP databases are built from ASN whois and/or
country lists on RIRs.
- Quan
On 9/26/19 6:32 PM, Toussaint OTTAVI via 44Net wrote:
Hi all,
We are migrating our TKNet network to AMPRNet addressing. For machines
directly connected to Internet (ie : XLX, DMR), we are using
44.190.11.0/24 range. Those addresses are geo-located in Chicago. This
has funny consequences. F/ex, when doing speed tests with online
services such as
nperf.com, the automatically-selected "nearest"
server is very far from here :-)
I have absolutely no idea about how geolocation works. Just for
curiosity, where is this information taken from ? The Whois database ?
But Brian's address is in San Diego, not in Chicago...
Is there an easy way to change geo-location information for a specific
AMPR subnet ?
Thank you in advance. 73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net