IP geolocation API accuracy help

hey folks, i'm running a simple web tool called 'What is my City Name'. it's pretty straightforward: user visits, we show their city based on their IP. nothing fancy, but it's been getting some traction.

the main issue i'm hitting right now is accuracy with the IP geolocation API i'm using. users, especially on mobile or with certain ISPs, are frequently reporting incorrect cities or even regions. for a tool literally named 'What is my City Name', this is kinda embarassing and definitely hurts trust.

here's what i've tried so far:

• started with a free tier IP lookup service, quickly ran into rate limits and pretty bad accurracy.
• switched to a more reputable, but still budget-friendly, IP geolocation API. it's better, but still not great. i'm seeing maybe 70-80% accuracy for city level, which is not what i want.
• thought about using browser's geolocation API, but privacy prompts and users denying permissions make it unreliable as a primary solution. plus, i want server-side lookup for initial load.
• i've also implemented some basic caching, but that's for performance, not accuracy.

i'm trying to figure out if there are specific best practices i'm missing, or maybe a premium IP geolocation API that offers significantly better accuracy without costing an arm and a leg for a small tool like mine. is there a way to combine multiple sources intelligently? what about handling mobile carrier IPs or satellite connections better?

really need some guidance here to get this right. help a brother out please...