Quite worldwide at the moment, when I look up www.cloudflare.com in the DNS system, I am getting the two IPv6 addresses 2606:4700::6810:7b60 and 2606:4700::6810:7c60, as well as the two IPv4 addresses 104.16.123.96 and 104.16.124.96.
→ iplocation.net: Geolocation for 2606:4700::6810:7b60
→ iplocation.net: Geolocation for 2606:4700::6810:7c60
→ iplocation.net: Geolocation for 104.16.123.96
→ iplocation.net: Geolocation for 104.16.124.96
These IPv6 and IPv4 addresses are, even they are the exact same, being announced from multiple locations across the whole world at the same time using something referred to as anycast, so that an user will (generally) end up on the closest Cloudflare PoP (Point of Presence), depending on the connectivity (and routing policies) that the specific end user ISP has, and where/how the specific end user ISP is able to connect with Cloudflare.
As one single IP address can only have one single set of information (e.g. country, state, city, …) attached at a time, any attempts to use such “geolocation” to determine the actual “destination country” on IP addresses used with anycast, or other sort of multi-homing as well, will always be whacky, if ever successful in any way.
With Anycast, or other kind of multi-homed IP addresses, the most common would be to see the IP addresses as showing up with the country code of the person/organisation that the IP addresses are allocated to.
That being said, - to determine whether the understanding (and thus elaboration above) is correct:
Where (and how) exactly did you see the country that you refer to, as “destination country”, that made you make this thread?