IP Geofeed Services for IPv4 Geolocation
IP Geofeed Services for IPv4 geolocation provide a standardized way to publish intended location data for deployed IP prefixes. Hyper ICT prepares RFC 8805 geofeeds, provides a stable hosted HTTPS URL and supports related RIPE Database geofeed and geoloc configuration where applicable.
Geofeed Setup
A managed workflow for publishing intended geolocation information for eligible IPv4 resources.
- RFC 8805 geofeed format
- Stable HTTPS hosted URL
- RIPE geofeed attribute support
- geoloc configuration where applicable
- Location updates when deployment changes
What Is an IP Geofeed?
An IP geofeed is a self-published file that associates IP prefixes with intended geographic information in a standardized format. Geolocation providers can use this operator-published data as one input when determining the location associated with an IP range.
What a Geofeed Contains
RFC 8805 defines a CSV-based structure containing an IP prefix followed by optional country, region and city information. Hyper ICT can prepare and host this data for eligible IPv4 resources.
- IPv4 prefix
- ISO country code
- ISO region code where applicable
- City information where applicable
Documentation example only. Actual entries are prepared according to the eligible prefixes and intended deployment locations associated with your service.
RFC 8805 Format and Geofeed Discovery
Publishing location data and making that data discoverable are related but separate parts of a geofeed deployment.
RFC 8805
RFC 8805 defines the format used for self-published IP geolocation feeds, including the prefix, country, region and city fields used in individual feed entries.
Geofeed Discovery
A geofeed URL can be associated with an Internet number resource so consumers can discover the operator-published location feed. In the RIPE Database this can be represented using the geofeed attribute where applicable.
Geofeed Setup for IPv4 Resources
Hyper ICT can handle the technical steps required to publish and maintain intended geolocation information for eligible IPv4 resources.
RFC 8805 Geofeed
We prepare the intended location data for eligible IPv4 prefixes using the standardized geofeed structure defined by RFC 8805.
Hosted Geofeed URL
We provide a stable HTTPS URL for the published geofeed so the feed can be referenced by supported resource records and consumed by external systems.
RIPE Database Configuration
For eligible RIPE-managed resources, we can assist with relevant geofeed and geoloc attributes where the required authorization is available.
From IPv4 Prefix to Published Geofeed
Hyper ICT can manage the process from collecting the intended deployment location to publishing and maintaining the applicable geofeed information.
Send Your Prefixes
Provide the IPv4 prefixes and intended geographic deployment location for each resource.
Prepare the Geofeed
We create the corresponding geolocation entries using the RFC 8805 format.
Publish the Feed
The completed geofeed is published through a stable HTTPS URL that can be referenced for the relevant IPv4 resource.
Configure Resource Data
Where applicable, we assist with the relevant RIPE Database geofeed or geoloc configuration for the supported resource.
Geofeed and geoloc Serve Different Purposes
Both can communicate intended location information, but they do so in different ways. Hyper ICT can assist with either configuration where applicable.
Hosted Prefix Location Feed
The geofeed attribute references a published geofeed containing intended geographic information for IP prefixes.
- References an external feed
- Feed can contain multiple prefixes
- Uses the RFC 8805 format
- Can be updated when deployment changes
Geographic Coordinates
The RIPE Database geoloc attribute stores geographic coordinate information directly on supported ORGANISATION or INET(6)NUM objects.
- Stored directly in a RIPE Database object
- Uses geographic coordinates
- Separate from the hosted geofeed file
- May be used by external geolocation providers
Geofeed Support for Leased IPv4 Resources
Geolocation configuration can be provided alongside IPv4 leasing for eligible Hyper ICT deployments where intended location information needs to be published.
Country-Level Deployment
Publish the intended country associated with an eligible IPv4 prefix using standardized geofeed data.
Region & City
Where appropriate, optional region and city information can also be included in the geofeed.
Future Location Changes
When an eligible prefix is redeployed, its published intended location information can be updated accordingly.
Geofeed Publishes Intended Location - It Does Not Control Geolocation Databases
A geofeed publishes operator-provided location information for IP resources. RIPE NCC is not a geolocation provider, does not verify this geolocation information, and external geolocation providers independently determine whether, when and how they consume or apply published location data.
Services Related to IP Geofeed and Geolocation
Geofeed configuration can be coordinated with IPv4 leasing and related network-resource services when deploying or relocating eligible prefixes.
IPv4 Leasing
Lease IPv4 resources from /24 for hosting, VPN and network infrastructure.
RIPE Maintainer
Assistance with RIPE Database Maintainers and authorized resource-object updates.
Reverse DNS
PTR records, reverse delegation and RIPE domain-object support for eligible IPv4 resources.
Network Services
BGP, ASN, RPKI, LOA and related IPv4 network-resource assistance.
Geofeed & IP Geolocation FAQ
Common questions about geofeed hosting, RFC 8805, RIPE geofeed attributes and IP geolocation.
What is an RFC 8805 geofeed?
An RFC 8805 geofeed is a self-published file that associates IP prefixes with intended geographic information. Each entry contains an IP prefix and may include country, region and city information.
What is the geofeed attribute in the RIPE Database?
The geofeed attribute associates an Internet number resource with a published geofeed URL. For eligible resources, Hyper ICT can assist with this configuration where the required RIPE Database authorization is available.
Do I need to host the geofeed myself?
No. Hyper ICT can prepare the geofeed and provide a stable hosted HTTPS URL for eligible customer resources.
Can Hyper ICT configure the geofeed field in RIPE?
For eligible RIPE-managed resources where the required database authorization is available, Hyper ICT can assist with adding or updating the relevant geofeed attribute.
What is the difference between geofeed and geoloc?
A geofeed attribute references an external feed containing prefix-level location information. In the RIPE Database, geoloc stores geographic coordinate information directly on supported ORGANISATION or INET(6)NUM objects.
Can the IP location be changed later?
Yes. If an eligible IPv4 prefix is redeployed to another location, its geofeed data and applicable RIPE Database geolocation attributes can be updated.
Does a geofeed guarantee every geolocation database will update?
No. A geofeed publishes intended location information, but external geolocation providers independently decide whether, when and how they consume and apply that data.
Does RIPE NCC verify geofeed or geoloc information?
RIPE NCC is not a geolocation provider and does not verify the geolocation information added by resource holders to the RIPE Database.
Is geofeed available with Hyper ICT IPv4 leasing?
Yes, for eligible Hyper ICT IPv4 leasing deployments. Geofeed hosting and applicable geolocation configuration can be coordinated with the IPv4 resource and intended deployment location.
Need a Geofeed for Your IPv4 Resources?
Tell us which IPv4 prefixes you use and their intended deployment locations. We can prepare the RFC 8805 geofeed, provide the hosted URL and assist with applicable RIPE Database geolocation configuration.