MyIP.dogStart an IP location correction with the actual source
An IP location correction is a request to review the geographic data associated with an address or prefix. Submit it to the organization that supplies the inaccurate estimate, or to the affected website if its source is unknown. There is no single global database that one lookup site can edit for every website, application and network provider.
Before requesting an IP location correction, confirm that the wrong location actually comes from an IP estimate. Account preferences, delivery settings, device location permission and saved application state can also supply a city or country. Describe the incorrect behavior to the affected service and ask which source it uses. A record change cannot fix an unrelated account setting.
Use the location troubleshooting guide if you still need to understand the discrepancy. This page focuses on preparing, submitting and following up an IP location correction. The objective is a justified change to the responsible source, not forcing every map to show your exact physical position.
Match the address before an IP location correction
Record the address observed by the affected service when possible. A separate public-IP check can provide context, but a browser, application or destination may use another family or exit. An IP location correction for an IPv4 value will not necessarily affect a service that is using your IPv6 path.
Keep the date, time, network and intentional VPN or relay state with the observation. If the address changes before review, preserve the original evidence and distinguish it from a new request. Do not replace the reported value with a newer one without explaining the change. IP location correction work depends on identifying the record that produced the original problem.
Prepare evidence for an IP location correction
A useful IP location correction request is specific enough to investigate without collecting unnecessary personal information. Begin with the following fields and follow the official form's requirements:
- The exact public address, or an authorized prefix if you represent its operator.
- The inaccurate country, region or city and the service displaying it.
- The proposed geographic correction at the level you can support.
- The observation time and source of the displayed result.
- Your relationship to the connection or address allocation.
- A concise description of the impact, such as an incorrect regional setting.
An IP location correction does not normally require publishing your household inventory, browser history or account password. Send requested evidence through the provider's official private channel. If a form requests information you do not understand, ask its support team why it is needed before disclosing it. Do not post identity documents in a public issue merely to establish a city-level discrepancy.
Avoid treating one map application as universal ground truth. It may use a different location method from the affected service. Likewise, the registry's country field can describe allocation context instead of subscriber geography. IP WHOIS lookup supplies registry information, but it does not by itself prove the exact location proposed in an IP location correction.
A concise IP location correction request
Adapt this outline using your own observations. The labels describe information to supply; they are not a completed or submitted request:
Affected service: the website or application showing the issue.
Observed address and family: the exact value associated with the result.
Observed at: date, time and timezone.
Displayed location: the country, region or city being disputed.
Requested correction: the supported geographic level and value.
Connection context: provider, network type and relevant VPN or relay use.
Impact and evidence: a short explanation and the evidence the official process requests.
Keep a private copy of the submitted IP location correction and its reference number. If the form cannot accept your situation, contact that provider through its own support route rather than inventing an address range you do not administer. One subscriber's observation is not authority to relocate every address held by the same company.
Official IP location correction routes
First identify the named data supplier. The following routes were checked against their official documentation; they are separate processes, not a combined submission service. If your affected website uses another supplier, ask for that supplier's current process. MyIP.dog does not forward these requests or guarantee that a provider will accept the proposed change.
MaxMind IP location correction
MaxMind's correction guidance links to its data correction request page. Use that official route when the inaccurate result is based on its data. Review the current form and provide the requested scope and evidence. Approval and downstream use remain separate from submission.
IPinfo IP location correction
IPinfo's submission instructions direct users to its corrections page. Its documentation describes support for one-time corrections and geofeeds. Choose the route appropriate to your authority over the address. A household user should not claim to maintain an operator's entire feed merely to complete a form.
Cloudflare IP location correction
Cloudflare provides an official correction route in its IP geolocation documentation. It asks for the relevant address range and applicable corrected fields, and explains that changes depend on confirming the submitted information. This is relevant when the disputed estimate comes from Cloudflare; it is not an instruction to submit every unrelated database discrepancy there.
Keep these IP location correction requests separate if several suppliers disagree. Record which service uses which source when that information is available. Multiple websites repeating one upstream value do not necessarily represent independent measurements, and a change at one supplier does not force another supplier to publish the same conclusion.
IP location correction when the source is unknown
Ask the affected website's support team to identify or investigate the source behind its location-dependent behavior. Include the exact symptom and timestamp. The website may also apply its own account rules or cached decisions. An IP location correction at a suspected supplier is unlikely to be an efficient first step when nobody has established that the website uses it.
IP location correction for network operators
If you administer an address block, investigate whether the issue affects a prefix, a subset of subscribers or a specific service. Allocation transfers, changed deployment and shared exits can require more context than one customer screenshot. Keep the prefix boundaries exact; the CIDR guide explains how a shorter prefix can unintentionally include additional addresses.
Operators can publish coarse geographic mappings using the geofeed format in RFC 8805. RFC 9632 describes finding and using geofeed data, including authority considerations. An IP location correction supported by operator-maintained data still depends on the consumer's ingestion and evaluation. A feed is not an instant worldwide override.
Maintain operational accuracy and appropriate granularity. A broad mobile exit may represent users across an area, and an anycast address can serve multiple locations. IPinfo describes the latter limitation in its anycast explanation. Do not promise a single precise city when the address's actual use does not support one.
Follow up an IP location correction
Treat submission, approval, supplier publication and adoption by the affected service as distinct events. Save any acknowledgement and use the provider's stated review process. Avoid promising a fixed completion time to everyone: evidence review, data releases and downstream refresh schedules differ. An accepted IP location correction may take longer to appear on a particular website.
When rechecking an IP location correction, compare the same address in the same source and record the time. If the public address has changed, label the new observation separately. Otherwise, you could mistake a different allocation for a successful IP location correction. Keep the original screenshot or text privately so you can describe exactly which field changed.
Then verify the practical problem behind the IP location correction. Did the website select the intended region, or does it still apply a saved account preference? If the supplier's result changed but the service did not, give the service both dated observations. An IP location correction can improve a data field without automatically changing every application decision built around it.
If an IP location correction remains unresolved
Ask what evidence is missing and whether the requested granularity is supportable. Provide new, relevant information through the existing case where possible. Repeatedly submitting the same unsupported assertion does not make it stronger. A city-level estimate may legitimately remain broad when shared infrastructure prevents a reliable narrower association.
IP location correction questions
Will restarting the router fix the record? It may leave the address unchanged or assign a different one, but it does not edit the supplier's data. Distinguish a changed connection from an IP location correction to the original record.
Should I change my private address? Changing a local device assignment normally does not change the public exit that the website observes. It can disrupt connectivity without addressing the disputed estimate. Use the public and private guide to identify the relevant value first.
Can this identify my exact home? An IP estimate is not a verified street address or live person-tracking method. Request an IP location correction only at an appropriate supported level, and avoid sharing precise household details simply to make an approximate map pin look exact.
Can MyIP.dog guarantee the correction? No. The responsible supplier evaluates its data, and the affected application controls how it uses that data. The purpose of this IP location correction workflow is to provide a clear, evidence-based request and a reproducible way to check its outcome.