Free Tool
Geofeed CSV Generator
Generate RFC 8805 compliant geofeed CSV files for your IP prefixes. Upload to RIPE NCC to improve geolocation accuracy of your IP address blocks. A free tool by IPv4Center.
IP Prefix Entries
Entry #1
geofeed.csv0 entries
Add a prefix entry to see the preview...
RFC 8805 Format
The geofeed format follows RFC 8805. Each line contains: prefix, ISO 3166-1 country code, ISO 3166-2 region code, city name, and postal code. Region code, city, and postal code are optional but recommended. Also check our <a href="https://ipv4center.com/tools/transfer-contract-generator" target="_self">transfer contract generator</a> for IPv4 transactions.
What is a Geofeed File?
Why Use Geofeeds?
- Correct geolocation for your IP blocks in major databases
- Ensure users see the right content based on their actual location
- Improve CDN routing and reduce latency for end users
- Prevent regional restrictions from incorrectly blocking your users
- Standardized RFC 8805 format recognized by all major RIRs
Who Needs This?
- ISPs and network operators managing IP address allocations
- Companies that have purchased or leased IPv4 blocks
- Data center operators with IP space in multiple locations
- Anyone whose IP blocks show incorrect geolocation
- VPN and hosting providers with global infrastructure
Frequently Asked Questions
What is a geofeed file (RFC 8805)?▼
A geofeed is a self-published CSV file, defined in RFC 8805, that maps your IP prefixes to geographic locations. Each line lists a prefix together with its ISO 3166-1 country code, optional ISO 3166-2 region code, city, and postal code. Geolocation providers consume this file to correct where your IP addresses appear — especially important after you have bought or leased IPv4 blocks previously used in another country.
How do I publish my geofeed so providers can find it?▼
Host the generated geofeed.csv at a publicly accessible HTTPS URL, then reference it from your RIR database objects. In the RIPE Database you can add a dedicated "geofeed:" attribute to your inetnum/inet6num object, or a "remarks: Geofeed https://example.com/geofeed.csv" line. ARIN, APNIC, and the other RIRs support similar remarks-based references, allowing geolocation providers to discover your file automatically.
How often should I update my geofeed file?▼
Update it whenever the physical location of a prefix changes — for example when you announce a block from a new data center or reassign address space to customers in another country. There is no mandatory schedule, but providers periodically re-fetch the file, so an outdated geofeed will keep propagating wrong locations. Keep one stable, always-current URL rather than publishing new URLs for each revision.
How long do geolocation providers take to apply geofeed changes?▼
Major geolocation databases — MaxMind, IPinfo, IP2Location, and Google — re-crawl geofeeds on their own schedules. In practice, changes are typically reflected within 1 to 4 weeks, while some providers pick them up within days. If a correction is urgent, you can additionally submit a manual correction request directly to each provider.
What are the CSV format requirements for a valid geofeed?▼
RFC 8805 requires a UTF-8 encoded CSV with one entry per line in the order: prefix, country code, region code, city, postal code. The country must be an ISO 3166-1 alpha-2 code and the region an ISO 3166-2 code. Comment lines start with "#", and all fields except the prefix and country may be left empty. The postal code field is optional and discouraged for privacy reasons.
Is this geofeed generator free to use?▼
Yes — the tool is completely free and requires no account. The CSV is generated entirely in your browser, so your prefix data never leaves your device. It is one of the free tools provided by IPv4Center alongside the IPv4 marketplace and transfer services.
More Free Tools
RIR Transfer Contract Generator