Correction directory

Wrong location? Fix it at the source first.

Location databases copy from each other and from the networks themselves. Fixing the source that feeds them lasts longest; vendor-by-vendor corrections come last.

Short answer

Start with the Truth Check to see which source is wrong. If your ISP publishes no geofeed, ask it to; if it does and a database ignores it, send that database the geofeed’s line for your address.

1. Your ISP’s geofeed (lasts longest)

A geofeed is a CSV file in which a network states where each of its address ranges is used (RFC 8805). Linked from the registry record (RFC 9632), it is read by geolocation vendors, so one correction reaches many of them. Only your ISP can publish or change it. The evidence report drafts the request for you.

Draft the ISP email

2. The service that blocked you

The site may be using an old copy of a database. Send its support a dated link showing what each source says, rather than a screenshot. Support template.

3. Each location vendor

VendorRouteLink last checkedStatus
MaxMind
GeoIP data correction form. MaxMind notes that home addresses are often reallocated, so a correction for one IP may not last.
Correction form 4 Nov 2026HTTP 200
IPinfo
Correction request form for IPinfo data.
Correction form 4 Nov 2026HTTP 200
Google
Report an incorrect IP-based location for Google services.
Correction form 4 Nov 2026HTTP 200
DB-IP
DB-IP has no public correction form; use its contact page.
Contact page 4 Nov 2026HTTP 200

We check every link once a month. MaxMind warns that addresses on home connections are often reassigned, so a correction for one IP may not stick. We have no relationship with any vendor listed.

Sources

  1. RFC 8805: A Format for Self-Published IP Geolocation Feeds
  2. RFC 9632: Finding and Using Geofeed Data