Google has some interesting stats on IPv6 usage: <a href="http://www.google.com/intl/en/ipv6/statistics.html" rel="nofollow">http://www.google.com/intl/en/ipv6/statistics.html</a><p>Currently ~2.53% of traffic going through Google is over IPv6. Adoption Rates:<p><pre><code> Belgium: 4.1%
Peru: 4.26%
USA: 4.88%
France: 4.91%
Germany: 5.24%
Romania: 7.63%
Switzerland: 9.47%</code></pre>
Comcast had been somewhat unstable for me since they rolled out IPV6 in my area. Before that 4 years of being rock solid.<p>On the bright side - dual stack indeed works, even though neither IPV4 nor IPV6 can keep ping going without dropping any packets for more then few minutes.
It's too bad that other providers are not offering this yet. For example, my provider says:<p>> At this time Optimum is not providing IPV6 addresses. In the future we will support users wishing to connect to IPv6-only sites. Currently, web site operators today are compatible with both IPv4 and IPv6 to ensure their sites are reachable by everyone. When IPv6 becomes the standard, which currently it is not, we will provide support for it.<p>If you don't have native IPv6 yet, ask your ISP why!
Anyone who's rolled out IPv6 on a large internal network or public facing site, why did you bother? Right now it seems like more work and complexity for exactly zero benefit.
Once I noticed that Comcast was IPv6 enabled in my area switching it on was as easy as checking a couple of boxes in my airport express. One was to enable IPv6 and the other was to block incoming IPv6 connections.<p>I have not noticed any issues since enabling it. Dual stack seems to work well. As browsers seem to choose whichever is faster I have seen some behaviour where Google thought I was accessing gmail from multiple locations at the same time when infact I had switched from IPv4 to IPv6.
Still waiting for Hacker News:<p><pre><code> $ ping6 news.ycombinator.com
unknown host
</code></pre>
Funny thing is, this site runs behind Cloudflare, where IPv6 is available by checking one box. Although that will cause IPv6 addresses to appear in the CF-Connecting-IP header, so perhaps the devs can't figure out how to manipulate them, or they just don't care.
Meanwhile, Charter cable's IPv6 page hasn't been updated in over a year, including hints at business test deployments in Q42012. I'm sure there is someone behind the scenes working on it, but nobody I have asked (I'm a fiber business customer) seems to know who to talk to, or when its getting rolled out.
According to the page Comcast linked to: <a href="http://www.worldipv6launch.org/measurements/" rel="nofollow">http://www.worldipv6launch.org/measurements/</a><p>in terms of percentage deployment, Google Fiber is at #4 with 67.05% .