[188708] in North American Network Operators' Group
Re: GeoIP database issues and the real world consequences
daemon@ATHENA.MIT.EDU (David Cantrell)
Wed Apr 13 07:04:52 2016
X-Original-To: nanog@nanog.org
Date: Wed, 13 Apr 2016 11:35:57 +0100
From: David Cantrell <david@cantrell.org.uk>
To: Theodore Baschak <theodore@ciscodude.net>
In-Reply-To: <F2EE953C-BEDB-42CC-BFC1-4541627F4B02@ciscodude.net>
Cc: NANOG Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
On Tue, Apr 12, 2016 at 07:14:15PM -0500, Theodore Baschak wrote:
> > On Apr 12, 2016, at 7:10 PM, Jean-Francois Mezei wrote:
> > On 2016-04-11 13:22, Ken Chase wrote:
> >> Well they DO know the IP location is within the USA -
> > A friend in Australia was with an ISP onwed by a US firm and his IP
> > address often geolocated to the USA.
> Similarly, IPv6 space thats been originated by a Canadian org, in Canada for 4 or 5 years is still shown as in the USA.
There are similar problems with phone numbers. Google's libphonenumber,
for example, will tell you that +1 855 266 7269 is in the US. It's not,
it's Canadian. It appears that for any NANP "area code" that isn't
assigned to a particular place libphonenumber just says "it's in the US"
instead of "it's in one of the NANP countries".
They appear to have a similar bug with Russia/Kazakhstan.
--
David Cantrell
