Last updated
Was this helpful?
Scenarios often encountered in actual use: When users utilize our IPs to access target websites, these sites may block their requests upon detecting IP geolocation mismatches. This often leads users to assume our IPs have incorrect regional assignments, consequently questioning service reliability.
Reasons: The inconsistency between the IP location detected by your target website and the location provided by our platform may stem from several factors. The primary cause remains database divergence—different websites rely on distinct IP geolocation databases (e.g., ipinfo, MaxMind) to determine physical locations. These databases predominantly utilize crowd-sourced network measurements and user-reported data rather than ASN information alone. Variations in vendors’ data sources and update frequencies often lead to conflicting results (e.g., discrepancies between ipinfo.io and ip2location.com).
When a country-level deviation occurs between our provided IP location and the target website’s detection, it is highly likely that the target site’s IP database has not yet updated its records to reflect recent ownership transfers of the IP segment. Our geolocation service leverages BGP-based databases (ipinfo, ping0.cc, iping.cc), which update IP geographic data daily to align with physical infrastructure changes. This approach ensures minimal margin of error. For comprehensive verification, we further cross-reference with commercial databases including MaxMind, IP2Location, and DB-IP.
Resolution: Therefore, when encountering such detection discrepancies, we strongly recommend performing cross-verification first. Should the final cross-verified result match the country originally provided in your ThorData portal, this indicates the target website's IP database contains outdated or inaccurate information. In this case, please present our verification evidence to the target website operator using the feedback template provided at the end of this document, requesting correction of the IP's geographic attribution.
⚠️ Critical Reminder:
DO NOT determine an IP's physical location solely by its ASN (Autonomous System Number). While the org field containing the ASN (e.g., AS12345) identifies the registered owning organization, it does NOT reflect the IP's current physical deployment location.
⚙️ Practical Example:
An enterprise registers its ASN in Germany (administrative headquarters)
Deploys the IP at its Singapore branch infrastructure
Result: → ASN registry location: Germany → Actual IP physical location: Singapore
ipinfo
Mainly based on BGP routing data
Real-time analysis of Internet routing tables (BGP), tracking the actual physical path and autonomous system (AS) of the IP, closer to the location of the network infrastructure (such as the city where the computer room is located).
ping0.cc
Mainly based on BGP routing data
It measures routing latency through global detection nodes and reversely infers the physical location of IP. It is particularly good at identifying the actual landing nodes of multinational CDN/cloud service IPs.
iping.cc
Mainly based on BGP routing data
Maxmind
Commercial Databases/Whois
Integrate commercial procurement data (ISP reports, user feedback), Whois registration information and website domain name associations to build a probability model.
IP2Location
Commercial Databases/Whois
Relying on commercial data aggregation, combined with domain name registration and user submission data, it is good at identifying IP types (corporate/residential/proxy)
DB-IP
Mixed (more commercial)
Integrate public BGP data with commercial sources and use machine learning to fuse signals from multiple sources.
Please follow the above steps, and we hope you can resolve the problem soon!
