ENTRDEESFRPTIT
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 transfer contract generator 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

What Is Geofeed (RFC 8805)?

Geofeed is a technical standard defined in RFC 8805 that allows IP address holders to self-publish the geographic location of their network prefixes in a machine-readable CSV format. The standard was published by the IETF in 2020 and has since been adopted by all major geolocation providers including MaxMind, IP2Location, IPinfo, and Google as an authoritative source for IP-to-location mapping corrections.

The geofeed mechanism works by hosting a CSV file at a publicly accessible HTTPS URL and referencing it from the network holder's RIR database objects (inetnum/inet6num in RIPE, NetRange in ARIN). CDNs like Cloudflare, Akamai, and Fastly consume geofeed data to optimize content routing — directing user requests to the nearest edge server based on the corrected IP geolocation rather than stale database entries.

Each geofeed entry consists of an IP prefix in CIDR notation followed by ISO 3166-1 alpha-2 country code, optional ISO 3166-2 region code, city name, and postal code. Search engines use this data to serve region-appropriate search results, and advertising platforms use it for geo-targeted ad delivery. RFC 9632 (2024) extended the standard with cryptographic signatures for enhanced authenticity verification.

Why IP Geolocation Accuracy Matters

IP geolocation accuracy directly impacts content delivery optimization by determining which CDN edge node serves a user's request. Incorrect geolocation can route traffic to distant servers, adding 50-200ms of latency per request. For organizations that have transferred IPv4 blocks between regions, stale geolocation data in commercial databases causes persistent routing inefficiencies until corrected via geofeed.

Regulatory compliance depends on accurate IP geolocation, particularly under GDPR (European Union), LGPD (Brazil), and similar data protection frameworks that restrict cross-border data flows. If a European user is incorrectly geolocated to a non-EU country, their traffic may be routed through non-compliant infrastructure. Similarly, content licensing restrictions (streaming services, gaming platforms) rely on geolocation to enforce regional availability.

Fraud detection systems use IP geolocation as a primary signal for identifying suspicious transactions — a login attempt from an IP geolocated to a different country than the user's known location triggers risk scoring. Inaccurate geolocation data causes both false positives (legitimate users blocked) and false negatives (fraudulent access permitted). Ad targeting accuracy, which directly affects publisher revenue, also degrades when geolocation databases contain stale information.

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.