Why is my internet provider detection tool showing weird results?

Hey AdsVolt community,

We launched our 'What is My ISP?' web tool a while back, which generally works well for internet provider detection and showing users their current ISP. It's supposed to be a straightforward IP address lookup service, but lately, it feels like it's developed a mind of its own.

The Problem:

Recently, we've started noticing some really inconsistent and frankly, bizarre results for a segment of our users. It's like the tool has decided to get creative with its responses:

• Sometimes it reports a major cloud provider (like AWS or Google Cloud) as the ISP for a residential user. Yeah, because Aunt Mildred is totally hosting her cat blog on AWS.
• Geolocation is occasionally off by hundreds of miles, even for non-VPN users. I've seen people in New York supposedly browsing from Kansas.
• The biggest headache: inconsistency. The same user, refreshing the page, might get two completely different ISP names or locations within minutes. It's like a magic 8-ball of network data.

What We've Tried:

We've been scratching our heads over this, trying to debug what's going on:

• We've double-checked our API calls to third-party IP lookup services (MaxMind, IPinfo.io) – they seem to return correct data when queried directly from our server.
• Scoured our server logs for any errors or unusual traffic patterns that might indicate a problem on our end. Nothing obvious jumping out.
• Ensured our caching layer isn't serving stale data, though this feels like more than a simple caching issue given the wild variations.
• Tested extensively with various VPNs and direct connections, but the inconsistencies seem somewhat random and not tied to specific network types.

The Ask:

What could be causing these wild discrepancies in our internet provider detection and IP address lookup? Are there common integration pitfalls with multiple IP services, or specific HTTP header issues we should be looking into? Any obscure server configurations or even client-side browser quirks that might mess with how the IP is reported or resolved?

Help a brother out please...