Data Corrections

Tell us where a network really is, or which other value we have wrong. A location takes effect with the next database build, usually within a week. Anything else is read by a person first.

An address corrects only itself. Give the network, like 203.0.113.0/24, to correct all of it.

The region or the postal code tells places of the same name apart. A city we cannot find corrects the country alone.

Only used to reach you about this correction. A location sent without an account counts as evidence beside our other sources: log in to have it applied as submitted.

What happens to a correction

A location sent while signed in, or through the API with your key, is applied as submitted with the next database build, whatever our other sources say. It holds for a year and counts as evidence after that.

A location sent without an account counts as evidence. It outweighs any two geolocation databases, but not three that agree with each other, and not a geofeed that the WHOIS record of the network references.

A geofeed URL is fetched with every build from then on. Sent while signed in, it outweighs any two geolocation databases as well. Sent without an account, it counts for less than one database and fills in where the others say nothing.

Other data is read by a person. We change what is wrong, and write to you if we need to know more.

One correction counts per network: a newer one replaces an older one, except that one sent without an account never replaces one from an account. We remove a correction that turns out to be wrong.

The geofeed format

A geofeed, as RFC 8805 defines it, has one network per line: prefix,country,region,city,postal.

203.0.113.0/24,DE,DE-BE,Berlin,10115
198.51.100.64/26,US,US-MO,Springfield,
2001:db8:42::/48,FR,,Paris,
192.0.2.7,JP
  • The prefix is a network or a single address in public address space, no larger than a /9 for IPv4 and a /17 for IPv6. The networks of this example are reserved for documentation and are refused.
  • The country is a two-letter ISO 3166-1 code, and the only field a line needs besides the prefix. The region is an ISO 3166-2 code or the name of the region.
  • A correction holds up to 100 lines, or 1,000 when you are signed in. Lines that start with # are ignored. For more networks, send the URL.

If you operate the network

Publish the geofeed and point to it from your WHOIS records, as RFC 9632 describes: with the geofeed: attribute of the inetnum or inet6num object, or with a remarks: Geofeed https://… line where your registry has no such attribute. We read the registries with every build and find the feed without this form, and so do the other providers that read geofeeds. It is the source we trust most for your networks.

Moving addresses you have just bought? Brander Group's guide How to Update IPv4 Address Geolocation lists where to send the same correction to the other geolocation providers.

From a script

Everything this form sends can be sent with your API key. The corrections API has the request formats.