[wbond]

IPv6 became available to me on my Comcast connection in the past six months, but I ended up disabling it at my local router. Unfortunately it seems in my area (North of Boston, MA) the IPv6 routing on Comcast's network is extremely spotty. Sometimes connections would time out on all different ports (22, 80, 443). This lead to a rather poor experience for members of my household. I ran into lots of issues with SSH. My wife ran into lots of issues using apps on her iPhone. She was switching to her mobile data connection on a regular basis to work around the issue. Since disabling IPv6 on our network, all of the issues have gone away.

[danyork]

Did you contact Comcast about this issue? I know some of the folks involved with the IPv6 rollout there and they are VERY focused on making the IPv6 experience as painless as possible.

[wbond]

No, after spending 3 weeks and 6 hours on the phone to add the correct TV to my account I gave up spending time with Comcast.

If you happen to know a competent contact that I can provide info to, I'd be happy. But I am not going to waste my time trying to get through to them via normal channels.

[jbrzozowski]

@wbond I run the program at Comcast, want to ping me offline?

[tsmarsh]

I found that switching to googles DNS fixed those issues for me (I'm on the south shore).

There is still the occasional delay, but its similar to the ipv4 service from Comcast.

[mitchty]

I had to switch dns for ipv4 regardless.

But ipv6 actually seems to be around 50% of my traffic now. Native dual stack is way better than the tunnel nonsense they were trialing a few years back. I've had zero issues with ipv6 and comcast now that they went to proper dual stack.