Can you guys that have received the email please do some traceroutes to cache.l.google.com and youtube.com as well as geekzone.co.nz and post them here?
Tracing route to cache.l.google.com [202.124.127.21] over a maximum of 30 hops:
1 2 19 ms 19 ms 19 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 19 ms 18 ms 18 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 67 ms 34 ms 33 ms 46.17.69.111.static.snap.net.nz [111.69.17.46] 5 34 ms 34 ms 34 ms 47.17.69.111.static.snap.net.nz [111.69.17.47] 6 33 ms 33 ms 34 ms 21.127.124.202.static.snap.net.nz [202.124.127.21]
Trace complete.
Tracing route to youtube.com [74.125.237.110] over a maximum of 30 hops:
1 2 30 ms 40 ms 41 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 18 ms 18 ms 18 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 18 ms 20 ms 19 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 19 ms 19 ms 19 ms 203.167.233.9 6 19 ms 19 ms 19 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125] 7 44 ms 43 ms 43 ms i-0-0-4-1.sydo-core02.bx.reach.com [202.84.142.149] 8 52 ms 47 ms 47 ms TenGigE0-1-0-13.oxf-gw1.Sydney.telstra.net [203.50.13.121] 9 50 ms 47 ms 47 ms Bundle-Ether1.ken-core4.Sydney.telstra.net [203.50.6.5] 10 49 ms 47 ms 47 ms Bundle-Ether1.ken39.Sydney.telstra.net [203.50.6.146] 11 45 ms 44 ms 44 ms 72.14.198.54 12 45 ms 45 ms 44 ms 66.249.95.224 13 45 ms 45 ms 45 ms 72.14.237.135 14 44 ms 44 ms 44 ms syd01s12-in-f14.1e100.net [74.125.237.110]
Trace complete.
Tracing route to geekzone.co.nz [202.175.128.164] over a maximum of 30 hops:
1 2 19 ms 19 ms 18 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 18 ms 18 ms 18 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 19 ms 18 ms 19 ms datacom.ape.net.nz [192.203.154.82] 5 19 ms 20 ms 19 ms 210.55.5.227 6 * * * Request timed out. 7 20 ms 19 ms 19 ms mail.geekzone.co.nz [202.175.128.164]
Trace complete.
Can get 30 seconds through a 720 video before it buffers, and buffers and buffers.
Tracing route to cache.l.google.com [202.124.127.25] over a maximum of 30 hops:
1 2 11 ms 11 ms 11 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 11 ms 10 ms 11 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 25 ms 25 ms 25 ms 46.17.69.111.static.snap.net.nz [111.69.17.46] 5 26 ms 26 ms 29 ms 47.17.69.111.static.snap.net.nz [111.69.17.47] 6 26 ms 26 ms 26 ms 25.127.124.202.static.snap.net.nz [202.124.127.2 5]
Trace complete.
Tracing route to youtube.com [173.194.38.71] over a maximum of 30 hops:
1 2 22 ms 11 ms 31 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 11 ms 10 ms 10 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 12 ms 11 ms 11 ms 111-69-27-65.core.snap.net.nz [111.69.27.65] 5 12 ms 11 ms 12 ms 203.167.233.9 6 11 ms 12 ms 11 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125 ] 7 137 ms 143 ms 137 ms i-0-6-4-0.tlot-core01.bx.reach.com [202.84.142.1 10] 8 137 ms 137 ms 136 ms i-4-2.tlot03.bi.reach.com [202.84.251.150] 9 187 ms 186 ms 187 ms 72.14.197.53 10 228 ms 251 ms 186 ms 72.14.234.47 11 193 ms 186 ms 186 ms 64.233.174.190 12 207 ms 187 ms 186 ms 64.233.174.177 13 201 ms 198 ms 197 ms 209.85.255.35 14 196 ms 198 ms 197 ms 209.85.251.237 15 197 ms 197 ms 196 ms nrt19s17-in-f7.1e100.net [173.194.38.71]
Trace complete.
Tracing route to geekzone.co.nz [202.175.128.164] over a maximum of 30 hops:
1 2 11 ms 17 ms 11 ms 16.17.69.111.static.snap.net.nz [111.69.17.16] 3 11 ms 11 ms 11 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 11 ms 11 ms 11 ms datacom.ape.net.nz [192.203.154.82] 5 11 ms 11 ms 11 ms 210.55.5.227 6 * * * Request timed out. 7 12 ms 12 ms 12 ms mail.geekzone.co.nz [202.175.128.164]
Pinging cache.l.google.com [202.124.127.22] with 32 bytes of data: Reply from 202.124.127.22: bytes=32 time=11ms TTL=59 Reply from 202.124.127.22: bytes=32 time=11ms TTL=59 Reply from 202.124.127.22: bytes=32 time=12ms TTL=59 Reply from 202.124.127.22: bytes=32 time=12ms TTL=59
Ping statistics for 202.124.127.22: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 12ms, Average = 11ms
C:\Windows\system32>ping youtube.com
Pinging youtube.com [74.125.237.67] with 32 bytes of data: Reply from 74.125.237.67: bytes=32 time=55ms TTL=47 Reply from 74.125.237.67: bytes=32 time=53ms TTL=48 Reply from 74.125.237.67: bytes=32 time=53ms TTL=47 Reply from 74.125.237.67: bytes=32 time=53ms TTL=48
Ping statistics for 74.125.237.67: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 53ms, Maximum = 55ms, Average = 53ms
C:\Windows\system32>tracert cache.l.google.com
Tracing route to cache.l.google.com [202.124.127.22] over a maximum of 30 hops:
1 1 ms tracert youtube.com
Tracing route to youtube.com [74.125.237.67] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms NB6Plus4Wn.home [192.168.1.1] 2 18 ms 23 ms 25 ms 20.17.69.111.static.snap.net.nz [111.69.17.20] 3 12 ms 11 ms 12 ms 24.17.69.111.static.snap.net.nz [111.69.17.24] 4 * * * Request timed out. 5 27 ms 27 ms 27 ms 111-69-27-66.core.snap.net.nz [111.69.27.66] 6 28 ms 29 ms 28 ms 203.167.233.9 7 28 ms 28 ms 27 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125 ] 8 52 ms 53 ms 52 ms i-0-0-4-0.sydo-core02.bx.reach.com [202.84.142.1 53] 9 62 ms 59 ms 59 ms TenGigE0-1-0-13.oxf-gw1.Sydney.telstra.net [203. 50.13.121] 10 56 ms 59 ms 59 ms Bundle-Ether1.ken-core4.Sydney.telstra.net [203. 50.6.5] 11 58 ms 59 ms 58 ms Bundle-Ether1.ken39.Sydney.telstra.net [203.50.6 .146] 12 54 ms 54 ms 54 ms 72.14.198.54 13 54 ms 54 ms 54 ms 66.249.95.224 14 54 ms 54 ms 54 ms 72.14.237.55 15 55 ms 55 ms 54 ms youtube.com [74.125.237.67]
GoodSync. Easily back up and sync your files with GoodSync. Simple and secure file backup and synchronisation software will ensure that your files are never lost (affiliate link).
We have made some more tweaks to our systems here. So go ahead and give it a try, please let us know the results or any other feedback you have in regards to Youtube.
Joined snap last week - its certainly slower than Trust Power Kinect unlimited (streamed 1080p no problem 24/7) but it seems a lot better today, I was actually thinking before that it was great then I saw this thread was updated
Must say that it 'seems' to be better since the last fix. The odd video will do an instant buffer, but the majority at 360/480p buffer just enough to not be an issue.
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.