GEO IP Updates

Mailman List Mirror (Read Only)
1

Hi,

We’ve leased some new IP blocks, but are having issues with customers complaining they can’t access some Geo Restricted content.

We updated all the GEO IP databases we can think of… but are still having issues…

2 services people have complained about are…

Crave TV
Amazon Prime

We are located in Canada as are all our clients, and they are getting notices that they are located in the US.

We updated… Maxmind, DB-IP, IP Info, IP Geolocation, IPHub. IP2location

2

Did you update the info in the Whois at the RIR ? Sometimes they pull from this in my experience.

3

No, we don't own the IPs, we lease them. We have no access to the whois
data, and have other blocks that we've had no issues with, so certainly not
that. Also using whois would be odd, as people often have large blocks,
and don't subdivide them in whois to say where each block is located.

4

$DAY_JOB previously had a case. Were it was necessary to contact Akamai. Because they have their own database.

5

Google also has a portal where you can provide a link to a self-published csv geofeed, which is used for some but not all products served from their CDN infrastructure.

https://isp.google.com/geo_feed/

They’re also working on getting the format standardised in the IETF. I applaud this, because less badly guessed geoip data and more reliably self-published data is better:

https://datatracker.ietf.org/doc/html/draft-google-self-published-geofeeds

6

Hey folk,

Martijn Schmidt said…

They’re also working on getting the format standardised in the IETF. I

applaud this, because less badly guessed geoip data and more reliably

self-published data is better:

https://datatracker.ietf.org/doc/html/draft-google-self-published-geofeeds

Just a quick note that this document is being advanced for publication as an Independent Stream [1] RFC. That means it is not getting IETF review or consensus and will not be an IETF RFC or any kind of standard.

It is important to recognise that not all RFCs are IETF RFCs. Publication on the Independent Stream is a way to produce RFCs that describe proprietary protocols, provide commentary on IETF work, or offer contrary opinions. While the Independent Stream RFCs are held to the same editorial standards as other RFCs, their technical content is not subject to the same level of scrutiny.

Reviews of drafts on the Independent Stream are always welcome. You can send comments and thoughts direct to the authors or to me as Independent Submissions Editor via rfc-ise@rfc-editor.org.

Thanks,

Adrian