Youtube slow

Started by gazzthompson, Dec 16, 2010, 17:28:23

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages 1 2 3 4 5
User actions

pctech

#50
Dec 25, 2010, 17:26:38
Yes.

gazzthompson

#51
Dec 25, 2010, 17:29:18
So change all the DNS to IDnets one. What about the IP? is it ok if i use standard 192.168.0.XX ?

Holodene

#52
Dec 26, 2010, 01:20:15
I doubt the issue has anything to do with DNS/your home network setup.

Rik

#53
Dec 26, 2010, 05:20:36
The suggested static address, Gaz, is in fact your static IP address, and every time you connect, that's what you'll be using.

Change the DNS settings on your machines, either to two nominated servers or to pick up DNS automatically. From what you say, you're running with just a primary DNS server, so will have problems if that fails or is busy (ie lags).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gazzthompson

#54
Dec 26, 2010, 16:05:59 Last Edit: Dec 26, 2010, 16:12:50 by gazzthompson
Set up with both DNS. Still not as fast as it should be, or has been. Currently watching a 360p video and its barley buffering just above the speed needed to watch the video, i use to be able to watch 720p videos without buffering....

currently exchanging emails with support, see what happens... its also rather embarrassing  my friends 2meg~ BT line buffers videos better than my 5meg line ...

Ping youtube.com = 198ms
ping www.youtube.com = 32ms.

Maybe, somehow, when watching videos im connecting to the first rather than the latter? idk :dunno:

Rik

#55
Dec 26, 2010, 16:30:58
Run a tracert on both and paste the results back here will you. It could be a routing issue, but I'd expect everyone to be affected if it was.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gazzthompson

#56
Dec 26, 2010, 16:32:18
No idea what a tracert is or how i perform it.

davej99

#57
Dec 26, 2010, 16:49:49
Quote from: gazzthompson on Dec 26, 2010, 16:32:18
No idea what a tracert is or how i perform it.
I am not an expert but something like:
start
run
type "cmd"
OK
type "tracert utube.com"
enter

Rik

#58
Dec 26, 2010, 16:53:57
In Windows, depending on version, hit Start > Run > type CMD and hit enter. You may have to do it via the search bar.

From that, you'll get a DOS-like window open. In that, type tracert www.youtube.com and hit enter, then repeat with tracert youtube.com. Right-click on the title bar, select Edit > Select All, then hit enter to copy. Paste back here using Ctrl-V.

These are my results:

tracert www.youtube.com

Tracing route to youtube-ui.l.google.com [209.85.227.190]
over a maximum of 30 hops:

 1    <1 ms     1 ms     1 ms  192.168.1.254
 2    14 ms    15 ms    19 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    14 ms    15 ms    13 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    14 ms    14 ms    15 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    14 ms    15 ms    14 ms  google1.lonap.net [193.203.5.136]
 6    14 ms    13 ms    13 ms  209.85.255.76
 7    19 ms    21 ms    21 ms  72.14.232.134
 8    21 ms   131 ms    29 ms  209.85.252.83
 9    27 ms    33 ms    21 ms  209.85.243.101
10    19 ms    19 ms    23 ms  wy-in-f190.1e100.net [209.85.227.190]

Trace complete.

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  192.168.1.254
 2    14 ms    13 ms    21 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    13 ms    15 ms    13 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    14 ms    15 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    13 ms    13 ms    13 ms  google1.lonap.net [193.203.5.136]
 6    14 ms    13 ms    13 ms  209.85.255.78
 7   103 ms    84 ms    84 ms  209.85.250.54
 8   121 ms   114 ms   117 ms  216.239.46.215
 9   127 ms   126 ms   129 ms  72.14.232.141
10   126 ms   126 ms   127 ms  209.85.241.35
11   132 ms   137 ms   132 ms  72.14.239.193
12   129 ms   126 ms   126 ms  iw-in-f93.1e100.net [74.125.95.93]

Trace complete.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gazzthompson

#59
Dec 26, 2010, 16:54:46
Ok thanks.


Code Select
C:\Users\Gazz>tracert youtube.com

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

 1    <1 ms    23 ms    <1 ms  192.168.0.1
 2    27 ms    27 ms    27 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    26 ms    29 ms    26 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    27 ms    27 ms    26 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    42 ms    28 ms   104 ms  google1.lonap.net [193.203.5.136]
 6    39 ms    27 ms    27 ms  209.85.255.76
 7   107 ms   102 ms   126 ms  216.239.43.192
 8   134 ms   161 ms   167 ms  216.239.46.217
 9   184 ms   184 ms     *     72.14.233.116
10   192 ms   190 ms     *     216.239.46.208
11   199 ms   193 ms     *     64.233.174.125
12   229 ms   199 ms   204 ms  216.239.46.6
13   192 ms   192 ms   191 ms  pz-in-f93.1e100.net [74.125.127.93]

Trace complete.

C:\Users\Gazz>


Code Select

C:\Users\Gazz>tracert www.youtube.com

Tracing route to youtube-ui.l.google.com [209.85.227.190]
over a maximum of 30 hops:

 1     1 ms    <1 ms    27 ms  192.168.0.1
 2    27 ms   213 ms    26 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    81 ms    27 ms    70 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
 4    27 ms    27 ms    27 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    26 ms    91 ms    59 ms  google1.lonap.net [193.203.5.136]
 6    27 ms    32 ms    37 ms  209.85.255.76
 7    34 ms    84 ms    33 ms  72.14.232.134
 8    33 ms    34 ms    41 ms  216.239.49.45
 9    36 ms    35 ms    35 ms  209.85.243.101
10    33 ms    34 ms    33 ms  wy-in-f190.1e100.net [209.85.227.190]

Trace complete.

C:\Users\Gazz>

Rik

#60
Dec 26, 2010, 17:06:40
Well, it looks like you have interleaving on, but you're also getting a different route from hop 5 onwards. This is in the Google part of the routing control, IDNet hand over at LONAP, so I'm not sure why you're getting the route you are.

If anyone else feels like doing a trace to youtube.com (no www), I'd be interested to see the variations in route.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

davej99

#61
Dec 26, 2010, 17:17:53
>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  192.168.0.1
  2    54 ms    43 ms    43 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    44 ms     *       43 ms  telehouse-gw5-e4-400.idnet.net [212.69.63.245]
  4    44 ms    43 ms    42 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    43 ms   147 ms    42 ms  google1.lonap.net [193.203.5.136]
  6    44 ms    43 ms    44 ms  209.85.255.76
  7   119 ms   139 ms   126 ms  216.239.43.192
  8   152 ms   149 ms   149 ms  216.239.46.217
  9   159 ms   157 ms   162 ms  209.85.241.22
10   161 ms   160 ms   159 ms  209.85.241.27
11   168 ms   161 ms   161 ms  209.85.240.45
12   160 ms   160 ms   159 ms  iw-in-f93.1e100.net [74.125.95.93]

Rik

#62
Dec 26, 2010, 17:20:49
Thanks, Dave. At least we end up in the same place. :) What did it give from XP? ;D
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

gazzthompson

#63
Dec 26, 2010, 17:22:03
Does the 190ms+ on my tracert explain why its slower than i think it should be?

Glenn

#64
Dec 26, 2010, 17:22:16
From a TT connection over wireless
Tracing route to youtube.com
over a maximum of 30 hops:

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    26 ms    25 ms    23 ms  89.242.48.1
 3    32 ms    33 ms    33 ms  62.24.254.224
 4    35 ms    35 ms    35 ms  gig-14-1-4001-rtr002.man.opaltelecom.net [62.24.
254.225]
 5    37 ms    36 ms    35 ms  xe-10-0-0-rt001.bir.as13285.net [78.151.225.71]

 6    38 ms    37 ms    37 ms  xe-11-2-0-rt001.man.as13285.net [62.24.240.0]
 7    40 ms    39 ms    40 ms  xe-11-1-0-rt001.sov.as13285.net [62.24.240.14]
 8    44 ms    43 ms    44 ms  host-78-144-0-214.as13285.net [78.144.0.214]
 9    45 ms    44 ms    44 ms  host-78-144-0-182.as13285.net [78.144.0.182]
10    78 ms    42 ms    42 ms  72.14.223.88
11    45 ms    44 ms    45 ms  209.85.255.78
12   109 ms   109 ms   127 ms  209.85.250.54
13   149 ms   147 ms   209 ms  216.239.46.215
14   196 ms   196 ms   196 ms  216.239.43.80
15   209 ms   207 ms   210 ms  216.239.46.212
16   208 ms   204 ms   264 ms  64.233.174.97
17   217 ms   209 ms   207 ms  216.239.46.6
18   202 ms   202 ms   201 ms  pz-in-f93.1e100.net [74.125.127.93]
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

davej99

#65
Dec 26, 2010, 17:22:29
Quote from: Rik on Dec 26, 2010, 17:20:49
Thanks, Dave. At least we end up in the same place. :) What did it give from XP? ;D

20ms overall  ;)

Rik

#66
Dec 26, 2010, 17:24:30
It's increasingly looking to me like Google has multiple routes and some are faster than others. Anyone else got a view?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#67
Dec 26, 2010, 17:24:43
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

#68
Dec 26, 2010, 17:26:17
I would imagine their server farms are taking a beating at the moment, around 40% of the worlds population are on holiday.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#69
Dec 26, 2010, 17:26:38
Thought. I'm on ADSL2+ (21CN), how about the rest of you. (It shouldn't affect the Google routing, but I'm clutching at straws here.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#70
Dec 26, 2010, 17:27:16
Quote from: Glenn on Dec 26, 2010, 17:26:17
I would imagine their server farms are taking a beating at the moment, around 40% of the worlds population are on holiday.

You're not wrong there, Glenn, otoh business traffic should be correspondingly lighter.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

#71
Dec 26, 2010, 17:29:40
The Mac traceroute gives multiple IP addresses for youtube.com (clever eh)

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)  0.945 ms  0.705 ms  0.638 ms
2  telehouse-gw2-lo1.idnet.net (212.69.63.51)  10.991 ms  23.721 ms  9.525 ms
3  telehouse-gw5-e4-400.idnet.net (212.69.63.245)  9.430 ms  9.298 ms  9.276 ms
4  redbus-gw2-g0-1-331.idnet.net (212.69.63.5)  9.989 ms  11.347 ms  9.969 ms
5  google1.lonap.net (193.203.5.136)  61.259 ms  10.079 ms  9.907 ms
6  209.85.255.76 (209.85.255.76)  72.945 ms
    209.85.255.78 (209.85.255.78)  10.905 ms
    209.85.255.76 (209.85.255.76)  9.763 ms
7  209.85.250.54 (209.85.250.54)  77.991 ms
    216.239.43.192 (216.239.43.192)  99.818 ms  83.573 ms
8  216.239.46.217 (216.239.46.217)  120.332 ms
    216.239.46.215 (216.239.46.215)  114.174 ms
    216.239.46.217 (216.239.46.217)  115.745 ms
9  209.85.241.22 (209.85.241.22)  123.765 ms  126.333 ms
    72.14.232.141 (72.14.232.141)  125.035 ms
10  209.85.241.37 (209.85.241.37)  124.724 ms
    209.85.241.35 (209.85.241.35)  122.907 ms
    209.85.241.37 (209.85.241.37)  126.795 ms
11  72.14.239.193 (72.14.239.193)  129.089 ms
    72.14.239.189 (72.14.239.189)  127.285 ms
    209.85.240.49 (209.85.240.49)  125.634 ms
12  iw-in-f93.1e100.net (74.125.95.93)  127.169 ms  127.377 ms  129.190 ms
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

#72
Dec 26, 2010, 17:31:10
TalkTalk LLU here in warm Cornwall.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#73
Dec 26, 2010, 17:34:58
So a completely different route as far as LONAP.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

pctech

#74
Dec 26, 2010, 20:20:45
Thimk it was mentioned earlier that tracerting to youtube.com is not the same as the route to www.youtube.com

Code Select
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    23 ms    22 ms    23 ms  losubs.subs.dsl3.th-lon.zen.net.uk [62.3.84.25]

  3    23 ms    22 ms    23 ms  ae0-116.cr1.th-lon.zen.net.net [62.3.84.193]
  4    23 ms    41 ms    22 ms  google1.lonap.net [193.203.5.136]
  5    24 ms    23 ms    24 ms  209.85.255.78
  6   103 ms   101 ms   101 ms  209.85.250.54
  7   139 ms   135 ms   135 ms  216.239.46.215
  8   167 ms   146 ms   146 ms  72.14.232.141
  9   146 ms   145 ms   146 ms  209.85.241.35
10   153 ms   145 ms   158 ms  209.85.240.45
11   146 ms   145 ms   145 ms  iw-in-f93.1e100.net [74.125.95.93]

Trace complete.

C:\Documents and Settings\Admin>tracert www.youtube.com

Tracing route to youtube-ui.l.google.com [209.85.229.136]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    24 ms    22 ms    22 ms  losubs.subs.dsl3.th-lon.zen.net.uk [62.3.84.25]

  3    24 ms    59 ms    23 ms  ae0-116.cr1.th-lon.zen.net.net [62.3.84.193]
  4    23 ms    23 ms    23 ms  195.66.226.125
  5    25 ms    23 ms    23 ms  209.85.252.76
  6    58 ms    30 ms    30 ms  72.14.232.134
  7    29 ms    30 ms    30 ms  209.85.252.83
  8    33 ms    29 ms    30 ms  209.85.243.85
  9    31 ms    29 ms    28 ms  ww-in-f136.1e100.net [209.85.229.136]

Trace complete.



Though I would have throught the clip traffic takes the shorter route though.
Print
Go Up Pages 1 2 3 4 5
User actions