[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GeoIP database issues and the real world consequences

Subject: GeoIP database issues and the real world consequences
From: theodore at ciscodude.net (Theodore Baschak)
Date: Tue, 12 Apr 2016 19:14:15 -0500
In-reply-to: <[email protected]>
References: <1460393711.14814.2.camel@beagle> <[email protected]> <[email protected]> <CAN9qwJ8mFyaV+KLinwFZzXJ=-sGQ-ZmckOwLNt-dPumFLAg0Jg@mail.gmail.com> <[email protected]> <[email protected]>

> 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.

Follow-Ups:
- GeoIP database issues and the real world consequences
  - From: david at cantrell.org.uk (David Cantrell)

References:
- GeoIP database issues and the real world consequences
  - From: cboyd at gizmopartners.com (Chris Boyd)
- GeoIP database issues and the real world consequences
  - From: math at sizone.org (Ken Chase)
- GeoIP database issues and the real world consequences
  - From: hugo at slabnet.com (Hugo Slabbert)
- GeoIP database issues and the real world consequences
  - From: josh at imaginenetworksllc.com (Josh Luthman)
- GeoIP database issues and the real world consequences
  - From: math at sizone.org (Ken Chase)
- GeoIP database issues and the real world consequences
  - From: jfmezei_nanog at vaxination.ca (Jean-Francois Mezei)

Prev by Date: GeoIP database issues and the real world consequences
Next by Date: GeoIP database issues and the real world consequences
Previous by thread: GeoIP database issues and the real world consequences
Next by thread: GeoIP database issues and the real world consequences
Index(es):
- Date
- Thread