Yeah, even with Comcast/Xfinity I run a HE.net tunnel for IPv6, just so I can have truly static allocations and not goof around with their DHCPv6 prefix request system.
It's been around for a long time! If you do the IPv6 training certification, they do eventually send the t-shirt :P
EDIT: They also provide free DNS for up to 50 domains at dns.he.net which is also worth looking at if you don't want to run your own for every little thing.
I haven’t used it in a few years, but one downside of an HE tunnel was that Netflix blocked traffic from it (since people were using it like a VPN to avoid geoblocks).
I had to run a DNS proxy to filter out AAAA records for any Netflix domains.
HE and Cogent are still feuding over IPv6 peering, too. Using HE for regular web browsing will work fine, but if you want to host through HE your services might not be reachable to visitors from a Cogent network, e.g. office buildings.
The norm seems to be for hosting services to contract with both HE and Cogent if they decide to go with one of them. This is why for typical client browsing you wouldn't notice--the other side has ensured you can reach them. HE seems to be the cheaper option, so people will route most of their traffic through HE, and then separately contract with Cogent for the smaller amount of traffic originating from/to Cogent networks. Alternatively, you contract with another network provider who handles that idiocy for you.
That is true, and a bunch of folks (including me) were experiencing issues with Google-related sites blocking with a 403 FORBIDDEN on the initial /64 static allocation from HE.net. Oddly enough, any subnet out of the optional routed /48 you can enable worked fine.
For sites that use HE.net and have more than one IPv6 subnet, I use the initial /64 for the DMZ, so that didn't matter on most of them. Small sites had just been using the /64 though, and I had to renumber those. Total pain.
The catch? _No IPv6 support whatsoever_