IP Geolocation Corrections
To report a geolocation correction, please complete the form below. The IP ranges should be formatted
according to IP Geofeeds
RFC 8805. For more
information, you can also refer to
the presentation Geofeeds in the
RIPE Database (PDF).
Two examples of a correct geofeed submission are provided below. The first is for US addresses, and the
second is for DE addresses. Note that the US example does not include a postal code.
# prefix,country_code,region_code,city,postal
38.21.40.0/22,US,US-NY,Prattsburgh,
38.21.44.0/23,US,US-NY,Odessa,
38.21.46.0/24,US,US-NY,Prattsburgh,
38.21.47.0/24,US,US-NY,Hornell
# prefix,country_code,region_code,city,postal
185.68.156.0/22,DE,DE-BY,Herzogenaurach,91074
5.182.88.0/22,DE,DE-BY,Herzogenaurach,91074
45.66.28.0/22,DE,DE-BY,Herzogenaurach,91074
45.84.24.0/22,DE,DE-BY,Herzogenaurach,91074
Tip: If possible, please provide a
publicly accessible URL to your
geofeed file in TXT or CSV format. This allows us to keep your geofeed data up-to-date automatically. Good
examples of geofeed URLs:
Threat Feed Submission
Submit a threat feed URL to help us improve our threat intelligence. Please provide a publicly accessible
URL to a threat feed (e.g., a list of malicious IPs, indicators of compromise, etc).
Examples of threat feeds:
General Data Corrections
For general data corrections, please complete the form below.