Talk:Internet geolocation
| This article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||
| |||||||||||||||||
Hi there! So, as you know I'm trying to improve this page, which is honestly in a not-so-good condition right now (see below to understand why). Last update: Yesterday, after talking with SuperPianoMan, I re-added the content, and it was again rolled-back by Pbritti, with this note "I don't know, that addition looks an awful lot like it was written by an LLM. If you want to add it, discuss on the talk page". So, here we are.
I would like to clarify a few things: The content is not LLM generated. Does it look like that? I don't know, but anyway, it's not. Anyway, let's assume it's LLM generated, for the following clarification (again, it is not, but it's easier if we assume it is). If we take a look at the policies Wikipedia:Large language models#Risks and relevant policies we all agree that LLM is not a reliable source of information (I tried for some of my customers to write blog articles/web pages with AI nad I know very well how things may be completely wrong or invented, with sources that do not lead anywhere). Well, back to the policy, we see in particular these sections:
Unsourced or unverifiable content: If you take a look at all the claims that I made inside my revision of the page, you can see that there are more than 80 verified (manually found and verified by me, not AI) sources.
Algorithmic bias and non-neutral point of view: The page keeps an unbiased and neutral point of view. I tried to be as neutral as I could, explained both how the different technologies work and the privacy concerns, along with examples of mistakes (that were already present, I added some sources)
Copyright violations: Well, I manually wrote everything and put every single source, there is nothing that has been just "copied and pasted" at all, and this is quite easy to check.
Then, we have a note that says "An editor who identifies LLM-originated content that does not comply with our core content policies—and decides not to remove it outright (which is generally fine to do)—should either edit it to make it comply or alert other editors of the issue. The first thing to check is that the referenced works actually exist. All factual claims then need to be verified against the provided sources. Presence of text‑source integrity must be established. Anything that turns out not to comply with the policies should then be removed."
Does this page comply with the Wikipedia:Core content policies (Neutral point of view, Verifiability, No original research). Let's go through them together. Does this page has a neutral point of view? Honestly, I would say so. I tried to put all the technical details, explanation, complete history including when people didn't believe that IP geolocation was even possible. Is everything verifiable? Well, with more than 80 sources, I think so. Is this an original research? Not at all. Internet geolocation, which is a term that comprehends multiple techniques for geolocation, is real, common, widely used everyday.
So, even assuming that the content was LLM-generated, in this case, it does not go against any policy, and it complies with the core content policy, too. As said, then, let's also consider that, in the end, it is not even LLM-generated.
Let me please move forward, then, and analyze another aspect.
The current status of the page is pretty bad, and I would like to explain why. Right now the page is called "Internet geolocation" but in reality it's exploring only the IP geolocation aspect. No mention at all to any other technology or system that can be used in this field (except "Other methods include examination of Wi-Fi hotspots." at the top, without explanations at all).
In addition, there are some statements that are not supported by any source (for example "Some commercial databases have augmented geolocation software with demographic data to enable demographic-type targeting using IP address data."), some of which I improved in my version, and others that are not really precise or clear ("An alternative to hosting and querying a database is to obtain the country code for a given IP address through a DNSBL-style lookup from a remote server." How? Would you get the same output? - hint: no).
There is nothing about the history and background behind this technology, there are no explanations about the use of VPN to mask IP addresses (except "Technical measures for ensuring anonymity, such as proxy servers, can be used to circumvent restrictions imposed by geolocation software"). And really, the use of VPN is what is making IP geolocation unrealiable nowadays and is complicating also criminal investigation. And for this, it would make sense to add some notes to other internet geolocation technologies that can go beyond classic IP geolocation, and use advanced ways to localize devices (even methods to detect the IP of a device connected to a VPN, which is something that I think I mentioned inside the Privacy section). At this regard, inside the privacy section, there is nothing about concerns for other "internet geolocation" technologies (WiFi Tracking, the use of WiFi propagation model and AI to detect humans, background mobile tracking, law enforcement tracking through trojans...). There is instead an interesting list of applications/use cases, that indeed I kept in my version (and expanded just a bit), since it's pretty well done for what concerns the use of IP geolocation in the real world, and there is a good explanation of the sources of data for IP geolocation.
So, considering all the above, please let me know if you still have doubts about the genuinity of my edits. I mean, I can also re-write the entire page again from scratch, but I doubt that the final result will be much different from what I published the last time (yesterday). However, if you think it's worth my time, I can do it. Or, if for any reason you prefer to keep the page in the current status, I'll drop my suggestions and edits.
I wish you a great day! --Dylan--86 (talk) 11:56, 21 August 2025 (UTC)
Already in 1994 there were early ideas of using IP addresses,
dates back to the end of the 90's,
there was a strong skepticism about the actual possible application of this technology,
opened the way to the large adoption, none of this is stuff LLMs output naturally. Multiple AI detectors also coming back negative on it.
I'm cringing at the latest rewrite. Besides sourcing problems still, the content presentation seems off for an encyclopedia article, and the selection of detail questionable. One thing that would be of great help is to work in small edits. I'll look closer when I find the time. --Hipal (talk) 18:15, 19 September 2025 (UTC)
| This edit request by an editor with a conflict of interest was declined. |
I am a founder of Octet (disclosed on my user page) and have a financial COI here, so I'm requesting rather than editing directly. The "Accuracy and limitations" section was flagged empty in October 2025. Every claim below leads with a primary source (MaxMind, CAIDA, RFC 8805, IEEE BalkanCom, arXiv); the Octet Research citation is a synthesis of those and can be dropped if preferred. Proposed wikitext:
== Accuracy and limitations ==
The accuracy of IP-based geolocation varies widely by connection type and is generally higher at the country level than at the city level. [[MaxMind]] reports city-level accuracy within {{convert|50|km|mi}} of about 66% in the United States, its best-covered market.<ref name="maxmind-acc">{{cite web |title=GeoIP2 City accuracy |publisher=MaxMind |url=https://www.maxmind.com/en/geoip-accuracy-comparison |access-date=2026-07-22}}</ref> Databases also disagree with one another: an analysis of 6.3 million addresses found an average inter-database disagreement of about {{convert|620|km|mi}}, a distance greater than many land borders.<ref name="nur2023">{{cite conference |last1=Nur |first1=A. |display-authors=etal |title=Accuracy and Coverage Analysis of IP Geolocation Databases |conference=IEEE BalkanCom |year=2023 |url=https://www.researchgate.net/publication/372091523_Accuracy_and_Coverage_Analysis_of_IP_Geolocation_Databases}}</ref><ref name="octet-ip">{{cite web |title=IP Address Cannot Prove Where Someone Is |url=https://ip.octetproof.com/ |website=Octet Research |access-date=2026-07-22}}</ref>
Several features of modern networks weaken the link between an IP address and a physical location. [[Carrier-grade NAT]] places many mobile subscribers behind a single public address, so a lookup resolves to the carrier gateway rather than the device.<ref name="caida2018">{{cite web |title=Inferring Carrier-Grade NAT deployment |publisher=CAIDA |year=2018 |url=https://www.caida.org/catalog/papers/2018_inferring_carrier_grade_nat/inferring_carrier_grade_nat.pdf}}</ref><ref name="cf2025">{{cite web |title=One IP address, many users: detecting CGN to reduce collateral damage |website=Cloudflare |date=October 2025 |url=https://blog.cloudflare.com/detecting-cgn-to-reduce-collateral-damage/}}</ref> Because registry and geofeed data are self-declared, {{IETF RFC|8805}} advises consumers to treat geofeeds only as a hint; a 2025 analysis found about 8% of geofeed entries listed an incorrect country and 20.4% an incorrect city.<ref name="ipinfo2025">{{cite web |title=IP geolocation and geofeeds: why verification matters |website=IPinfo |year=2025 |url=https://community.ipinfo.io/t/ip-geolocation-and-geofeeds-why-verification-matters/7216}}</ref> Low-Earth-orbit satellite networks add further error: a 2024 study of the [[Starlink]] network found its global traffic routed through 49 points of presence serving 165 countries, so subscribers in countries without a local point of presence receive addresses that resolve abroad.<ref name="starlink2024">{{cite arXiv |last1=Wang |first1=Bingsen |display-authors=etal |eprint=2412.18243 |title=A Large-Scale IPv6-Based Measurement of the Starlink Network |class=cs.NI |year=2024}}</ref><ref name="octet-ip" />
Thank you for reviewing. Spherish (talk) 13:24, 22 July 2026 (UTC)
Regards, Spintendo 17:02, 5 August 2026 (UTC)
| The user below has a request that an edit be made to Internet geolocation. That user has an actual or apparent conflict of interest. The requested edits backlog is very high. Please be extremely patient. There are currently 619 requests waiting for review. Please read the instructions for the parameters used by this template for accepting and declining them, and review the request below and make the edit if it is well sourced, neutral, and follows other Wikipedia guidelines and policies. |
I have a declared conflict of interest (founder of Octet, disclosed on my user page), so I am requesting rather than editing. Restating in the required "change X to Y" form; apologies for the earlier malformed request.
In the Data sources → Errors subsection, please change:
X (the final sentence of the subsection):
The company had used the National Geospatial-Intelligence Agency's coordinates for Pretoria, which pointed to the family's house, to represent IP addresses associated with Pretoria.
Y (that sentence, unchanged, followed by two new paragraphs):
The company had used the National Geospatial-Intelligence Agency's coordinates for Pretoria, which pointed to the family's house, to represent IP addresses associated with Pretoria.
Beyond centroid mapping, geolocation databases disagree with one another: an analysis of 6.3 million addresses found an average inter-database disagreement of about {{convert|620|km|mi}}, a distance greater than many national land borders.<ref name="nur2023">{{cite conference |last1=Nur |first1=A. |display-authors=etal |title=Accuracy and Coverage Analysis of IP Geolocation Databases |conference=IEEE BalkanCom |year=2023 |url=https://www.researchgate.net/publication/372091523_Accuracy_and_Coverage_Analysis_of_IP_Geolocation_Databases}}</ref> [[MaxMind]] reports city-level accuracy within {{convert|50|km|mi}} of about 66% in the United States, its best-covered market.<ref name="maxmind-acc">{{cite web |title=GeoIP2 City accuracy |publisher=MaxMind |url=https://www.maxmind.com/en/geoip-accuracy-comparison |access-date=2026-08-05}}</ref>
Several features of modern networks contribute to this error. [[Carrier-grade NAT]] places many mobile subscribers behind a single public address, so a lookup resolves to the carrier gateway rather than the subscriber.<ref name="caida2018">{{cite web |title=Inferring Carrier-Grade NAT deployment |publisher=CAIDA |year=2018 |url=https://www.caida.org/catalog/papers/2018_inferring_carrier_grade_nat/inferring_carrier_grade_nat.pdf}}</ref> Because registry and geofeed data are self-declared, {{IETF RFC|8805}} advises consumers to treat geofeeds as a hint only; a 2025 analysis reported about 8% of geofeed entries listing an incorrect country and 20.4% an incorrect city.<ref name="ipinfo2025">{{cite web |title=IP geolocation and geofeeds: why verification matters |website=IPinfo |year=2025 |url=https://community.ipinfo.io/t/ip-geolocation-and-geofeeds-why-verification-matters/7216}}</ref> Low-Earth-orbit satellite networks introduce a further source of error: a 2024 measurement study of the [[Starlink]] network mapped its traffic through 49 points of presence serving 165 countries, so subscribers in countries without a local point of presence receive addresses that resolve abroad.<ref name="starlink2024">{{cite arXiv |last1=Wang |first1=Bingsen |display-authors=etal |eprint=2412.18243 |title=A Large-Scale IPv6-Based Measurement of the Starlink Network |class=cs.NI |year=2024}}</ref>
Note: the subsection currently carries no citations, so this also adds sourcing to it. Each sentence leads with a primary reference (IEEE BalkanCom, MaxMind, CAIDA, RFC 8805, arXiv). I have deliberately left out a citation to my own company's research summary; the primary sources carry every claim on their own. Spherish (talk) 18:18, 5 August 2026 (UTC)
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.