youtube being throttled on bt?

Daemonic

Same when running the trace to ie.youtube.com

traceroute to ie.youtube.com (208.65.153.253), 30 hops max, 40 byte packets
1 bas505.cwt.esat.net (193.95.136.241) 11.220 ms 10.236 ms 10.679 ms
2 vlan501.rt502.cwt.esat.net (193.95.137.125) 24.135 ms 12.442 ms 10.276 ms
3 vlan52.rt001.cwt.esat.net (193.95.130.145) 11.070 ms 10.029 ms 9.348 ms
4 ge1-0.core002.cwt.esat.net (193.95.129.2) 10.526 ms 9.531 ms 10.234 ms
5 pos2-0.br002.ldn.esat.net (193.95.131.50) 27.503 ms 27.093 ms 27.207 ms
6 195.66.226.185 (195.66.226.185) 27.939 ms 27.592 ms 103.150 ms
7 g2-0-0.core02.lon01.atlas.cogentco.com (130.117.1.61) 29.131 ms 51.646 ms 27.468 ms
8 p0-0.core01.jfk02.atlas.cogentco.com (130.117.2.105) 95.426 ms 95.258 ms 95.284 ms
9 p5-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 94.752 ms 95.286 ms 95.678 ms
10 t4-2.mpd01.jfk01.atlas.cogentco.com (154.54.7.114) 96.292 ms 97.260 ms 96.247 ms
11 t4-4.mpd01.ewr03.atlas.cogentco.com (154.54.1.38) 96.377 ms 95.067 ms 138.586 ms
12 you-tube-llc.demarc.cogentco.com (38.101.84.66) 137.120 ms 138.770 ms 136.315 ms
13 * * * Request timed out.
14 * * * Request timed out.
15 64.15.116.13 (64.15.116.13) 156.489 ms 157.612 ms 160.192 ms
16 * * * Request timed out.
17 * * * Request timed out.
18 208.65.153.253 (208.65.153.253) 207.751 ms 203.638 ms 203.934 ms
Trace complete

Barlow07

Daemonic wrote:

Same when running the trace to ie.youtube.com

traceroute to ie.youtube.com (208.65.153.253), 30 hops max, 40 byte packets
1 bas505.cwt.esat.net (193.95.136.241) 11.220 ms 10.236 ms 10.679 ms
2 vlan501.rt502.cwt.esat.net (193.95.137.125) 24.135 ms 12.442 ms 10.276 ms
3 vlan52.rt001.cwt.esat.net (193.95.130.145) 11.070 ms 10.029 ms 9.348 ms
4 ge1-0.core002.cwt.esat.net (193.95.129.2) 10.526 ms 9.531 ms 10.234 ms
5 pos2-0.br002.ldn.esat.net (193.95.131.50) 27.503 ms 27.093 ms 27.207 ms
6 195.66.226.185 (195.66.226.185) 27.939 ms 27.592 ms 103.150 ms
7 g2-0-0.core02.lon01.atlas.cogentco.com (130.117.1.61) 29.131 ms 51.646 ms 27.468 ms
8 p0-0.core01.jfk02.atlas.cogentco.com (130.117.2.105) 95.426 ms 95.258 ms 95.284 ms
9 p5-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 94.752 ms 95.286 ms 95.678 ms
10 t4-2.mpd01.jfk01.atlas.cogentco.com (154.54.7.114) 96.292 ms 97.260 ms 96.247 ms
11 t4-4.mpd01.ewr03.atlas.cogentco.com (154.54.1.38) 96.377 ms 95.067 ms 138.586 ms
12 you-tube-llc.demarc.cogentco.com (38.101.84.66) 137.120 ms 138.770 ms 136.315 ms
13 * * * Request timed out.
14 * * * Request timed out.
15 64.15.116.13 (64.15.116.13) 156.489 ms 157.612 ms 160.192 ms
16 * * * Request timed out.
17 * * * Request timed out.
18 208.65.153.253 (208.65.153.253) 207.751 ms 203.638 ms 203.934 ms
Trace complete

I'm having the same problem with eircom BB, but it seems that BT, IBB and possbile other service providers customer's are having the same problems. I could be wrong but it seems that the issue is with a server on a network that ISP are connected. I was talking to tech and there is not much they can do?

I wont be going on youtube for while. Anyone else have any other information on what is happening.

vibe666

nothing more back from youtube support, i think i might have p*ssed them off with my last reply, but it was such a pointless cut/paste bullsh*t email response that showed they hadn't even read past the subject of my email and just sent me back their default response.

there are other sites though. metacafe springs to mind. aspparently if you upload (original) video's and they get a lot of views you can even earn a bit of cash.

i would say that if enough people contact their ISP's to complain, that someone will have to do something about it eventually. anyone know any reporters?

vishal

This time it is vlan54.rt002.cwt.esat-x.com [193.95.130.161]

tracert youtube.com

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

1 1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms bas506.cwt.esat.net [193.95.136.242]
3 14 ms 8 ms 10 ms vlan500.rt502.cwt.esat.net [193.95.136.125]
4 147 ms 14 ms 9 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 10 ms 9 ms 9 ms ge0-0.core002.cwt.esat.net [193.95.129.18]
6 26 ms 26 ms 25 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
7 26 ms 26 ms 26 ms 195.66.226.185
8 26 ms 26 ms 26 ms g9-0-0.core01.lon01.atlas.cogentco.com [130.117.
1.77]
9 101 ms 100 ms 100 ms p3-0.core02.jfk02.atlas.cogentco.com [66.28.4.18
9]
10 101 ms 100 ms 100 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
11 105 ms 100 ms 99 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
12 100 ms 100 ms 100 ms t4-2.mpd01.ewr03.atlas.cogentco.com [154.54.1.30
]
13 113 ms 113 ms 113 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

14 * * * Request timed out.
15 * * * Request timed out.
16 134 ms 134 ms 134 ms 64.15.116.9
17 * * * Request timed out.
18 * * * Request timed out.
19 182 ms 183 ms 182 ms 208.65.153.238

Trace complete.

vishal

is it just me or has Praetor post been removed?

vishal

seems to be working fine now.

Markjf

vishal wrote:

is it just me or has Praetor post been removed?

Yes it was removed or he removed it himself why ? I don't know. He said in it “ there were engineers working on the problem in city west and that it could take a few days as it was an intermittent problem”
My tracert is coming up as bad as ever with high hits at 3 and 7


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

1 4 ms 2 ms 1 ms mygateway.ar7 [192.168.1.1]
2 31 ms 13 ms 16 ms bas002.bmt.esat.net [193.95.142.243]
3 149 ms 192 ms 21 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
4 21 ms 13 ms 13 ms ge1-0.core001.bmt.esat.net [193.95.140.17]
5 14 ms 13 ms 21 ms pos3-0.core001.cwt.esat.net [193.95.131.41]
6 14 ms 15 ms 14 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
7 462 ms 366 ms 407 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
8 31 ms 30 ms 108 ms 195.66.226.185
9 71 ms 30 ms 55 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
10 378 ms 251 ms 101 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
11 109 ms 102 ms 101 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
12 110 ms 101 ms 101 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
13 343 ms 282 ms 334 ms t4-2.mpd01.ewr03.atlas.cogentco.com [154.54.1.30
]
14 121 ms 187 ms 120 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

15 * * * Request timed out.
16 * * * Request timed out.
17 142 ms 142 ms 142 ms 64.15.116.5
18 * * * Request timed out.
19 * * * Request timed out.
20 200 ms 190 ms 190 ms www.youtube.com [208.65.153.253]

Trace complete.

Barlow07

vishal wrote:

is it just me or has Praetor post been removed?

I noticed this last night. I assumed that he works for BT, which is why he said engineers would fix the issue within a few days. I can only think that someone had a quiet word in his ear and that he or a moderator removed his post's for legal reasons.

pug_

Markjf wrote:

Yes it was removed or he removed it himself why ? I don't know. He said in it “ there were engineers working on the problem in city west and that it could take a few days as it was an intermittent problem”
My tracert is coming up as bad as ever with high hits at 3 and 7


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

1 4 ms 2 ms 1 ms mygateway.ar7 [192.168.1.1]
2 31 ms 13 ms 16 ms bas002.bmt.esat.net [193.95.142.243]
3 149 ms 192 ms 21 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
4 21 ms 13 ms 13 ms ge1-0.core001.bmt.esat.net [193.95.140.17]
5 14 ms 13 ms 21 ms pos3-0.core001.cwt.esat.net [193.95.131.41]
6 14 ms 15 ms 14 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
7 462 ms 366 ms 407 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
8 31 ms 30 ms 108 ms 195.66.226.185
9 71 ms 30 ms 55 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
10 378 ms 251 ms 101 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
11 109 ms 102 ms 101 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
12 110 ms 101 ms 101 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
13 343 ms 282 ms 334 ms t4-2.mpd01.ewr03.atlas.cogentco.com [154.54.1.30
]
14 121 ms 187 ms 120 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

15 * * * Request timed out.
16 * * * Request timed out.
17 142 ms 142 ms 142 ms 64.15.116.5
18 * * * Request timed out.
19 * * * Request timed out.
20 200 ms 190 ms 190 ms www.youtube.com [208.65.153.253]

Trace complete.

Maybe because he was talking sh1te? the thing about traceroutes that most people don't really get is that even though they can be a good indication of a network problem you have to learn how to read them properly.

In all of the examples given the hop preator asked to highlight showed traffic flowing through it just fine. The fact that the node it's self responded slowly isn't an indicator of a problem as most ISP's configure their devices to give ICMP traffic lower prioraty to internet traffic passing through a device. If there are slow response times from one particular hop on then you're more likely to have located a problem.

Again if you look at the examples given in each case the traceroutes start to get slow from p9-0.core02.jfk02.atlas.cogentco.com on, which indicates the problem is more than likely located on the cogent network.

Bohrio

That is true

In fact if you tracert ANY target you will get the same result, try it yourself, trace not only youtube but google.com or yahoo.com for example and you will see for yourself.

If BT says the problem is not at their side then it must be true. Tracerts are tricky to interpreter, for us, it is impossible to determine if there is a problem or not, we have trust BT and accept that the problem is outside BT's network, at least BT Ireland, BT UK node is a bit of a joke though.

Could also be a problem with Youtube's lynx system, I have heard they are being overloaded.

Whatever it is BT is aware of it and if they havent done anything is either because the can't (out of their scheme) or they dont know (which I doubt it)

Praetor either misread or rushed when he said it was a routing problem (very unlikely though as packets do reach destination) and PUG has said ICMP is normally consider low priority request, so when the router receives the request from a user it will acknowledge it, finish doing other request and then reply to that ICMP you requested. Doesnt mean there is a problem is just not considered important at that moment, basically let just say that the router has better things to do!

I must say that if a router is too busy to reply it does indicate that, at that moment, is working at high capacity.

At first it did looked like a BT issue but if you look to all those tracerts its clear that the high latency occurs overseas.

Have anyone else using a different ISP had the same problem?

Markjf

Thanks for the info guys, interesting stuff. As I said earlier in the tread I did a test with my brother who is on Eircom at home and he had no problem but in his job they have Bt and over the last few weeks it’s imposable to use YouTube. I will get him to do a tracert later for me and see what he comes up with.

So from what you are saying you need a string of high hops before you can class it as being a problem area? Here is another tracert to google.com a few high spots but not to bad,


Tracing route to www.l.google.com [64.233.183.104]
over a maximum of 30 hops:

1 2 ms 1 ms 2 ms mygateway.ar7 [192.168.1.1]
2 14 ms 14 ms 13 ms bas002.bmt.esat.net [193.95.142.243]
3 15 ms 13 ms 13 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
4 20 ms 17 ms 14 ms ge0-0.core002.bmt.esat.net [193.95.140.18]
5 51 ms 15 ms 17 ms t2a2-p9-0-0.ie-dub2.eu.bt.net [166.49.198.137]
6 14 ms 19 ms 15 ms t2c1-ge6-0.ie-dub2.eu.bt.net [166.49.158.11]
7 40 ms 38 ms 41 ms t2c1-p4-0.uk-lon2.eu.bt.net [166.49.195.41]
8 38 ms 53 ms 41 ms t2c2-ge7-2.uk-lon2.eu.bt.net [166.49.164.174]
9 43 ms 47 ms 40 ms t2c1-ge4-2.uk-lon1.eu.bt.net [166.49.208.6]
10 145 ms 59 ms 39 ms t2a1-ge4-0-0.uk-lon1.eu.bt.net [166.49.135.102]

11 43 ms 38 ms 40 ms 195.66.224.125
12 40 ms 57 ms 70 ms 209.85.252.42
13 331 ms 279 ms 185 ms 216.239.43.123
14 45 ms 358 ms 398 ms 72.14.232.141
15 43 ms 43 ms 44 ms 72.14.233.81
16 65 ms 52 ms 51 ms 209.85.249.133
17 44 ms 43 ms 48 ms www.google.com [64.233.183.104]

Trace complete


Here is one for you tube again, I took a few and they all seem to get bad around 10 or 11



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

1 1 ms 1 ms 1 ms mygateway.ar7 [192.168.1.1]
2 14 ms 14 ms 14 ms bas002.bmt.esat.net [193.95.142.243]
3 16 ms 15 ms 14 ms vlan103.rt002.bmt.esat.net [193.95.142.1]
4 14 ms 14 ms 13 ms ge1 [193.95.140.17]
5 13 ms 17 ms 15 ms pos3 [193.95.131.41]
6 190 ms 14 ms 14 ms ge0 [193.95.129.18]
7 31 ms 30 ms 31 ms pos2 [193.95.131.50]
8 31 ms 40 ms 36 ms 195.66.226.185
9 34 ms 31 ms 39 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
10 99 ms 372 ms 120 ms p0-0.core01.jfk02.atlas.cogentco.com [130.117.2.
105]
11 133 ms 130 ms 97 ms p5-0.core01.jfk01.atlas.cogentco.com [66.28.4.9]

12 106 ms 245 ms * t4-2.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
4]
13 130 ms 119 ms 113 ms t4-4.mpd01.ewr03.atlas.cogentco.com [154.54.1.38
]
14 121 ms 190 ms 133 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

15 * * * Request timed out.
16 * * * Request timed out.
17 170 ms 179 ms 144 ms 64.15.116.5
18 * * * Request timed out.
19 * * * Request timed out.
20 192 ms 204 ms 210 ms www.youtube.com [208.65.153.251]

Trace complete.

Bohrio

Look, this is a tracert to google.com

See what I mean?

Tracing route to www.google.com [64.233.183.104]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms voyager.home [192.168.1.1]
2 26 ms 11 ms 18 ms bas502.cwt.esat.net [193.95.136.238]
3 88 ms 36 ms 12 ms vlan501.rt502.cwt.esat.net [193.95.137.125]
4 17 ms 13 ms 11 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 10 ms 13 ms 11 ms ge2-0.br003.cwt.esat.net [193.95.129.23]
6 11 ms 11 ms 12 ms ^C

3 seconds later

Tracing route to www.google.com [64.233.183.104]
over a maximum of 30 hops:

1 4 ms 1 ms 1 ms voyager.home [192.168.1.1]
2 11 ms 12 ms 14 ms bas502.cwt.esat.net [193.95.136.238]
3 154 ms 11 ms 12 ms vlan501.rt502.cwt.esat.net [193.95.137.125]
4 12 ms 16 ms 12 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 13 ms 19 ms 11 ms ge2-0.br003.cwt.esat.net [193.95.129.23]
6 12 ms 12 ms 13 ms 213.242.106.133
7 34 ms 39 ms 24 ms so-4-1-0.bbr2.London1.Level3.net [4.68.128.117]

8 108 ms 111 ms 176 ms ae-0-0.bbr2.Chicago1.Level3.net [64.159.1.34]
9 112 ms 113 ms 110 ms ae-21-52.car1.Chicago1.Level3.net [4.68.101.34]

10 121 ms 126 ms 123 ms GOOGLE-INC.car1.Chicago1.Level3.net [4.79.208.18
]
11 129 ms 135 ms 140 ms 72.14.232.53
12 177 ms 204 ms 245 ms 64.233.175.26
13 208 ms 123 ms 124 ms google.com [64.233.167.99]

Long hop

It will be interesting to see a tracert from another ISP

vibe666

well after all that, it's working fine for me now. video's loading fine.

How's everyone else?

vishal

google video is acting up. also youtube has got bad again

Toto Wolfcastle

This may be the most confusing thread I have ever read, but I've been having the same problem. I don't know who the provider is, I'm in student accommodation. At first I kind of put it down to the amount of people using at one time (at that stage it was just from around 10.30 pm for a couple of hours) but now it happens all the time. It's really annoying though.

(By the way, if anything above didn't make any sense, don't laugh!! I'm not technically minded.)

purple'n'gold

vibe666 wrote: »

well after all that, it's working fine for me now. video's*loading fine.

How's everyone else?

just tried mine, still bad, it's so annoying.

vibe666

this just keeps getting weirder. not seeing any ping or traceroute difference, but streams are starting up right away almost, less than a second after the page is loaded and no buffering at all after that.

traceroute to ie.youtube.com (208.65.153.238), 30 hops max, 40 byte packets
1 bas506.cwt.esat.net (193.95.136.242) 30.542 ms 14.398 ms 17.746 ms
2 vlan500.rt501.cwt.esat.net (193.95.136.124) 148.963 ms 185.793 ms 63.220 ms
3 vlan53.rt002.cwt.esat-x.com (193.95.130.153) 51.714 ms 53.491 ms 48.912 ms
4 ge0-0.core002.cwt.esat.net (193.95.129.18) 50.055 ms 59.801 ms 57.084 ms
5 pos2-0.br002.ldn.esat.net (193.95.131.50) 78.723 ms 89.806 ms 101.617 ms
6 195.66.226.185 (195.66.226.185) 97.525 ms 73.097 ms 68.146 ms
7 g2-0-0.core02.lon01.atlas.cogentco.com (130.117.1.61) 56.039 ms 49.805 ms 57.330 ms
8 p0-0.core01.jfk02.atlas.cogentco.com (130.117.2.105) 127.979 ms 134.748 ms 152.179 ms
9 p5-0.core01.jfk01.atlas.cogentco.com (66.28.4.9) 137.849 ms 134.396 ms 137.524 ms
10 t4-2.mpd01.jfk01.atlas.cogentco.com (154.54.7.114) 129.894 ms 100.388 ms 114.270 ms
11 t4-4.mpd01.ewr03.atlas.cogentco.com (154.54.1.38) 116.090 ms 135.532 ms 153.438 ms
12 you-tube-llc.demarc.cogentco.com (38.101.84.66) 168.294 ms 143.030 ms 132.199 ms
13 * * * Request timed out.
14 * * * Request timed out.
15 64.15.116.5 (64.15.116.5) 133.986 ms 185.572 ms 188.865 ms
16 * * * Request timed out.
17 * * * Request timed out.
18 208.65.153.238 (208.65.153.238) 211.020 ms 267.099 ms 225.582 ms
Trace complete

PING ie.youtube.com (208.65.153.253): 56 data bytes
64 bytes from 208.65.153.253: icmp_seq=0 ttl=238 time=206.8 ms
64 bytes from 208.65.153.253: icmp_seq=1 ttl=238 time=199.9 ms
64 bytes from 208.65.153.253: icmp_seq=2 ttl=238 time=222.5 ms
64 bytes from 208.65.153.253: icmp_seq=3 ttl=238 time=243.9 ms
64 bytes from 208.65.153.253: icmp_seq=4 ttl=238 time=191.2 ms
--- ie.youtube.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 191.2/212.8/243.9 ms

Bohrio

Hello people

Would it be possible for people using an ISPs other than BT to post tracerts to youtube?

Markjf

BT Maynooth

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

1 16 ms 2 ms 2 ms mygateway.ar7 [192.168.1.1]
2 30 ms 12 ms 13 ms bas503.cwt.esat.net [193.95.136.239]
3 24 ms 13 ms 14 ms vlan501.rt501.cwt.esat.net [193.95.137.124]
4 25 ms 13 ms 12 ms vlan51.rt001.cwt.esat.net [193.95.130.137]
5 25 ms 12 ms 14 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
6 45 ms 31 ms 30 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
7 44 ms 30 ms 29 ms 195.66.226.185
8 48 ms 50 ms 32 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
9 113 ms 102 ms 101 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
10 117 ms 104 ms 104 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
11 115 ms 99 ms 101 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
12 115 ms 100 ms 101 ms t4-4.mpd01.ewr03.atlas.cogentco.com [154.54.1.38
]
13 178 ms 157 ms 145 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

14 * * * Request timed out.
15 * * * Request timed out.
16 180 ms 178 ms 177 ms 64.15.116.9
17 * * * Request timed out.
18 * * * Request timed out.
19 218 ms 229 ms * www.youtube.com [208.65.153.253]
20 225 ms 226 ms 230 ms www.youtube.com [208.65.153.253]

Trace complete.



Eircom Westmeath


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

1 1 ms 1 ms 1 ms 192.168.1.254
2 * * * Request timed out.
3 16 ms 58 ms 84 ms 83.71.114.129
4 30 ms 98 ms 111 ms 83.71.113.98
5 37 ms 76 ms 66 ms po1.ccr01.ams03.atlas.cogentco.com [195.69.144.1
24]
6 152 ms 218 ms 217 ms t1-1.mpd02.lon01.atlas.cogentco.com [130.117.1.1
70]
7 118 ms 116 ms 119 ms t4-1.mpd03.jfk02.atlas.cogentco.com [154.54.5.12
2]
8 116 ms 112 ms 112 ms g13-0-0.core02.jfk02.atlas.cogentco.com [154.54.
5.233]
9 118 ms 118 ms 119 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
10 114 ms 112 ms 113 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
11 112 ms 113 ms 111 ms t4-4.mpd01.ewr03.atlas.cogentco.com [154.54.1.38
]
12 113 ms 113 ms 113 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

13 * * * Request timed out.
14 * * * Request timed out.
15 195 ms 214 ms 209 ms 64.15.116.13
16 * * * Request timed out.
17 * * * Request timed out.
18 186 ms 185 ms 185 ms 208.65.153.251

Trace complete.

Did a tracert with my brother Pretty much the same but if we download a you tube video he has no problems I have to give up. We also did a speed test again and both have a download speed of 212kbs.

Bohrio

Hi that's very interesting, the only difference is that Esat's router connects to the cogent network through london (lon01.atlas.cogentco.com), so the problems could laythere, Eircom on the other hand, connects to cogent from amsterdam (ams03.atlas.cogentco.com).

It will be interesting to see tracerts from more providers...

Valentia

Aren't BT just leasing from Eircom in most places including Maynooth??

Bohrio

they lease only the service from the customer's place to the internet backhaul, from there is ISP responsibility.

Markjf

So is there any way to prove this is BT’s problem ? Or do we have to ring BT customer support ((shudder)) to get to the bottom of this.

I can tell you it’s a royal pain in the ass trying to watch a video that keeps stopping every 10 seconds to buffer.

Bohrio

Hi

No point in ringing them, whatever it is they already know, they have to know.

Markjf

They may know, in fact they could be the ones doing it (conspiracy theory) If they were packet shaping.

Valentia

Bohrio wrote: »

they lease only the service from the customer's place to the internet backhaul, from there is ISP responsability.

OK, thanks.

vibe666

Markjf wrote: »

They may know, in fact they could be the ones doing it (conspiracy theory) If they were packet shaping.

that was my first thought tbh, but it's a pretty lame way of doing it, and there's plenty of other stuff not getting throttled/shaped/borked that would make more of a difference.

I just tried a few test video's on youtube again and it's crapping out again like before, so i guess it was just a lucky strike last time.

i just logged a fault with my connection on the BT website (you can do it if you log in to view your account online). i would suggrest that everyone else does it too, to raise awareness that this is not a one off problem for one user.

i also added a link to this thread. fingers crossed someone will read it.

Markjf

If i am reading this right, a tracert from yesterday is taking a different route, still no improvement to you tube. Maybe they are working on it?


Yesterday

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

1 16 ms 2 ms 2 ms mygateway.ar7 [192.168.1.1]
2 30 ms 12 ms 13 ms bas503.cwt.esat.net [193.95.136.239]
3 24 ms 13 ms 14 ms vlan501.rt501.cwt.esat.net [193.95.137.124]
4 25 ms 13 ms 12 ms vlan51.rt001.cwt.esat.net [193.95.130.137]
5 25 ms 12 ms 14 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
6 45 ms 31 ms 30 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
7 44 ms 30 ms 29 ms 195.66.226.185
8 48 ms 50 ms 32 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
9 113 ms 102 ms 101 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
10 117 ms 104 ms 104 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
11 115 ms 99 ms 101 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
12 115 ms 100 ms 101 ms t4-4.mpd01.ewr03.atlas.cogentco.com [154.54.1.38
]
13 178 ms 157 ms 145 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

14 * * * Request timed out.
15 * * * Request timed out.
16 180 ms 178 ms 177 ms 64.15.116.9
17 * * * Request timed out.
18 * * * Request timed out.
19 218 ms 229 ms * www.youtube.com [208.65.153.253]
20 225 ms 226 ms 230 ms www.youtube.com [208.65.153.253]

Trace complete


Today

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

1 2 ms 1 ms 1 ms mygateway.ar7 [192.168.1.1]
2 34 ms 13 ms 13 ms bas503.cwt.esat.net [193.95.136.239]
3 35 ms 15 ms 27 ms vlan500.rt502.cwt.esat.net [193.95.136.125]
4 23 ms 12 ms 24 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 35 ms 69 ms 12 ms ge2-0.br003.cwt.esat.net [193.95.129.23]
6 17 ms 12 ms 13 ms 213.242.106.133
7 26 ms 26 ms 26 ms so-4-1-0.bbr2.London1.Level3.net [4.68.128.117]

8 102 ms 91 ms 91 ms as-0-0.bbr1.NewYork1.Level3.net [4.68.128.106]
9 107 ms 92 ms 90 ms ae-34-89.car4.NewYork1.Level3.net [4.68.16.134]

10 155 ms 146 ms 127 ms GOOGLE-INC.car4.NewYork1.Level3.net [4.78.166.24
6]
11 * * * Request timed out.
12 * * * Request timed out.
13 167 ms 179 ms 178 ms 64.15.116.5
14 * * * Request timed out.
15 * * * Request timed out.
16 213 ms 221 ms 214 ms www.youtube.com [208.65.153.238]

Trace complete.

Barlow07

Markjf wrote: »

If i am reading this right, a tracert from yesterday is taking a different route, still no improvement to you tube. Maybe they are working on it?


Yesterday

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

1 16 ms 2 ms 2 ms mygateway.ar7 [192.168.1.1]
2 30 ms 12 ms 13 ms bas503.cwt.esat.net [193.95.136.239]
3 24 ms 13 ms 14 ms vlan501.rt501.cwt.esat.net [193.95.137.124]
4 25 ms 13 ms 12 ms vlan51.rt001.cwt.esat.net [193.95.130.137]
5 25 ms 12 ms 14 ms ge1-0.core002.cwt.esat.net [193.95.129.2]
6 45 ms 31 ms 30 ms pos2-0.br002.ldn.esat.net [193.95.131.50]
7 44 ms 30 ms 29 ms 195.66.226.185
8 48 ms 50 ms 32 ms g2-0-0.core02.lon01.atlas.cogentco.com [130.117.
1.61]
9 113 ms 102 ms 101 ms p9-0.core02.jfk02.atlas.cogentco.com [66.28.4.25
3]
10 117 ms 104 ms 104 ms p5-0.core02.jfk01.atlas.cogentco.com [66.28.4.17
0]
11 115 ms 99 ms 101 ms t4-4.mpd01.jfk01.atlas.cogentco.com [154.54.7.11
8]
12 115 ms 100 ms 101 ms t4-4.mpd01.ewr03.atlas.cogentco.com [154.54.1.38
]
13 178 ms 157 ms 145 ms you-tube-llc.demarc.cogentco.com [38.101.84.66]

14 * * * Request timed out.
15 * * * Request timed out.
16 180 ms 178 ms 177 ms 64.15.116.9
17 * * * Request timed out.
18 * * * Request timed out.
19 218 ms 229 ms * www.youtube.com [208.65.153.253]
20 225 ms 226 ms 230 ms www.youtube.com [208.65.153.253]

Trace complete


Today

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

1 2 ms 1 ms 1 ms mygateway.ar7 [192.168.1.1]
2 34 ms 13 ms 13 ms bas503.cwt.esat.net [193.95.136.239]
3 35 ms 15 ms 27 ms vlan500.rt502.cwt.esat.net [193.95.136.125]
4 23 ms 12 ms 24 ms vlan54.rt002.cwt.esat-x.com [193.95.130.161]
5 35 ms 69 ms 12 ms ge2-0.br003.cwt.esat.net [193.95.129.23]
6 17 ms 12 ms 13 ms 213.242.106.133
7 26 ms 26 ms 26 ms so-4-1-0.bbr2.London1.Level3.net [4.68.128.117]

8 102 ms 91 ms 91 ms as-0-0.bbr1.NewYork1.Level3.net [4.68.128.106]
9 107 ms 92 ms 90 ms ae-34-89.car4.NewYork1.Level3.net [4.68.16.134]

10 155 ms 146 ms 127 ms GOOGLE-INC.car4.NewYork1.Level3.net [4.78.166.24
6]
11 * * * Request timed out.
12 * * * Request timed out.
13 167 ms 179 ms 178 ms 64.15.116.5
14 * * * Request timed out.
15 * * * Request timed out.
16 213 ms 221 ms 214 ms www.youtube.com [208.65.153.238]

Trace complete.

I would imagine BT are aware of the problem and also they have probably got customer's calling them and what not. If there is a slight improvment, then they must be working on it, but it could be more then a week before they get it fixed.

ondafly

well I've tried 4 videos on youtube, that worked on Friday in work (eircom connection). They don't work on my BT connection at all.