why am i seeing ip data discrepancies with my geolocation api?

hey everyone,

i'm trying to integrate a pretty popular IP geolocation API for regional content delivery and some basic fraud detection in our SaaS. for the most part, it works as expected, but we've hit a pretty annoying wall with specific data points.

for about 5-7% of our traffic, we're seeing really significant ip data discrepancies. this isn't just minor variations like a few miles off on a city, we're talking about city, region, and ISP data being wildly off, sometimes even across continents. and we're fairly certain these users aren't behind VPNs or proxies; our other detection methods aren't flagging them. it's causing real issues with our content targeting logic and, frankly, making our fraud detection a bit unreliable for these edge cases.

here's an example of what we're seeing:

// Our API response for an IP:
{
  "ip": "192.0.2.1",
  "country_code": "US",
  "country_name": "United States",
  "region_name": "California",
  "city": "Los Angeles",
  "isp": "Comcast Cable"
}

// Expected/Verified data for the same IP (from another reliable source/manual check):
{
  "ip": "192.0.2.1",
  "country_code": "CA",
  "country_name": "Canada",
  "region_name": "Ontario",
  "city": "Toronto",
  "isp": "Bell Canada"
}

we've tried a bunch of troubleshooting steps: checked for common issues like IPv4 vs IPv6, ensured headers like X-Forwarded-For are correctly passed through our load balancers, and even cross-referenced with a secondary, less accurate, free service which sometimes aligns with our "expected" data. no caching issues on our end that we can identify, and the API provider's status page shows no outages.

are there common, deeper technical reasons for such severe ip data discrepancies beyond the usual suspects? could this be specific routing issues, or something related to how certain ISPs handle their IP blocks that geolocation services just struggle with? i'm really looking for advanced debugging tips or overlooked configuration nuances that might explain this.

waiting for an expert reply.