I have been following the IPFire location project for some time now because of how impactful the project is to open-source cybersecurity efforts. The database is used by companies like TOR, F-Droid, and IPFire itself.
I often reach out to OSS projects to use our data in the projects, bringing the highest quality of IP location data possible to their users. Through a community outreach effort, we have secured a small yet active part in many OSS projects, providing the best possible data backed by active and ever-vigilant support to end-users and our community at large.
IPFire were frustrated by the IP geolocation data industry, to the point they built their IP database.
I am going to compare our Location data with their IPFire location to show there is room for us to collaborate and bring our data insights to IPFire location data. We can make IP geolocation data a major open-source software around the world.
Proposal
Integrate IPinfo Lite data into IPFire Location data natively. We are not asking to replace the IPFire location data service, but rather to enhance the data quality by incorporating our data into the project.
Considering the impact IPFire location data has had, we are not asking to adopt our IPinfo Lite data as a first-party location data provider. However, since our data is shared as CC-BY-SA 4.0 (the same license as IPFire location data), which permits commercial distribution and modification, we ask for the data insights from our data to be incorporated into the project.
Data Accuracy Comparision
First, our data is going to be super accurate as we use our ProbeNet platforms with around 1,200 PoPs to run active measurements all over the world to generate first-party network data-based IP geolocation. This makes us one of the few, if not the only, IP geolocation provider using a proprietary self-built network like this, ensuring a significant amount of accuracy points over anything the industry has observed. Traditional IP geolocation data relies on ASN/ISP reported location data primarily.
Moreover, we are not just running basic active measurements. We have dozens of engineers specializing in internet measurements, research and development, data, data, and data.
Our data is completely unbeatable.
Evalution (08/31/2025 - 22:39:06 UTC )
This is not going to be an in-depth comprehensive evaluation considering the challenges I had to look up the IP addresses from the database so I will use their website lookup service: https://www.ipfire.org/location/lookup/8.8.8.8
We are going to select a few IP addresses from our IPinfo Accuracy page: IPinfo's Geolocation Data Accuracy - IPinfo.io
5.253.227.173
- IPFire: US
- IPinfo Lite: DE
5.253.227.173 | Frankfurt am Main, AS205659, & VPN Not Detected - IPinfo.io
23.230.104.41
- IPFire: US
- IPinfo: DE
23.230.104.41 | Frankfurt am Main, AS203061, & VPN Not Detected - IPinfo.io
193.233.63.52
- IPFire: EU (No country mentioned)
- IPinfo: RU
193.233.63.52 | Moscow, AS42745, & VPN Not Detected - IPinfo.io
50.114.4.7
- IPFire: US
- IPinfo: SG
50.114.4.7 | Ottawa, AS64199, & VPN Not Detected - IPinfo.io
We are addressing the accuracy and licensing issues that IPFire faced with their previous data provider. Therefore, we welcome collaboration and partnership with the IPFire platform and the community at large.