IP Data Correction

Important:

Corrections may take up to 4 days to be reflected in the API.
If submitting a geofeed URL, ensure it is publicly accessible and contains accurate data.
We do not manually verify the data submitted via this form. We only process data in the correct format. Please do not put your correction data in the free text form field.

Ensuring data accuracy is our top priority. We dedicate significant resources to maintaining high data quality and update our dataset daily. However, errors and inaccuracies may still occur. For that reason, we have created this form to allow you to submit corrections to our data.

You can also submit corrections automatically via the Corrections API.

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:

Your Email Address*

We will use this email to contact you if we need more information.

Geofeed Submission *

Geofeed URL (Preferred)

Enter the URL of your geofeed file (CSV or TXT format) that follows RFC 8805 format.
Example: https://geo.dynamikcloud.com/geofeed.txt

Geofeed Data (Paste RFC 8805)

Each line: IP prefix/subnet, country code, region code, city, postal code.
Example: 104.132.107.0/24,US,US-NJ,Princeton,08540

Verification Source

Describe your authority to verify this data. For example: "We are the ISP that owns and operates these IP ranges and can confirm their physical locations" or "We are the datacenter operator where these IPs are hosted".

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.

Your Email Address*

We will use this email to contact you if we need more information.

API Data Point*

Select the specific data point of the API that needs correction.

Correction Details*

Provide details about the correction. For example: "The IP Address 1.2.3.4 belongs to the VPN Provider NordVPN".