No. This project is not about gathering information which we intend to sell to any parties. Not only the ISP-facing side of this service is provided free-of-charge, but the consumer-side of this service as well.

The validator service provided at opengeofeed.org/validator uses the geofeed_validator Python module, which is available as an open-source project from Github.

The validation process itself makes sure the following information inside the feed is valid:

• ISO3316 Country Codes
• ISO3316 Region/Subdivision Codes
• IP networks are public, non-multicast, non-loopback networks
• IP networks are not contained multiple times within the same feed
• An ISO3316 Country Code is provided if there is an ISO3316 Region and matches the country of that region
• An ISO3316 Country Code is provided if there is a city or zipcode defined.
• [draft extension] If provided, if the default allocation size is valid for the IP version of the IP network.

OpenGeoFeed is provided free-of-charge to all interested parties.

We would be happy to hear from you. If you need to get in touch with us, please drop us an email at info@opengeofeed.org.

No. OpenGeoFeed is designed in a way that only the owner of given IP network can announce their geolocation information.

More information about the details of our verification process can be found at How do you establish the owner relationship of a given network?.

Right now we would like you to submit your questions via email.

Please have a look at the How to contact you? FAQ and don’t hesitate to drop us an email.

self-published geofeeds, as defined in Internet Draft: Self-published IP Geolocation Data provide means for a service provider to announce the geolocation information for their IP address ranges.

OpenGeoFeed was developed and is hosted by ANEXIA Internetdienstleistungs GmbH.

We firmly believe in the ideas behind self-published geofeeds.

At ANEXIA we know the issues that arise when hosting multiple IP subnets in regions all over the world and the time required to update that information at IP Geolocation database providers.

Thus we support the idea of having an approach to publish this information ourselves and have IP Geolocation database providers fetch that information. Also, we believe that this method also offers a benefit to aforementioned database providers as well, because updating their databases can be automated and hence the administrative burden on their end can be minimized as well.

Feeds are updated periodically. Whilst the AS-specific feeds are updated about once every 5-10 minutes right now, the public feed is updated hourly.

Please also bear in mind that we may cache responses for a short while, in order to be able to operate this service more efficiently.

A quote from the section “Motivation” of the aforementioned Internet Draft:

Providers of services over the Internet have grown to depend on best-
effort geolocation information to improve the user experience.
Locality information can aid in directing traffic to the nearest
serving location, inferring likely native language, and providing
additional context for services involving search queries.

When an ISP, for example, changes the location where an IP prefix is
deployed, services which make use of geolocation information may
begin to suffer degraded performance. This can lead to customer
complaints, possibly to the ISP directly. Dissemination of correct
geolocation data is complicated by the lack of any centralized means
to coordinate and communicate geolocation information to all
interested consumers of the data.