I'm getting the same bandwidth (50⇑/10⇓) and latency (10ms) on v4 and v6 with TekSavvy DSL -- but it wasn't always the case. Tunnels hide the actual hops taken... so the latency contributions are hard to gauge with things like traceroute. For the most part, IPv6 is pretty seamless there days. Except for some unexpected holdouts like github.com, a lot of the internet is reachable via IPv6. If you cannot get native IPv6, you can still use Teredo (apt install miredo). Default miredo servers route you through remlab in EU, which will increase latency. Microsoft has some public North American teredo servers you can use, although they keep renaming them. I think " win1710.ipv6.microsoft.com" is the one I used last time I needed it. -Bart On Fri, Aug 3, 2018 at 11:36 AM Michael P. Soulier < msoulier [ at ] digitaltorque [ dot ] ca> wrote: > On 03/08/18 Bart Trojanowski said: > > > There are restrictions. For example it's only available on DSL, not > cable. > > I'm on DSL. > > Mind you when I was running an HE tunnel, I found that we had bandwidth > issues with services like youtube once google left v6 on permanently, > but that was likely an HE bandwidth limitation. > > Mike >