Neuradni T-2 forum

Imam povezavo 20/20, ampak namesto, da bi za video porabil par sekund, se mi večino časa nalaga, ko da bi imel ISDN. ( Nazadnje sem za 3 minutni video, ki ni HD čakal 20 min, da ga je naložilo.)
Prej sem pingal youtube in rezultat je takšen:

Pinging youtube.com [74.125.67.100] with 32 bytes of data:
Reply from 74.125.67.100: bytes=32 time=131ms TTL=50
Reply from 74.125.67.100: bytes=32 time=127ms TTL=50
Reply from 74.125.67.100: bytes=32 time=125ms TTL=50
Reply from 74.125.67.100: bytes=32 time=125ms TTL=50

Ping statistics for 74.125.67.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 131ms, Average = 127ms

Pa opažam, da je pri google.com isto, seveda ni problemov z nalaganjem, I think:

Pinging google.si [74.125.91.104] with 32 bytes of data:
Reply from 74.125.91.104: bytes=32 time=135ms TTL=49
Reply from 74.125.91.104: bytes=32 time=135ms TTL=49
Reply from 74.125.91.104: bytes=32 time=135ms TTL=49
Reply from 74.125.91.104: bytes=32 time=135ms TTL=49

Ping statistics for 74.125.91.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 135ms, Maximum = 135ms, Average = 135ms


Če dam pa za primer slovensko spletno stran; vijavaja.com, je pa kul:

Pinging vijavaja.com [91.185.193.95] with 32 bytes of data:
Reply from 91.185.193.95: bytes=32 time=1ms TTL=58
Reply from 91.185.193.95: bytes=32 time=1ms TTL=58
Reply from 91.185.193.95: bytes=32 time=1ms TTL=58
Reply from 91.185.193.95: bytes=32 time=1ms TTL=58

Ping statistics for 91.185.193.95:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

--

Zanima me kaj je problem in kako bi se to zadevo rešil. Je kriva povezava? Računalnik? ( nikar ne reč, da so torrenti, ker sem osebno poskrbel, da client ni prižgan na nobenem računalniku v hiši.)

isto stanje imam jaz na kabelskem internetu, torej kaj misliš kje je težava?

Ping do strežnikov onkraj luže bo vedno 100+ ms...

Isto je na siol optiki.

Malkec napisal/-a:Ping do strežnikov onkraj luže bo vedno 100+ ms...

Torej to pomeni, da se obsojen na počasen youtube, ne glede na hitrost, ki jo imam?

Ping načeloma nima veze z delovanjem (vsaj za youtube). Daj kopiraj kakšen url od youtube ki ti dela počasi, da sprobamo. Meni v tem trenutku dela bp, tudi HQ posnetki.

Evo recimo tale:

http://www.youtube.com/watch?v=H613IQiD ... e=featured

Predvaja 2 sekundi, ptem zopet loada 8s. Testirano iz Siola.

podobno na trieri.
na T-2 mi je celo deloval koliko toliko normalno.

Deluje normalno, tudi HQ.

Zadnje čas zgleda da ima youtube probleme. Odvisno pa je dostikrat iz katerega njihovega strežnika ti video strema, vsa zadeva je itak v "oblaku", tako da je težko določit strežnik in kakšna je njegova obremenjenost na drugi strani.
Drugače pa ta video na t2 pred minuto delal tekoče.

na to sem že opozarjal (mislim na yt)

Ja samo T-2 tukaj ne more nič naredit, ker problem ni v T-2.

Sprobano iz strani siola. Deluje normalno tudi hq.

C:\>tracert youtube.com

Sledenje smeri do youtube.com [74.125.127.100]
prek največ 30 preskokov:

1 1 ms 2 ms 1 ms 192.168.1.1
2 * 19 ms 20 ms 89-212-0-1.gw.t-2.net [89.212.0.1]
3 18 ms 18 ms 19 ms 84-255-250-161.core.t-2.net [84.255.250.161]
4 19 ms 20 ms 19 ms 84-255-250-9.core.t-2.net [84.255.250.9]
5 21 ms 21 ms 22 ms 84-255-250-42.core.t-2.net [84.255.250.42]
6 25 ms 25 ms 25 ms win-b2-link.telia.net [213.248.79.229]
7 106 ms 54 ms 54 ms hbg-bb2-link.telia.net [80.91.252.82]
8 68 ms 69 ms 139 ms ldn-bb2-link.telia.net [80.239.147.185]
9 180 ms 143 ms 225 ms ash-bb1-link.telia.net [213.248.65.210]
10 144 ms 143 ms 143 ms level3-ic-130870-ash-bb1.c.telia.net [213.248.89.178]
11 156 ms 144 ms 144 ms vlan99.csw4.Washington1.Level3.net [4.68.17.254]
12 144 ms 145 ms 168 ms ae-72-72.ebr2.Washington1.Level3.net [4.69.134.149]
13 155 ms 154 ms 163 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69]
14 162 ms 161 ms 161 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
15 188 ms 193 ms 196 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61]
16 230 ms 219 ms 217 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53]
17 218 ms 219 ms 217 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34]
18 210 ms 210 ms 211 ms GOOGLE-INC.car1.Seattle1.Level3.net [4.79.104.74]
19 223 ms 225 ms 224 ms 209.85.249.34
20 230 ms 213 ms 213 ms 209.85.250.126
21 232 ms 231 ms 231 ms 216.239.48.34
22 235 ms 231 ms 231 ms 209.85.250.146
23 226 ms 230 ms 223 ms 64.233.174.101
24 222 ms 216 ms 216 ms 216.239.46.30
25 224 ms 225 ms 224 ms pz-in-f100.google.com [74.125.127.100]