April IP geolocation database released, new stucture
The April release is now available.
For previous users of the database there is some changes in the database structure. These mods are from suggestions from users in the forum :
1) IP are now stored using the following formula (256 times bigger int than before) :
ip = ((A*256+B)*256+C)*256
Why? to use directly the INET_ATON function in MySQL. Now queries are simply :
SELECT * FROM `ip_group_city` where `ip_start` <= INET_ATON('74.125.45.100') order by ip_start desc limit 1IP are stored as bigint NOT int(11) anymore...
2) Added reserved and unallocated IP classes (iana.org)
3) Canada and USA region codes are now using the FIPS standard (no more 2 letters abreviation)
4) Country table renamed to iso3166_countries
In a few days I will release an even smaller database. City, latitude and longitude will be store in different tables because there is alot of redundant data...
Stay tuned, during the month of april I will release some new tools as well!
- subjects:


Comments
Thanks
Marc,
This is fantastic stuff, thanks.
The accuracy for international ranges is really good.
The Feb DB list, used to point these ip's to a Lat/Long which was on the ocean floor on the google earth map :)
221879,62.24.139.253,OK,GB,United Kingdom,P2,Warrington,Warrington,,53.3833,-2.6
149950,202.27.184.100,OK,NZ,New Zealand,E7,Auckland,Auckland,,-36.8667,174.767
Thanks,
Haarith
Re : some ranges are incorrect
Range were ok it's just that there was a problem with the Country tables. For some reasons I got an old one that was in the fips standard and the ip use ISO standard...
It's fixed now.
Thanks for letting me know.
some ranges are incorrect
hi,
since the last update, some ranges give incorrect information, so it seems.
for example:
the range 80.70.128.0 - 80.70.143.255 appears as if it in italy, when it is actualy in israel.
the range 192.115.80.0 - 192.115.83.255 is also in israel but is shown as in netherlands.
can this be updated?