GeoIP2 Release Notes - 2014 Archive
More IPs mapped to postal codesDecember 16, 2014
As part of our ongoing work to return more data, MaxMind has increased the number of IP addresses that map to a postal code.
An ISP may allocate an IP range over multiple postal codes. In such cases, MaxMind cannot accurately determine the exact postal code associated with an IP address in that range. Previously we only included a postal code if we were confident of the resolution. Now, we include more postal codes, returning a postal code within a 50km radius.
We are doing this as a convenience to our customers who want to use the postal code instead of the city to link to other data.
In addition, we've added Poland and Portugal to the list of countries for which we return postal codes. The full list of countries for which we provide postal codes now includes the following:
Argentina, Australia, Austria, Belgium, Brazil, Bulgaria, Canada, Croatia, Czech Republic, Denmark, Finland, France, Germany, Hungary, Iceland, India, Italy, Malaysia, Mexico, Netherlands, New Zealand, Norway, Pakistan, Poland, Portugal, Russia, Slovakia, South Africa, Spain, Sweden, Switzerland, Thailand, United Kingdom, United States.
Improvements to accuracy in Japan, South Korea and Venezuela and change in lat/lon returnedNovember 25, 2014
We have improved the coverage and accuracy for GeoIP City in Japan, South Korea and Venezuela. We expect to make further improvements to the accuracy in South Korea over the next few weeks.
If we are unable to determine the city or region for IP addresses in Argentina, Austria, Bangladesh, Belgium, Bulgaria, Brazil, Canada, Chile, Colombia, Czech Republic, Denmark, Egypt, Spain, Finland, Greece, Hungary, Indonesia, Ireland, Iran, Netherlands, Norway, Peru, Philippines, Poland, Portugal, Russia, Sweden, Thailand, Turkey, Ukraine, we will return a latitude and longitude of the largest city in the country.
- MaxMind’s most accurate IP geolocation data – GeoIP2 web service data accurately geolocates 5% more IPs to postal codes and 3% more IPs to cities than GeoIP Legacy data
- Location names in eight popular languages
- Support for IPv6 addresses
- This release updates the API to use version 2.1 of our GeoIP2 web service.
omni()method has been replaced with the
cityISPOrg()has been removed.
city()method now returns ASN, ISP, and organization data.
- As noted in the web service release notes, several fields that were incorrectly strings in version 2.0 of the web service have been changed to be numeric.
Users of version 2.0 are not affected, but they are encouraged to update to the new version. Only serious functionality issues will be fixed in version 2.0.
GeoIP2 Web Service v2.1July 18, 2014
MaxMind has released version 2.1 of the GeoIP2 web service. Changes include:
- The Omni endpoint was renamed Insights. The path for this endpoint has changed accordingly.
- The City/ISP/Org endpoint was removed. The City endpoint now returns all of the data previously returned by City/ISP/Org.
- In v2.0,
autonomous_system_number, and all of the
confidencevalues were incorrectly returned as strings. These are now returned as integers.
To upgrade, please use the updated service URIs specified in our developer documentation.
For the version 2.0 endpoints, the City endpoint will now include ISP/Org data. The other output for the 2.0 endpoints was unchanged.
Type Change to GeoIP2 Metro Code FieldApril 1, 2014
In previous GeoIP2 databases, the
metro_code was incorrectly represented as a
string. This has been corrected and now
metro_code is internally represented
uint16. This should not affect users of the official Java, .NET, Perl,
or PHP GeoIP2 APIs. The Python API will now return an integer rather than a
metro_code. Users of libmaxminddb or third-party APIs may be
This page was last updated on June 6, 2023.