Urgent: IP geolocation data suddenly wildly inaccurate – help!

Our 'IP Lookup Tool - Geo-locate Any IP Address & Get Details' has been running smoothly for months, but in the last 24-48 hours, the accuracy of our IP location data has drastically plummeted. I'm completely stuck and urgently need some expert insights.

The problem is severe: users are reporting completely incorrect locations – we're talking wrong cities, regions, and sometimes even countries – for their own IP addresses. My own testing confirms this; IPs I know to be in specific locations are now showing up thousands of miles away. This isn't just a minor drift; it's wildly off, making the tool practically useless for its core function.

I've spent hours troubleshooting this, trying everything I can think of. First, I checked all our API keys and credits for our primary IP geolocation provider, MaxMind GeoLite2. Everything appears fine; there are no rate limit errors or expired keys. I then compared our tool's results with several other free online IP lookup services, and they all seem to provide accurate IP location data, which makes our tool look particularly bad. I've also scanned our server logs for any unusual errors or network connectivity issues, but found nothing immediately obvious that would explain such a widespread problem. Full restarts of our web server and application services have yielded no change in accuracy whatsoever. Curiously, I verified that our own server's IP address is correctly geolocated by the MaxMind API, which it is – this just adds to the confusion about why user IPs are so incorrect. Finally, I've reviewed recent code changes; no new deployments or updates were pushed to the application in the last week that could possibly explain this sudden and drastic shift in accuracy.

I'm racking my brain trying to figure out what could be causing this. Could this be related to a DNS resolution problem on our server affecting the API calls to MaxMind? Is it possible the MaxMind database itself is experiencing a temporary, localized glitch that's impacting a specific range of IPs or a region? Or perhaps I'm overlooking a caching layer within our application or server infrastructure that might have gone stale and is now serving old, incorrect IP location data?

Has anyone else recently experienced such a sudden and drastic drop in IP geolocation accuracy, especially with MaxMind or a similar major provider? What obscure server configurations, network settings, or application-level issues could possibly lead to this kind of widespread inaccuracy for IP location data? Are there any specific network diagnostics or external tools I should be using right now to pinpoint the problem? This issue is severely impacting user trust and the core functionality of our IP Lookup Tool, and I'm completely stuck after hours of troubleshooting. Desperately need expert advice on this. Waiting for an expert reply.