![]() ![]() ![]() |
|
Huskie: Woops - sorry pasted the wrong one - heres with ipv6 off:
Pinging r1.sn-5uaezns7.googlevideo.com [74.125.7.166] with 32 bytes of data:
Reply from 74.125.7.166: bytes=32 time=212ms TTL=52
Reply from 74.125.7.166: bytes=32 time=211ms TTL=52
Reply from 74.125.7.166: bytes=32 time=211ms TTL=52
Reply from 74.125.7.166: bytes=32 time=211ms TTL=52
Ping statistics for 74.125.7.166:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 211ms, Maximum = 212ms, Average = 211ms
Huskie: I haven't changed my dns. It's set to automatically obtain one.
Tested after turning ipv6 off. Not as smooth as some others but a lot better than before.
Still defaults to 360p. If I switch to 720p, I have to pause for a few seconds (otherwise it'll buffer), but it's a lot better than before. Do not as smooth as some others are getting I guess but I'm happy with it.
Huskie: I'll try their DNS servers and see how it goes.
Not sure what you mean by "Just remember that this may stop the internet from working on Non Snap internet connections."
Cheers guys
Huskie: Hmm.. tried turning IPV6 back on, and it goes back to buffering haha. I don't currently have a reason to use IPV6 though so I guess there's no issue with it being turned off.
Flush the DNS cache like I said earlier. Even though snap have fixed the issue at their end. Your computer will be remembering the wrong DNS addresses.
RalphFromSnap: Hi,
Just an update on this, we did see some issues with some IPv6 address's/subnets (Huskies being one of them) not being served from the local nodes - this has been identified and resolved this morning so if you try again now with IPv6 turned on it should be fine.
Thanks,
TheRalph
|
![]() ![]() ![]() |