You'll need to ask Google most of these questions as they know the details why they think you (or something else) is doing something wrong according to their reasoning. Tunnels are end-to-end. That will be trickier to abuse (and why would they bother with IPv6 then anyway). It might be that you have a host in your network that is causing requests of course, verify with tcpdump what hosts are doing or better always have netflow/sflow running. If you think your account is compromised, why did you not contact info@sixxs.net about this?

Same issue here. It started occurring around the same time as OP.

I'm experiencing the same since I switched on my SIXXS tunnel again this week. YouTube constantly gives captchas, and the Youtube APIs give HTTP 402 (Payment required). My subnet had no activity in the past 6 months, so I'm guessing some user did something very bad, so large part of SIXXS address space was marked as malicious by YouTube. The iPad app doesn't have the problem. Another workaround can be to use youtube-dl -4 to download a video over IPv4.

Please understand that we hold no power over a multi-billion dollar company. We are just running SixXS for the fun of it, as a little hobby. We are not a massive ISP with hundreds of thousands of customers, thus have no users or legal power to do anything about a third party service. If Google or any other third party service makes a decision to block you they will block, nothing anybody can do about. We have already asked using private favors to resolve this. Unfortunately nothing is happening even though we know that some parts of the company is using: Geofeeds (a Google format) and Prefixes and we register all prefixes in RIPE. There is really nothing more we can do to explain to them where users are and which prefixes they use. Like you we cannot do anything further either. They are the service you have to complain to, as they are blocking you. We have done as good as everything we can do to resolve this, there is nothing else we can do. Changing PoPs will just mean that PoP gets blocked too if their algorithms are made like the way they are and thus would just mean other users not having access. That does not resolve any problem at all as it will block another PoP and keep the old PoP useless as it will remain on the blacklist too.

Hi, Same problem here (for weeks or even months now) with my home network with aiccu sixxs tunnel + radvd daemon for my own ipv6 subnet. To please others in my household I'll now have to disable radvd in order for them to be able to use Youtube. Thanks for documenting it here, a shame Google seems incapable to detect between subnets with abuse, and subnets without abuse. On the other hand, maybe it will motivate me more to switch to an internet provider with native ip6 support. Regards, Johannes

Same problem here. I have a tunnel on the NLHAA01. When I disable ipv6 there's no problem, but with ipv6 enabled all my hosts will get the "I'm not a robot" captcha.

Well, probably unnecessary to confirm since there are many reports, but I've also got the problem on nlhaa01. Why is Google blocking such a large range instead of just individual /64? Unfortunately I had to set a lower precedence for the whole 2a00:1450::/32 subnet to fix this, so no Google services are being accessed over IPv6. I understand this isn't the fault of SixXS, just wondering why this is happening.

Thr NLHAA01 is provided by LeaseWeb, probably one of the biggest malware hosters in (at least) the Netherlands. I can understand why this is being "blocked" by Google/Youtube. LeaseWeb has 2 subnets for subnets: 2001:1af8:fe00::/40 2001:1af8:ff00::/40 Maybe there's a difference between the 2 subnets? Mine comes from the FE00 subnet.

I've reported the issue to LeaseWeb and they are in contact with Google. Let's keep our fingers crossed.

Hi, this problem still exist, very annoying.

I can also confirm this issue. A workaround for me is to reject/drop traffic to 2a00:1450::0/32. Webbrowsers fallback to ipv4. First visits are a bit slower. $IPT6 -A FORWARD -d 2a00:1450::0/32 -j REJECT -m comment --comment "Block IPv6 to Google" $IPT6 -A FORWARD -s 2a00:1450::0/32 -j REJECT -m comment --comment "Block IPv6 from Google" All other traffic keeps going over IPv6. Can anyone confirm that the other NL PoPs do not have this problem? I consider requesting a new pop/tunnel and subnet.