[bdb]

Actually, you'd be surprised -- Comcast is leading the charge on the residential IPv6 front in the US, and Time Warner Cable isn't too far behind. Verizon, the largest carrier in the US not owned by a content company (by my back-of-napkin math), has been slower in deployment of IPv6, by contrast. (OTOH, since IPv6 is critical to LTE deployment, VZW et al have been much quicker on the uptake.)

I actually think that the content hosting folks are behind the curve here. Amazon is one of the biggest hold-outs; their IPv6 rollout has thus far been a total joke. No IPv6 for Cloudfront? No IPv6 glue for Route53 authoritative nameservers? No IPv6 on VPC, barely on EC2 at all, etc., etc. From what I've heard, the management at Amazon doesn't really care about the network behind their infrastructure; instead of investing in building a backbone that could do a better job supporting this kind of stuff -- and all kinds of inter-region applications which would be useful -- they want pretend the network doesn't exist and that nothing needs to change. It's too bad. I think we'd see more IPv6 usage if Amazon would get their act together.

[js2]

I have TWC residential service. Coincidentally, I just experimented with setting up IPv6 yesterday on my Airport Extreme. TWC is not issuing IPv6 addresses at my location. So I went with an automatic tunnel (192.88.99.1). That IP is 16 hops and 150 ms away for me (anycast by Congent in my case) and its performance was awful.

I switched to a manual tunnel from HE (tunnelbroker.net). I confirmed this worked, that my Apple devices behind the Airport Express all got IPv6 addresses and so forth, and that the performance was decent.

Experience in hand, I then tore it all down, since I couldn't think of a good reason why I really needed IPv6 at home. :-)

[wmf]

And now real IPv6 never gets debugged because everyone is using HE.net tunnels.