Youtube slow

gazzthompson · Dec 27, 2010, 16:20:40

Support has suggested i try another router..... currently using a DG834GT with latest firmware.

DorsetBoy · Dec 27, 2010, 18:02:04

tracert youtube.com

Tracing route to youtube.com [74.125.95.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Vigor.router [192.168.1.1]
  2    25 ms    26 ms    27 ms  lns2.uan.thn.uk.murphx.net [89.145.254.70]
  3    27 ms    27 ms    26 ms  uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
  4    27 ms    27 ms    36 ms  ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161]
  5    26 ms    27 ms    26 ms  te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
  6     *        *        *     Request timed out.
  7    27 ms    33 ms    27 ms  209.85.255.175
  8    95 ms   100 ms   135 ms  209.85.250.54
  9   127 ms   127 ms   128 ms  216.239.46.215
 10   138 ms   143 ms   140 ms  72.14.232.141
 11   138 ms   139 ms   139 ms  209.85.241.35
 12   145 ms   140 ms   145 ms  209.85.240.45
 13   140 ms   140 ms   140 ms  iw-in-f93.1e100.net [74.125.95.93]

Trace complete.

>ping -n 10 youtube.com

Pinging youtube.com [74.125.95.93] with 32 bytes of data:
Reply from 74.125.95.93: bytes=32 time=139ms TTL=52
Reply from 74.125.95.93: bytes=32 time=139ms TTL=52
Reply from 74.125.95.93: bytes=32 time=139ms TTL=52
Reply from 74.125.95.93: bytes=32 time=138ms TTL=52
Reply from 74.125.95.93: bytes=32 time=138ms TTL=52
Reply from 74.125.95.93: bytes=32 time=137ms TTL=52
Reply from 74.125.95.93: bytes=32 time=139ms TTL=52
Reply from 74.125.95.93: bytes=32 time=138ms TTL=52
Reply from 74.125.95.93: bytes=32 time=138ms TTL=52
Reply from 74.125.95.93: bytes=32 time=138ms TTL=52

Ping statistics for 74.125.95.93:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 137ms, Maximum = 139ms, Average = 138ms

>ping -n 10 youtube.co.uk

Pinging youtube.co.uk [74.125.45.100] with 32 bytes of data:
Reply from 74.125.45.100: bytes=32 time=120ms TTL=53
Reply from 74.125.45.100: bytes=32 time=120ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53
Reply from 74.125.45.100: bytes=32 time=120ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53
Reply from 74.125.45.100: bytes=32 time=121ms TTL=53
Reply from 74.125.45.100: bytes=32 time=119ms TTL=53

Ping statistics for 74.125.45.100:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 119ms, Maximum = 121ms, Average = 119ms

tracert youtube.co.uk

Tracing route to youtube.co.uk [74.125.45.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Vigor.router [192.168.1.1]
  2    40 ms    26 ms    27 ms  lns2.uan.thn.uk.murphx.net [89.145.254.70]
  3    27 ms    27 ms    26 ms  uan-er1.uan.thn.uk.murphx.net [89.145.254.65]
  4    25 ms    27 ms    27 ms  ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161]
  5    26 ms    27 ms    27 ms  te2-3.cr05.tn5.bb.gxn.net [62.72.139.97]
  6     *        *        *     Request timed out.
  7    27 ms    27 ms    26 ms  209.85.252.76
  8   103 ms   101 ms   100 ms  216.239.43.192
  9   122 ms   126 ms   120 ms  209.85.251.9
 10   118 ms   132 ms   119 ms  72.14.232.215
 11   132 ms   126 ms   124 ms  209.85.253.133
 12   119 ms   121 ms   120 ms  yx-in-f100.1e100.net [74.125.45.100]

Trace complete.

Gary · Dec 27, 2010, 18:44:31

Quote from: DorsetBoy on Dec 27, 2010, 18:02:04
Code Select Expand
tracert youtube.com Tracing route to youtube.com [74.125.95.93] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Vigor.router [192.168.1.1] 2 25 ms 26 ms 27 ms lns2.uan.thn.uk.murphx.net [89.145.254.70] 3 27 ms 27 ms 26 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65] 4 27 ms 27 ms 36 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161] 5 26 ms 27 ms 26 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97] 6 * * * Request timed out. 7 27 ms 33 ms 27 ms 209.85.255.175 8 95 ms 100 ms 135 ms 209.85.250.54 9 127 ms 127 ms 128 ms 216.239.46.215 10 138 ms 143 ms 140 ms 72.14.232.141 11 138 ms 139 ms 139 ms 209.85.241.35 12 145 ms 140 ms 145 ms 209.85.240.45 13 140 ms 140 ms 140 ms iw-in-f93.1e100.net [74.125.95.93] Trace complete. >ping -n 10 youtube.com Pinging youtube.com [74.125.95.93] with 32 bytes of data: Reply from 74.125.95.93: bytes=32 time=139ms TTL=52 Reply from 74.125.95.93: bytes=32 time=139ms TTL=52 Reply from 74.125.95.93: bytes=32 time=139ms TTL=52 Reply from 74.125.95.93: bytes=32 time=138ms TTL=52 Reply from 74.125.95.93: bytes=32 time=138ms TTL=52 Reply from 74.125.95.93: bytes=32 time=137ms TTL=52 Reply from 74.125.95.93: bytes=32 time=139ms TTL=52 Reply from 74.125.95.93: bytes=32 time=138ms TTL=52 Reply from 74.125.95.93: bytes=32 time=138ms TTL=52 Reply from 74.125.95.93: bytes=32 time=138ms TTL=52 Ping statistics for 74.125.95.93: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 137ms, Maximum = 139ms, Average = 138ms >ping -n 10 youtube.co.uk Pinging youtube.co.uk [74.125.45.100] with 32 bytes of data: Reply from 74.125.45.100: bytes=32 time=120ms TTL=53 Reply from 74.125.45.100: bytes=32 time=120ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Reply from 74.125.45.100: bytes=32 time=120ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Reply from 74.125.45.100: bytes=32 time=121ms TTL=53 Reply from 74.125.45.100: bytes=32 time=119ms TTL=53 Ping statistics for 74.125.45.100: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 119ms, Maximum = 121ms, Average = 119ms tracert youtube.co.uk Tracing route to youtube.co.uk [74.125.45.100] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Vigor.router [192.168.1.1] 2 40 ms 26 ms 27 ms lns2.uan.thn.uk.murphx.net [89.145.254.70] 3 27 ms 27 ms 26 ms uan-er1.uan.thn.uk.murphx.net [89.145.254.65] 4 25 ms 27 ms 27 ms ge2-6-1.cr1.core.thn.uk.murphx.net [89.145.254.161] 5 26 ms 27 ms 27 ms te2-3.cr05.tn5.bb.gxn.net [62.72.139.97] 6 * * * Request timed out. 7 27 ms 27 ms 26 ms 209.85.252.76 8 103 ms 101 ms 100 ms 216.239.43.192 9 122 ms 126 ms 120 ms 209.85.251.9 10 118 ms 132 ms 119 ms 72.14.232.215 11 132 ms 126 ms 124 ms 209.85.253.133 12 119 ms 121 ms 120 ms yx-in-f100.1e100.net [74.125.45.100] Trace complete.

I think you have to use www.youtube.com for it to find the closest server Dorset, but I could be wrong

Traceroute has started…

traceroute: Warning: www.youtube.com has multiple addresses; using 209.85.227.93
traceroute to youtube-ui.l.google.com (209.85.227.93), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 4.210 ms 3.586 ms 5.100 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 18.325 ms 18.240 ms 19.555 ms
3 telehouse-gw5-e4-400.idnet.net (212.69.63.245) 15.277 ms 18.341 ms 20.324 ms
4 redbus-gw2-g0-1-331.idnet.net (212.69.63.5) 19.902 ms 20.245 ms 19.132 ms
5 google1.lonap.net (193.203.5.136) 20.253 ms 49.546 ms 17.810 ms
6 209.85.255.76 (209.85.255.76) 17.499 ms 19.044 ms
209.85.255.78 (209.85.255.78) 18.768 ms
7 66.249.95.173 (66.249.95.173) 25.995 ms 24.531 ms 26.328 ms
8 209.85.251.231 (209.85.251.231) 23.653 ms 92.700 ms
209.85.252.83 (209.85.252.83) 22.686 ms
9 209.85.243.93 (209.85.243.93) 34.986 ms
209.85.243.101 (209.85.243.101) 30.423 ms
209.85.243.89 (209.85.243.89) 25.776 ms
10 wy-in-f93.1e100.net (209.85.227.93) 23.411 ms 23.571 ms 25.693 ms

This is over wifi

Traceroute has started…

traceroute: Warning: youtube.com has multiple addresses; using 74.125.95.93
traceroute to youtube.com (74.125.95.93), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 2.908 ms 1.167 ms 3.331 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 21.085 ms 16.864 ms 14.887 ms
3 telehouse-gw5-e4-400.idnet.net (212.69.63.245) 15.103 ms 19.442 ms 16.103 ms
4 redbus-gw2-g0-1-331.idnet.net (212.69.63.5) 19.434 ms 18.603 ms 16.026 ms
5 google1.lonap.net (193.203.5.136) 18.808 ms 20.570 ms 15.581 ms
6 209.85.255.78 (209.85.255.78) 59.347 ms
209.85.255.76 (209.85.255.76) 26.835 ms
209.85.255.78 (209.85.255.78) 32.561 ms
7 209.85.250.54 (209.85.250.54) 85.159 ms 85.263 ms
216.239.43.192 (216.239.43.192) 111.535 ms
8 216.239.46.215 (216.239.46.215) 120.456 ms 120.509 ms
216.239.46.217 (216.239.46.217) 128.605 ms
9 72.14.232.141 (72.14.232.141) 129.484 ms
209.85.241.22 (209.85.241.22) 136.681 ms 136.276 ms
10 209.85.241.35 (209.85.241.35) 136.792 ms
209.85.241.27 (209.85.241.27) 133.638 ms
209.85.241.29 (209.85.241.29) 133.894 ms
11 72.14.239.189 (72.14.239.189) 132.460 ms
209.85.240.49 (209.85.240.49) 132.714 ms
209.85.240.45 (209.85.240.45) 135.604 ms
12 iw-in-f93.1e100.net (74.125.95.93) 131.912 ms 129.108 ms 129.304 ms

pctech · Dec 27, 2010, 18:48:39

You are correct Gary as otherwise it ends up at a server in the States which is why you can see the high latency.

Gary · Dec 27, 2010, 18:52:05

Quote from: pctech on Dec 27, 2010, 18:48:39
You are correct Gary as otherwise it ends up at a server in the States which is why you can see the high latency.

Thanks for clearing that up Mitch

pctech · Dec 27, 2010, 18:54:26

Np, navigating to just youtube.com bounces you over to www.youtube.com anyway so I doubt this will have any bearing on Gaz's issue.

DorsetBoy · Dec 27, 2010, 18:55:54

That is what I was taught long ago, however Mark Baker at fast.co.uk insisted that www. must never be used on a ping or tracert and they would not accept stats that included it.

Gary · Dec 27, 2010, 19:02:04

You tube is fast here, I can watch 1080p over wifi with no issue, saying that browsing seems snappier tonight than a few days back anyway for me.

pctech · Dec 27, 2010, 19:05:29

Pass Dorset but as you can see it gives very different results.

gazzthompson · Dec 28, 2010, 16:42:26

Im not really willing to spend money on a new router and the effort it comes with if im honest. Im going to give IDnet the benefit of the doubt till January then try another company for a month.

pctech · Dec 28, 2010, 16:44:37

Most are going to yearly contracts but I can recommend Zen if you want to try someone else.

However I think their hunch maybe correct on this, one other thought, have you tried a factory reset on the router?

gazzthompson · Dec 28, 2010, 16:52:23

Well i will only be trying another monthly contract one, not a yearly... like Zen.

Ill try a factory reset soon.

pctech · Dec 28, 2010, 17:06:00

Sorry mate, Zen are monthly.

I wouldn't go on a yearly contract.

gazzthompson · Dec 28, 2010, 17:48:11

Yeah i failed, ill be trying monthly ones.. like Zen (is what i meant to say). but w'll see.

pctech · Dec 28, 2010, 17:53:13

Try the reset (with power connected) first and then try another ISP, if it fails then your equipment needs replacing.

gazzthompson · Jan 20, 2011, 22:00:36

Im trying to listen to music and im having to buffer and wait for this 360p video

http://www.youtube.com/watch?v=3nKmNwqgjqo&feature=related

i dont know whats wrong?

Glenn · Jan 20, 2011, 22:02:45

I've just watched this at 360 with no problems http://www.youtube.com/watch?v=L4mGoRte104

gazzthompson · Jan 20, 2011, 22:05:48

Barley buffered on my 5meg line.

Glenn · Jan 20, 2011, 22:06:58

Something is strange then, as I'm on a 2.5mb profile.

Glenn · Jan 20, 2011, 22:09:05

I'm playing your link at 480 with no buffering, so I would think it is local.

pctech · Jan 20, 2011, 22:29:25

I wonder if it was stored on a server in the States and your requsst caused it to be copied to Google's UK cache which would improve performance.

pctech · Jan 20, 2011, 22:40:04

Couple of tests I have done would appear to support this.

First visit: sluggish with frequent buffering.

Copied URL, closed and reopened browser (FF) pasted URL in.

Second visit: no buffering.

My line gets throughput of around 2.38Mbps.

Gary · Jan 21, 2011, 07:26:26

No buffering etc, line throughput of 6.57Mbps on other youtube video, but your Original Url :
http://www.youtube.com/watch?v=3nKmNwqgjqo&feature=related said fault please wait on first visit, second visit plays perfectly

gazzthompson · Jan 21, 2011, 16:17:03

Its working fine now, tho the buffer isnt as fast as i would think it would be on a 5Mbps line... seems very sporadic

gazzthompson · Jan 21, 2011, 16:30:23

Ok update:

http://www.youtube.com/watch?v=s66PdneR4RI&feature=related

failed to buffer, restarted browser (chrome) and its now playing... though again, still not as fast as i would expect a 5Mbps line to be