Youtube / IPv6 / Netherlands

Seth Mos seth.mos at dds.nl
Thu Jun 25 15:26:38 UTC 2015


> Op 25 jun. 2015, om 16:44 heeft Max Tulyev <maxtul at netassist.ua> het volgende geschreven:
> 
> 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
> 
> On 25.06.15 15:33, Marco Davids wrote:
>> 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.
>> 
>> 
> 




More information about the NANOG mailing list