Feature Request: Add an IGeoIPDatabaseProvider for IPinfo country database

[abdullahdevrel]

I work for IPinfo and was checking out the project. I think if you are interested, you can package an IP geolocation database by incorporating the access token of the IPinfo Lite database. If you build out the download mechanism and package in the access token.

https://ipinfo.io/developers/ipinfo-lite-database

• It is updated daily, with zero compromise to accuracy. There is no range clustering, and the database provides full accuracy.
• It includes country and ASN information in the same database.
• The data granularity reaches individual IP level.
• It is licensed under CC-BY-SA 4.0, permitting commercial usage, redistribution, and repackaging.
• Available file formats include: CSV, MMDB, JSON and Parquet
• The data is tabular and unnested, making it very easy to use. The dataset includes both IPv4 and IPv6 in a single file.

Database schema

Field Name	Example	Data Type	Descrption
network	154.24.39.204/30	TEXT	CIDR/IP range or single IP address
country	Canada	TEXT	Country name
country_code	CA	TEXT	Two-letter ISO 3166 country code of the IP addresses
continent	North America	TEXT	Continent name of the IP location
continent_code	NA	TEXT	Two-letter continent code of the IP location
asn	AS174	TEXT	Autonomous System Number, an organization that owns the IP range block
as_name	Cogent Communications	TEXT	Name of the AS (Autonomous System Number) organization
as_domain	cogentco.com	TEXT	Official domain or website of the ASN organization

Documentation: https://ipinfo.io/developers/ipinfo-lite-database

Samples: https://github.com/ipinfo/sample-database/tree/main/IPinfo%20Lite

The IP database can be simply downloaded with only an free access token:

curl -L https://ipinfo.io/data/ipinfo_lite.csv.gz?token=$TOKEN -o ipinfo_lite.csv.gz

We also have a free IPinfo Lite API service based on this database that supports unlimited requests. Let me know what you think. Thanks!

[Sebbs128]

Thanks @abdullahdevrel

Supporting the MMDB from IPinfo via an IGeoIPDatabaseProvider would be a good fit, however packaging that database directly in my nuget packages is something I'd want to avoid (due to licensing for the end-user and infrequency of updates to my nuget packages). Stumbling upon IPinfo may have even been the reason I decided to abstract out the GeoIP provider. I don't think incorporating the API service would be appropriate though, as it would introduce a lot more latency (due to the http round trip), and reliance on an external service would be bound to introduce other issues.

Supporting a download mechanism is an interesting one. I was originally thinking that fetching new databases and updating the config should be an end-user concern, though potentially removing that administration burden does seem appealing. I'll need to give that some more thought as I'm also considering removing the requirement that the database even be in the local file system.

[abdullahdevrel]

Hey @Sebbs128 Thank you for reviewing the request so carefully.

packaging that database directly in my nuget packages is something I'd want to avoid

You do not need to package the database directly. You only need to include your project-specific IPinfo access token. Your end-users will download the database using your project-specific IPinfo access token.

due to licensing for the end-user

We do not have an End User Licensing Agreement (EULA) like everyone else. The database is shared under CC-BY-SA 4.0, which permits commercial redistribution of the database.

We only require a public attribution statement stating that your project uses our data. The attribution is less about a marketing statement and more about letting other projects know that this project uses our data. This enables your end users to reach out to us directly about issues with our data.

don't think incorporating the API service would be appropriate though, as it would introduce a lot more latency (due to the http round trip), and reliance on an external service would be bound to introduce other issues.

Entirely your call. :)

We just want to give you the option that fits your project. We provide not only the data but also the infrastructure to back up the data. We are currently processing billions of requests through that endpoint, so I think reliability or performance should be a major concern.

I'll need to give that some more thought as I'm also considering removing the requirement that the database even be in the local file system.

Awesome! Ping me if you have any issues or concerns. Cheers!