Adding Geofeed to RIPE NCC
RIPE NCC provides the most comprehensive geofeed support among all RIRs. You can add geolocation information directly to your inetnum or inet6num objects in the RIPE Database. RIPE supports both a dedicated geofeed: attribute and the standard remarks: method.
Prerequisites
- A RIPE NCC Access account with maintainer (mntner) access to the relevant inetnum/inet6num object
- A geofeed CSV file hosted on a publicly accessible HTTPS URL
- Your IP prefix must be registered in the RIPE Database
If you don't have a geofeed file yet, use our free Geofeed Generator to create one in seconds.
Step 1: Find Your Object in the RIPE Database
- Go to the RIPE Database Query tool: https://apps.db.ripe.net/db-web-ui/query
- Search for the subnet you want to update (e.g.,
203.202.232.0/24) - Click on the matching
inetnumorinet6numobject in the results
Step 2: Log In and Edit the Object
- Click "Update Object" on the object detail page
- Log in with your RIPE NCC Access credentials if prompted
- You will see the object editor with all existing attributes
mnt-by: attribute of the object.
Step 3: Add Geolocation Attributes
In the object editor, you need to add the following attributes. If the attribute keys are not already present, click the "+" button next to any existing input field and select the attribute you want to add from the dropdown.
Add the following attributes to your object:
country: TR
language: TR
geoloc: 41.0291 28.9766
geofeed: https://yourdomain.com/.well-known/geofeed.csv
remarks: Geofeed https://yourdomain.com/.well-known/geofeed.csvAttribute Explanations
| Attribute | Description | Example |
|---|---|---|
country: | ISO 3166-1 two-letter country code where the addresses are used | TR |
language: | ISO 639-1 language code for the country | TR |
geoloc: | Latitude and longitude coordinates (decimal format, space-separated) | 41.0291 28.9766 |
geofeed: | HTTPS URL pointing to your geofeed CSV file (RIPE-specific attribute) | https://yourdomain.com/.well-known/geofeed.csv |
remarks: | Standard RFC 8805 geofeed reference (for compatibility with other databases) | Geofeed https://yourdomain.com/.well-known/geofeed.csv |
geofeed: and remarks: Geofeed ... ensures maximum compatibility. The geofeed: attribute is RIPE-specific and processed directly by RIPE, while the remarks: format is the RFC 8805 standard recognized by third-party geolocation databases like MaxMind and IPinfo.
Step 4: Submit the Changes
- Review all the attributes you've added
- Click "Submit" to save the changes
- RIPE will validate the object and apply the update
Step 5: Verify Your Geofeed
After submitting, you can verify your geofeed setup:
- Query your object again on the RIPE Database to confirm the attributes are saved
- Allow 24-48 hours for geolocation databases to pick up the changes
Example: Complete inetnum Object with Geofeed
inetnum: 203.202.232.0 - 203.202.232.255
netname: EXAMPLE-NET
descr: Example Network
country: TR
language: TR
geoloc: 41.0291 28.9766
admin-c: EXAMPLE-RIPE
tech-c: EXAMPLE-RIPE
status: ASSIGNED PA
geofeed: https://example.com/.well-known/geofeed.csv
remarks: Geofeed https://example.com/.well-known/geofeed.csv
mnt-by: EXAMPLE-MNT
source: RIPEApplying Geofeed to Multiple Subnets
If you have multiple subnets, you need to update each inetnum or inet6num object individually. The geofeed URL can be the same file — it should contain entries for all your prefixes.
For parent objects (e.g., a /16 that contains multiple /24s), the geofeed attribute on the parent applies to all child objects unless overridden by a more specific child object.
Don't Have a Geofeed File?
You can generate your geofeed CSV file for free using our Geofeed Generator tool. Simply enter your IP prefixes, select the correct country, region, and city, and download the ready-to-use CSV file.
