Accurate IP geolocation matters. Whether you're running a content delivery network, protecting accounts from fraud, or simply showing the right language or currency to users — getting someone's location wrong can cause frustration, lost conversions, or unnecessary support tickets.

But the truth is, geolocation databases often get things wrong.

Geofeeds are a way for ISPs, hosting providers, and network operators to fix that. A geofeed is a simple, self-published list that tells geolocation providers where your IP ranges are actually being used — down to the country, region, or city level.

In this guide, we’ll explain what geofeeds are, how they work, why they’re important, and how to set one up — including how to submit it to providers like IPLocate to help keep your location data accurate.

What is a geofeed?

A geofeed is a plain-text file (in CSV format) where you list your IP ranges and their correct physical location. It's designed to be machine-readable and easy to update. Geolocation providers like IPLocate can ingest this data and use it to correct or enhance their IP-to-location mapping.

Think of it as a public, authoritative source for the location of your IPs — maintained by you.

Geofeeds are standardized under RFC 8805, which defines how the file should be structured and published.

The geofeed format

At a technical level, a geofeed is a CSV file listing your IP ranges and their corresponding location data.

Each line contains:

ip_prefix,country_code,region_code,city_name,postal_code

Only the ip_prefix is required. However, the more fields you include, the more useful and precise your data will be.

Field	Required	Description
ip_prefix	Yes	The IPv4 or IPv6 network in Classless Inter-Domain Routing (CIDR) notation. Example: 192.0.2.0/24
country_code	Yes*	The two-letter ISO 3166-1 alpha-2 country code. Example: US for the United States. * Optional according to the geofeed spec, but without providing at least a country code, a geofeed is not useful.
region_code	No	The ISO 3166-2 subdivision code representing the state or province. Example: US-CA for California. Region codes must be a valid ISO 3166-2 region code, or they will be ignored.
city_name	No	The name of the city. Example: Los Angeles
postal_code	No	The postal code or ZIP code. Example: 90001

Example:

192.0.2.0/24,US,US-CA,Los Angeles,90001
2001:db8::/32,DE,DE-BY,Munich,80331

Lines starting with # are treated as comments.

You can also view some live example geofeeds:

• https://geofeed.tools.telstra.net/geofeed.csv
• https://lg.telia.net/ripe/AS25400_geofeed.csv
• https://www.f5.com/content/dam/f5/geofeed.txt

How to set up a geofeed

1. Create your geofeed file

Use any text editor or spreadsheet tool. Save the file as geofeed.csv, following the format above.

Make sure to:

• Encode it in UTF-8
• Use commas as separators (no tabs)
• Include, at a minimum, the ip_prefix and country_code fields
• Include a header or comment line if you like

2. Host it publicly

The file must be accessible online without authentication. You have a few options:

• Self-host on your website (e.g. https://yourdomain.com/geofeed.csv)
• GitHub repo – upload the CSV and link to the raw file URL
• Google Sheets – publish to the web and link to the CSV version

3. Add a pointer in WHOIS/registry records

To help geolocation providers find your feed automatically, add a reference to your IP registry object (like RIPE, ARIN, or APNIC).

Some registries (such as APNIC or RIPE) support this via a geofeed attribute. Example:

geofeed: https://yourdomain.com/geofeed.csv

For other registries, add the geofeed to the remarks or comment attribute. Example:

remarks: Geofeed https://yourdomain.com/geofeed.csv

By doing this, geolocation providers can automatically find, verify, and start consuming your geofeed on a regular basis. This means you won’t need to let geolocation providers know when you update your geofeed.

RFC 9092 recommends this as best practice.

4. Submit to geolocation providers (including IPLocate)

If you’ve added a pointer in WHOIS/registry records, this step is optional. Good geolocation providers will automatically find your geofeed when they scan registry records, and will add your geofeed data to their database. For example, IPLocate does this automatically every day.

However, if you have not added a pointer in WHOIS/registry records, or to be sure that every geolocation provider will find your geofeed, you can notify providers directly.

For IPLocate, submit your geofeed URL on our corrections page.

For other providers, you can find their contact details below:

• IPLocate: Submit a data correction
• MaxMind: GeoIP Data Correction Request Form
• IP2Location: https://www.ip2location.com/contact
• IPinfo: https://ipinfo.io/corrections
• IPGeolocation.io: [email protected]
• DB-IP: https://db-ip.com/contact/
• Digital Element: https://www.digitalelement.com/contact-us/

When contacting these providers, include:

• A link to your geofeed.
• Proof of ownership of the IP ranges you are submitting. If you can use a work email address that’s referenced in your WHOIS/registry records, this is usually sufficient. Otherwise, include any additional details that will help the provider verify your geofeed.

How geofeeds help

Now that you know how they work, let’s look at why geofeeds are so useful:

Fewer incorrect locations

Stop getting support tickets from users asking, "Why does your service think I’m in the wrong country?" Geofeeds let you proactively fix these issues.

Better localization & UX

Ensure users see the right content, currency, and language — without needing to manually override locations in your app.

Less fraud & fewer false positives

Incorrect geolocation can lead to logins being flagged or blocked unnecessarily. Accurate IP data helps avoid this.

Faster corrections

Instead of waiting weeks for a geolocation provider to update your IPs manually, a geofeed lets them ingest your data automatically.

Less support overhead

Publishing a geofeed reduces the burden on your support team and your users.

Where to find existing geofeeds

For service operators looking to improve their geolocation data, various resources and tools are available to help you find geofeeds:

CAIDA Datasets

The Center for Applied Internet Data Analysis (CAIDA) offers a comprehensive collection of datasets, including geofeeds scanned and collected from WHOIS data. Explore their datasets here.

Geofeed-Finder

This utility discovers and retrieves geofeed files from WHOIS data, validates ownership of prefixes, manages caching, and ensures ISO code compliance. Access the tool on GitHub: geofeed-finder.

OpenGeoFeed

A free service designed to assist in managing geofeeds. It allows network operators to announce geolocation information for their IP address ranges securely. Learn more at OpenGeoFeed.

Conclusion

If you're managing IP space, a geofeed is one of the easiest, most powerful tools for improving the accuracy of IP geolocation. It’s simple to set up, easy to update, and widely supported by the industry.

By publishing your geofeed and submitting it to providers like IPLocate, you're making the internet just a little more accurate — for you and your users.

Have a geofeed? Submit it on our corrections page

Need an IP Geolocation API? Try IPLocate.io — trusted, fast, and accurate.