Hi,
Would anyone from Google care to explain to me off-list why certain
Youtube-content is blocked in the Netherlands while using IPv6 when it
is working fine via IPv4?
Geolocation imperfections perhaps?
The IPv6-address is within 2a02:a47f:e000::/36
(actually, it is: 2a02:a444:443b:0:xxxx:xxxx:xxxx:xxxx)
Thank you.
geolocation is hard 
geolocation is a broken concept anyway
Similar to like being allowed by law to only offer some downloads of
series/movies during the night (starting 10pm afaik) for
youth-protection (here in Germany) ... come on ...
Kind regards,
sn
Marco Davids schreef op 25-6-2015 om 14:33:
Hi,
Would anyone from Google care to explain to me off-list why certain
Youtube-content is blocked in the Netherlands while using IPv6 when it
is working fine via IPv4?Geolocation imperfections perhaps?
The IPv6-address is within 2a02:a47f:e000::/36
(actually, it is: 2a02:a444:443b:0:xxxx:xxxx:xxxx:xxxx)
To add to Marco,
The entire 2a02:a400::/25 prefix is used by KPN Netherlands for consumer
and small business DSL internet.
http://bgp.he.net/ip/2A02:A400:C17F:0::
Kind regards,
Seth
If you would like to see how Google has your geolocation set, check:
curl http://redirector.c.youtube.com/report_mapping
You might want to force it both IPv4 and IPv6 to see if there is any difference.
Best Regards,
-Phil
Hi,
+1.
Our 2a01:d0::/32 is floating by Google's geo all around the world, it
was Iran, now it is Russia... and I can't do anything with it, and have
no human contact in Google for complaint.
And run it a few times, because it may think your IP in asia is in Amsterdam, etc..
[jared@eng0 ~]$ curl -4 http://redirector.c.youtube.com/report_mapping
203.105.73.114 => ams09x03 : superx_isp_number: 8 (203.105.64.0/20) [s]
[jared@eng0 ~]$ curl -4 http://redirector.c.youtube.com/report_mapping
203.105.73.114 => sjc07x04 : superx_isp_number: 1 (203.105.64.0/20) [u]
- Jared
Hi,
+1.
Our 2a01:d0::/32 is floating by Google's geo all around the world, it
was Iran, now it is Russia... and I can't do anything with it, and have
no human contact in Google for complaint.
That sounds like a software problem where it does not match anything in the database and then proceeds to return the last known value of the variable. 
That’s even worse then saying “We don’t know”.
Regards,
Seth
geolocation is hard
If you would like to see how Google has your geolocation set, check:
curl http://redirector.c.youtube.com/report_mappingYou might want to force it both IPv4 and IPv6 to see if there is any difference.
And run it a few times, because it may think your IP in asia is in Amsterdam, etc..
[jared@eng0 ~]$ curl -4 http://redirector.c.youtube.com/report_mapping
203.105.73.114 => ams09x03 : superx_isp_number: 8 (203.105.64.0/20) [s]
[jared@eng0 ~]$ curl -4 http://redirector.c.youtube.com/report_mapping
203.105.73.114 => sjc07x04 : superx_isp_number: 1 (203.105.64.0/20) [u]
Maybe its actually telling you where youtube is serving videos from for that IP address, in realtime, based on a large number of variables only one of which is where on the Earth that IP might be located.
That might be possible, but sending traffic to Europe vs another site smells
like some other issue.
It’s also interesting to look at the internalized CIDR it’s matching against.
Take puck as an example.
puck:~$ curl http://redirector.c.youtube.com/report_mapping -4
204.42.254.5 => ord31x04 : superx_isp_number: 1 (204.42.224.0/19) [u]
puck:~$ curl http://redirector.c.youtube.com/report_mapping -6
2001:418:3f4::5 => sjc07s17 (2001:418:200::/39) [u]
Many interesting results as a consequence.
- jared
https://github.com/morrowc/yt_troubleshooting
might even be useful... I have not run it in a bit so it might die horribly
but it might also tell you something useful 
