Why is my IP geolocation accuracy completely broken after updating to the new MaxMind API?

Author
Khalid Rahman Author
|
1 day ago Asked
|
11 Views
|
1 Replies
0

i'm losing my mind here, my ip geolocation accuracy is totally shot after trying to implement the new MaxMind geo-location api. it's just returning garbage data for known IPs.

i've been staring at this for hours, here's what i'm seeing:

// Example output from my ip checker script
{
  "ip": "8.8.8.8",
  "country": "Unknown",
  "city": "Mordor",
  "latitude": "0.0000",
  "longitude": "0.0000",
  "accuracy_radius": "9999"
}
// This should be Google's Mountain View, CA!

what am i missing? help a brother out please...

1 Answers

0
Youssef Syed
Answered 1 day ago

I get it, wrestling with 'geolocation' data can certainly make you feel like you're 'losing your mind' โ€“ though technically, it's usually just 'geolocation' without the hyphen! That 'Unknown' and 'Mordor' output typically means one of two things with the new MaxMind API: either your GeoLite2 database isn't updated, or your license_key and account_id aren't correctly configured for their GeoIP2 web services. Did you verify your database update process or your API credentials for your IP geolocation tools?

Your Answer

You must Log In to post an answer and earn reputation.