Still struggling: How to fix IP geo-targeting accuracy?

Ugh, I'm back here again, still completely stuck with IP geolocation, but now the problem has shifted from data getting stuck to outright inaccuracy. My previous post was about the data just not updating, but now that's mostly resolved, I'm getting completely wrong locations for a significant chunk of my users. This is becoming a massive blocker for launching some critical geo-targeting features and localizing content for our SaaS, and frankly, I'm pulling my hair out.

The core issue is that our system is reporting wildly inaccurate IP location data for too many users. We're seeing users in California being identified as being in New York, or even worse, in completely different countries. This isn't just a minor offset; it's often off by hundreds or thousands of miles. This directly impacts our ability to deliver localized content, offer region-specific pricing, and run effective geo-targeting ad campaigns. Our conversion rates are suffering because users are seeing irrelevant offers or content.

Here's what I've tried so far:

• We initially thought it was our old API, so we switched providers, testing both MaxMind and IPinfo extensively. While they provided some improvements, the core accuracy problem persists across both.
• I've meticulously verified that the correct IP address is being passed to these APIs. I've dug through server logs, added extra logging specifically for the IP address before the API call, and everything looks correct on that front. It's not a 'wrong IP' being sent issue.
• As a fallback, we've implemented client-side browser geolocation, but that's not ideal for server-side logic and many users block it or we can't rely on it for every interaction, especially for our backend analytics and ad targeting.
• For MaxMind, I've ensured our local GeoLite2 database is updated daily. I even manually downloaded and re-uploaded it to rule out any corruption.
• We've also gone through our server network configurations, checking for any unusual proxy settings, CDN configurations (we use Cloudflare, but pass the real IP via CF-Connecting-IP), or other factors that might be obfuscating the true IP or location data. Nothing jumped out.

I'm desperate for some fresh ideas. Specifically, I need to know:

• What are the absolute best practices for improving IP geo-targeting accuracy, especially when dealing with mobile users, VPNs, or large ISPs that might route traffic through distant points?
• Are there any common server-side misconfigurations I might be overlooking that could be severely affecting the accuracy of the IP address lookup results from these APIs?
• What are some effective, deep-dive debugging steps or tools for reliably getting accurate IP location data? I need to get to the bottom of why these APIs are returning such bad data for certain IPs.
• Are there any alternative, more robust server-side geo-targeting methods or combinations of methods that can provide significantly better geolocation data than relying solely on standard IP geolocation APIs?