IP geolocation database release notes
Release notes about the IP monthly database. You can also get updates on our RSS feed or on Twitter.
April release
April update is out.
March release
Important changes in this release. First, gmtOffset-dstOffset-timezone fields were removed. Why? We released a timezone database which gives the real gmtoffset for a specific date. Unfortunately, we cannot add it directly into the database because the gmtoffset can change during the month. Please see the timezone database page for more info. Second, we added US metrocode to the database, some users requested it.
February release
February update is out.
January release
January release is out. No changes, simply an update.
December release
December release is out!
November release
November release is out! We made some changes in the way the database are build to save time (more automatic script), please let us know if you see any problems in the new release.
October release
October release is out!
September release
Added timezone field from Geonames. Fixed vietnamese regions.
August release
Removed couple of IP /8 classes that are not reserved anymore (iana.org).
Timezone fixed in the new release
Timezone bug is now fixed. Please let us know in the forum if you see any other problems.
July release
The new release is out, no major change this month. We fixed a little problem, iso3166_countries table was using memory storage engine instead of MyISAM for databases with multiple tables. The original (feb09) database format that we stop using 3 months ago was not updated. Next month we will add areacode to US/Canada IP address. If you see any incoherent results, please let me know in the forum.
June release
The new release of the database now include timezone GmtOffset and DstOffset from geonames.org. If you see any bugs or incoherent results, please let me know in the forum.
May release
The database is now offered in different formats (single or multiple tables, 3 or 4 digits...). Scripts that collect data were rewritten almost from scratch to increase performance (near 10 times!), now i'm loading the Maxmind CSV DB as the raw data instead of the geoiplookup command in loop. It was tested and retested but if you see bugs or incoherent results, please let me know in the forum. In the next release I will add the timezone...
CSV format
CSV format now available for MSSQL users
Private networks FIXED
The problem with private networks range has been fixed (172.16.0.0 – 172.31.255.255 and 192.168.0.0 – 192.168.255.255). If you see anything wrong please let me know in the forum.
Private networks
There should be no problem with the current release except for private network IP (172.16.0.0 – 172.31.255.255 and 192.168.0.0 – 192.168.255.255). It's fixed on our side (for the API) but the fix will appear in the May release. If you see anything wrong please let me know in the forum.