Geolocation API acting weird?

Hey everyone, hope you're all having a less frustrating day than I am! Following up on some of the excellent discussions we've had here about optimizing IP lookup accuracy, I'm now facing a new, rather annoying headache. Our primary geolocation API seems to be having a full-blown personality crisis, and it's driving me absolutely bonkers. It's not just a minor inaccuracy we're dealing with; it’s giving us results that are wildly inconsistent and, frankly, laughably bad sometimes. We’re seeing users who are clearly in London suddenly showing up in Manchester, or even different countries entirely, for repeat visits from what appear to be the same IP address. This erratic behavior is completely messing with our geo-targeting logic, which, as you can imagine, is pretty central to some of our features. We’ve tried just about everything we can think of to troubleshoot this digital Houdini. We’ve meticulously checked our API keys, verified that our internal database (we lean on a MaxMind GeoLite2 setup for some initial filtering) is up-to-date, thinking maybe a stale database was the culprit. We even went so far as to A/B test with another free geolocation API just to see if our main provider was the problem child, but while the other one wasn't perfect, it didn't exhibit this level of random geographic gymnastics. We’ve peered into our network configurations, considered CDN influence, basically every stone we could think to turn over. Despite all these efforts, and the significant amount of hair I’ve pulled out, the issue persists. It seems particularly prevalent with mobile IPs and certain VPN providers, which makes sense to a degree, but it’s not exclusively limited to them. Honestly, sometimes it feels less like an 'inaccuracy' in IP address lookup and more like a 'random guess generator' that occasionally hits the mark by sheer dumb luck. So, I’m throwing this out to the collective wisdom of AdsVolt. Has anyone else encountered similar erratic and wildly inconsistent behavior with their geolocation API? Are there specific types of IPs that are just inherently more problematic for accurate geo-location than others, beyond the usual suspects like VPNs and proxies? And crucially, are there any lesser-known strategies or tools for debugging these kinds of inconsistencies that go beyond the usual suspects we've already tried? Any insights or shared experiences would be a lifesaver right now. Thanks in advance!