This is only "supposed to be" accurate to some definition of what country the IP is assigned to, it is not an authoritative field for where it is currently bein

This is only "supposed to be" accurate to some definition of what country the IP is assigned to, it is not an authoritative field for where it is currently being used. Multinational corporations, M&As, georedundant failover, leasing/selling, and other events often result in this field being outdated or plain wrong. Hell, I've been able to advertise part of my ARIN assigned US IP space out of a peer in Europe. This also ignores the EU designation on certain records https://wq.apnic.net/apnic-bin/whois.pl?searchtext=94.102.168.23 https://wq.apnic.net/apnic-bin/whois.pl?searchtext=94.102.16... Edit: RIPE actually has documentation on this fallacy specifically https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-Primary-Objects#description-of-the-inetnum-object:~:text=to%20the%20object.-,%E2%80%9Ccountry%3A%E2%80%9D,-%E2%80%93%20Officially%20Assigned%20two https://docs.db.ripe.net/RPSL-Object-Types/Descriptions-of-P... > “country:” – Officially Assigned two-letter ISO 3166 country code or "EU" (exceptionally reserved). It has never been specified what this country represents. It could be the location of the head office of a multi-national company, where the server centre is based, or the home of the End User. Therefore, it cannot be used in any reliable way to map IP addresses to countries.