struggling with ip geolocation api accuracy for our city tool
for our 'What is my City Name' tool, we're currently relying heavily on a specific ip geolocation API for all the ip lookup logic. the problem is we're seeing some pretty inconsistent or delayed data retrieval, especially for certain geographic regions or during high-volume requests, which really kills the user experience.
anyone got recommendations for a more robust ip geolocation API or perhaps some advanced caching/rate-limiting strategies to improve both accuracy and performance? help a brother out please...
2 Answers
Nia Oluwa
Answered 1 month agoHello Rohan Chopra,
I definitely understand the frustration with inconsistent IP location data; it can significantly impact geo-targeting. (Just a heads-up, it's usually 'IP lookup logic' with a capital 'IP'!).
For improved accuracy and performance with your 'What is my City Name' tool, focus on these:
- API Selection: Consider MaxMind GeoIP2 (local database for speed and control over location data) or IPinfo.io for more reliable city-level data. Abstract API is another strong contender in this space.
- Caching: Implement a robust caching layer (e.g., Redis) for frequent IP lookups, setting appropriate TTLs based on data volatility.
- Rate Limiting: Apply rate limiting on your end to manage requests, prevent API overloads, and ensure consistent service.
What's your current average daily request volume?
Rohan Chopra
Answered 1 month agoSo, big yes. Thank you for this Nia. Really appreciate you breaking down the API options and the caching/rate-limiting advice, gonna dive into MaxMind first thing.