Youtube / IPv6 / Netherlands

Thu Jun 25 15:37:16 UTC 2015

> On Jun 25, 2015, at 11:33 AM, Scott Whyte <swhyte at gmail.com> wrote:
> 
> 
> 
> On 6/25/15 07:49, Jared Mauch wrote:
>> 
>>> On Jun 25, 2015, at 10:08 AM, Phil Rosenthal <pr at isprime.com> wrote:
>>> 
>>> 
>>>> On Jun 25, 2015, at 9:32 AM, Christopher Morrow <morrowc.lists at gmail.com> wrote:
>>>> 
>>>> geolocation is hard :(
>>> 
>>> 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.
>> 
>> 
>> And run it a few times, because it may think your IP in asia is in Amsterdam, etc..
>> 
>> [jared at 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 at 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