URGENT: my IP lookup tool's geolocation accuracy is totally broken, what am i missing?

hey everyone, still stuck with this darn IP lookup tool showing completely wrong locations, its driving me nuts! i thought i had a handle on it after the "tourist" IP discussion, but it's gotten so much worse.

• The Core Problem: it's not just random "tourist" IPs anymore; my tool is consistently misidentifying locations for critical user segments, especially those using VPNs or mobile data. its like the entire IP geolocation API logic is just failing me.
• Impact: this is seriously messing up my geo-targeting for ads and even basic analytics. my user segmentation is a complete joke right now and i'm wasting ad spend targeting the wrong regions.
• What I've Tried (and Failed At):
  • i've switched between two different IP geolocation APIs (ipstack and ipinfo.io), but the results are still unreliable. both of them give me similar, incorrect data for the same IPs.
  • i've double-checked all API keys and rate limits; everything seems fine on that front. no obvious errors or throttling.
  • i've reviewed my backend code for any caching issues or logic errors that might be holding onto old data. cleared caches, restarted services, but no change.
  • i've tested with known VPN IPs and mobile IPs from friends; often it gets them completely wrong or gives a very generic data center location that's miles from the actual user.
• Specific Observations: it seems particularly bad for mobile IPs in certain countries (like india and parts of southeast asia) and for almost all VPN connections. sometimes it shows a city miles away from the actual one, or even a completely different country. for example, a mobile user in mumbai might show up as being in bangalore or even a generic US data center.
• Desperate Plea: i'm completely out of ideas and this is impacting my business directly. i mean, what's the point of an IP lookup tool if it can't even tell me where my users are? has anyone faced this level of persistent geolocation inaccuracy with their chosen IP geolocation API provider? what obscure thing could i be overlooking? could it be something with my server's egress IP or something equally weird?

thanks in advance for any insights, i'm really pulling my hair out here!