25 Jun
2015
25 Jun
'15
10:44 a.m.
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. 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.