Submit a Data Correction

Found an inaccuracy? Help us fix it. Data accuracy is our top priority — we update our datasets daily, but errors can still slip through. Pick the correction type below and send it our way.

Updated daily
We refresh our IP intelligence datasets every single day.
Live within ~4 days
Approved corrections propagate to the API within four days.
Automate it
Prefer code? Use the Corrections API.

Before you submit

  • We process submissions in the correct format automatically and do not manually verify them — so please keep your data in the proper fields, not in the free-text box.
  • If you submit a geofeed URL, make sure it is publicly accessible and accurate.

IP Geolocation Corrections

Report the correct location for an IP range. Ranges must follow the IP Geofeeds RFC 8805 format. See the RIPE geofeed presentation (PDF) for background.

We'll only use this to contact you if we need more information.

Choose one method — a public URL (best) or paste the data directly.

Geofeed URL Recommended

A CSV or TXT file following RFC 8805. Lets us keep your data up to date automatically.

OR
Paste geofeed data

Format: prefix,country_code,region_code,city,postal

Optional, but it speeds up review. Tell us how you can vouch for this data.

Example geofeeds

United States postal code omitted 
# 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
Germany postal code included 
# 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

Good public geofeed URLs to model yours on: geo.terraservers.net/geofeed.csv and geo.dynamikcloud.com/geofeed.txt.