Geofeed
Sign in
IPv4 · IPv6 · RFC 8805

Publish your network's location data

Geofeed helps network operators create and maintain public geolocation feeds for IPv4 and IPv6 prefixes. Manage location records in one place and share a stable CSV URL with geolocation providers.

Open your account

Build and maintain your geofeed

Add IPv4 and IPv6 networks with country, region and city fields.

Validate and import CSV records, or load announced prefixes from RIPEstat by ASN.

Publish a CSV URL that stays the same when you rename a feed or update its entries.

Optionally compare declared countries with MaxMind results. A match is not proof that a provider uses your feed.

How geofeed publishing works

1. Create a feed and add the prefixes and locations you want to publish.

2. Copy the public CSV URL and add a geofeed reference to network objects you control, where your registry supports it.

3. Check the CSV response and keep the location records up to date.

An open CSV format for IP geolocation

Geofeeds describe network locations as CSV rows: network prefix, country code, region code, city and optional postal code. This tool publishes feeds in the RFC 8805 format. ISO country and region codes remain unchanged when you switch interface language.

Example record

192.0.2.0/24,DE,DE-BE,Berlin,

Format and discovery references: RFC 8805 · RFC 9632

When providers adopt your feed

Publishing a feed does not change any provider's database by itself. Providers discover your feed through the geofeed reference in your registry objects, evaluate it and apply it on their own schedule. A provider downloading your feed (discovery) is not the same as its public products showing your data (adoption).

How long providers take to discover your feed

ProviderDiscovery time (estimates)
IP2Location3-5 days
MaxMind5-10 days
db-ip~7 days
BigDataCloud~2 days
IPRegistry~2 days
Digital Element~1 week
iplocate1-2 weeks
ipapi.is5-7 days
IPAPI.coManual - contact them
IPBase~1 month
IPGeolocation.io3-5 days

Estimates from this our own experience publishing geofeeds. Discovery means the provider has picked up your feed; their databases and downstream products can take longer to reflect it. These are estimates, not guarantees. IPAPI.co has no automatic discovery - contact them directly to share your geofeed.

Other providers - external measurements

ProviderMeasured reactivity
Fastah~1 day
IPInfo.io~1 day
IPData.co~2 days
apiip~4 days
IPWhois~10 days

Measured by geolocatemuch.com (October 2026): they periodically place a test geofeed in registry records and count the days until each provider reflects it. These are external observations, not this our estimates.

Strict providers may need manual contact

MaxMind and IP2Location are strict about adopting new geofeeds and may require direct contact: MaxMind through GeoIP Exchange or a data-correction request, IP2Location through their support. We have confirmed this with both providers.

Accurate entries protect your whole feed

Geofeed.us accepts any valid ISO 3166-1 country code, but providers judge plausibility. Entries in countries where your network has no presence - for example North Korea or Antarctica - can cause a provider to reject or ignore the entire feed, not just those rows. This has confirmed this behaviour with MaxMind and IP2Location. Feeds spanning many countries are also flagged for operator review on this service.

Locations to avoid unless accurate

These are the seven countries and territories with the fewest IPv4 addresses in IP2Location's Internet IP Address 2026 Report (2025 data, 249 entries ranked by total IPs). Do not put them in your feed unless your network is genuinely located there. Providers may treat entries in places with almost no address space as implausible. Low address count alone is not a rule, and this is not a ban: if your network really is there, list it.

Country / territoryCodeIPv4 addressesRank (of 249)
Heard Island and McDonald IslandsHM5#249
French Southern TerritoriesTF9#248
Saint Helena, Ascension and Tristan da CunhaSH15#247
Christmas IslandCX18#246
Western SaharaEH23#245
South Georgia and the South Sandwich IslandsGS30#244
Cocos (Keeling) IslandsCC94#243

Also near the bottom of the same report: KP #236 (1,540), BV #238 (1,181), AQ #240 (595), WF #230 (3,689).

Source: IP2Location Internet IP Address 2026 Report, ip2location.com/reports/internet-ip-address-2026-report. Rank 249 is the fewest addresses.

Google is a special case

Google is a special case: it does not use public geofeeds by default and instead falls back on the RIR registration country of the announcing ASN. Network operators can submit their geofeed through Google’s ISP portal (isp.google.com). However, you must have your own ASN allocated to you before submitting a geofeed, as Google requires an allocated ASN for the submission process. Submission does not guarantee that the geofeed will be used or indicate when it may take effect.

Even after a provider adopts a feed, its products and downloadable databases refresh on their own cycles, so changes visible to end users can take longer.

What publishing does and does not do

Publishing a geofeed makes your declared locations available. It does not establish prefix ownership, update registry objects automatically, or guarantee adoption by any geolocation provider. Each consumer chooses when and whether to use a feed.

Your dashboard requires sign-in. Published CSV feeds are public, so include only information you intend to share.

Common questions

Does this force providers to update my IP location?

No. The feed is a source providers can discover and evaluate. Refresh schedules and acceptance vary by provider.

Can I publish IPv4 and IPv6 in the same feed?

Yes. A feed can contain both IPv4 and IPv6 prefixes, with one location record per prefix.

Does changing the interface language change my CSV?

No. Language selection changes interface labels, not network records, ISO codes or the public CSV format.