To be honest, I posted the tracert because youtube was feeling a little sluggish, and I noticed all the +200ms hops. I didn't even realize that it was resolving
www.youtube.com to a weird address..
Here's a tracert using an IS-based test account, using 'www.youtube.com' and still using UnoTelly:
Tracing route to youtube-ui.l.google.com [64.233.184.190]
over a maximum of 30 hops:
1 5 ms 2 ms 6 ms HOME [192.168.1.1]
2 10 ms 13 ms 10 ms 196-215-220-1.dynamic.isadsl.co.za [196.215.220.1]
3 12 ms 14 ms 19 ms cdsl1-umh-gi0-0-0-3102.ip.isnet.net [196.38.74.245]
4 13 ms 13 ms 12 ms 196.26.210.200
5 13 ms 13 ms 15 ms mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net [168.209.93.240]
6 29 ms 26 ms 27 ms 168.209.0.178
7 30 ms 29 ms 29 ms core1a-bry-gi0-0-0.ip.isnet.net [168.209.217.1]
8 25 ms 25 ms 26 ms core1a-bry-ge1-0-1.isnet.net [168.209.100.237]
9 25 ms 25 ms 25 ms 196.26.0.130
10 25 ms 29 ms 25 ms 72.14.205.16
11 198 ms 198 ms 197 ms 66.249.95.8
12 194 ms 192 ms 194 ms proxy.google.com [216.239.51.5]
13 205 ms 203 ms 206 ms 64.233.174.82
14 198 ms 198 ms 198 ms 209.85.255.223
15 * * * Request timed out.
16 203 ms 203 ms 207 ms 64.233.184.190
Trace complete.