Geolocation API failing on lookup?

Hey everyone,

I've been knee-deep working on our 'What is My ISP?' tool, and it heavily relies on accurate IP geolocation data. Lately, I've noticed some really inconsistent results, which is starting to become a real headache.

The problem is, when we perform an IP lookup, the geolocation API we're using frequently returns null or just plain incorrect values for crucial fields like 'country' and 'city'. This isn't happening for obscure IPs either; it's for valid, public IP addresses that absolutely should have reliable data. It's causing inaccurate reporting for our users, and that's not ideal.

Here's a simplified example of what we're seeing in the console:

{
  "ip": "203.0.113.45",
  "isp": "Example ISP Inc.",
  "country": null,
  "city": "",
  "latitude": null,
  "longitude": null,
  "error": "Geolocation data incomplete"
}

As you can see, crucial data is just missing or incomplete. My main question is, what are the most common reasons for a geolocation API to return such inconsistent or null data for specific fields, especially 'country' and 'city'? Are there specific IP ranges that are notoriously harder to geolocate accurately, or could this be a common API misconfiguration I might be overlooking?

Anyone faced this before with their IP lookup services?