On Thu, 26 Sep 2019, Toussaint OTTAVI via 44Net wrote: If you have delegated reverse DNS, one could publish DNS LOC records: 1.11.190.44.in-addr.arpa. IN LOC 42 N 42 W see, for optional precision/elevation parameters: https://en.wikipedia.org/wiki/LOC_record https://tools.ietf.org/html/rfc1876 Whether or not the forward/reverse records are consumed by the various third-party Geo-IP sites remains to be seen, but under the guise of amateur radio, it might make sense to *experiment*, try, and report back. ...Perhaps even with a proposal that all networks/IP addresses under 44.0/8.415 MAY or SHOULD provide LOC records. Thus opening things up to a bit of data analysis---perhaps something CAIDA would be interested in? -Paul

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: