Geo-IP lookup going rogue?

Hey everyone, we're running a pretty straightforward web tool called 'What is My Country?' – you know, the kind of service that tells you your current country and IP location. Simple, right? Except lately, it seems to be having a bit of an existential crisis, returning wildly inaccurate locations for some of our users, and honestly, it's driving us a little nuts. We've been through the usual suspects for debugging. Checked server logs until our eyes glazed over, verified API responses from our primary geolocation providers (yes, we even have a backup, tried MaxMind and IPInfo.io, thinking maybe one of them was having a bad day, but both seem to be returning sensible data on their end), ensured our caching layer isn't serving up ancient, stale data, and even gave the whole server a good old reboot just in case it was a cosmic ray flipping a bit somewhere. Nothing. The problem persists. We're seeing some truly bizarre results. We've had users clearly in downtown London appearing to be chilling on a beach in rural Brazil, or someone in California magically teleporting to a sheep farm in New Zealand, according to our tool anyway. It's not even consistently wrong, which is the most baffling part. Sometimes it works perfectly for an IP address lookup, sometimes it's completely off the wall, even for the same IP address if you try it a few minutes later. It's like our tool is playing a very unfunny game of geo-roulette. The real kicker is that the problem isn't universal. It affects some users, especially those potentially behind VPNs or proxies, but there's no clear pattern we can discern. Some VPNs work fine, giving accurate results, while others are totally wrong, making us question everything we thought we knew about IP addresses and geography. This inconsistency is the core frustration; if it was always wrong, we'd at least have a consistent bug to chase. So, this is where we turn to the collective wisdom of the AdsVolt community. Has anyone else experienced similar IP address lookup issues with their web tools? Are there any obscure server configurations, network settings, or third-party API quirks we might be overlooking? We're open to any suggestions for advanced geolocation API debugging strategies beyond the obvious things we've already tried, because frankly, we're running out of obvious things to try.