Cable Forum - View Single Post - Speed Issue

KevAmiga · 15-03-2006, 11:03

Right... im away from my desk for a while but i have been emailing back and forth, ill paste some stuff here for others to look at and ill check back later.

Some traceroutes from Bolch :

>> 5 15 ms 15 ms 15 ms 212.187.137.1
>> 6 15 ms 15 ms 16 ms so-6-1-0.mp2.manchesteruk1.level3.net
>>[4.68.113.118]
>> 7 105 ms 99 ms 97 ms as-0-0.bbr1.newyork1.level3.net
>>[4.68.128.106]
>> 8 98 ms 96 ms 97 ms ge-7-0-0-54.gar3.newyork1.level3.net
>>[4.68.97.100]
>> 9 88 ms 86 ms 90 ms ewr-brdr-02.inet.qwest.net [205.171.1.97]
>>10 86 ms 114 ms 143 ms ewr-core-01.inet.qwest.net [205.171.17.125]
>>11 129 ms 128 ms 127 ms tpa-core-01.inet.qwest.net [67.14.3.2]
>>12 128 ms 129 ms 128 ms fl1-edge-03.inet.qwest.net [205.171.27.42]
>>13 126 ms 126 ms 125 ms 65.115.128.14
>>14 126 ms 126 ms 126 ms 216.87.0.229
>>15 128 ms 127 ms 126 ms w5.fredlulu.com [64.239.76.225]

.........

>> 7 24 ms 25 ms 26 ms telc-ic-1-as0-0.inet.ntl.com [62.253.188.121]
>> 8 25 ms 49 ms 25 ms ldn-b2-link.telia.net [213.248.100.37]
>> 9 41 ms 25 ms 25 ms ldn-bb2-pos0-3-0.telia.net [213.248.74.9]
>>10 95 ms 94 ms 96 ms nyk-bb2-pos0-2-0.telia.net [213.248.65.94]
>>11 99 ms 100 ms 107 ms ash-bb1-pos7-0-0-0.telia.net
>>[213.248.80.138]
>>12 115 ms 121 ms 116 ms atl-bb1-pos5-0-0.telia.net [213.248.80.142]
>>13 123 ms * 122 ms uns-llc-112059-atl-bb1.c.telia.net
>>[213.248.91.2]
>>14 117 ms 115 ms 115 ms nntp1.usenetserver.com [208.49.80.60]

And a ping ..

>Reply from 208.49.80.60: bytes=32 time=123ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=114ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=114ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=115ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=126ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=117ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=115ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=114ms TTL=52
>Request timed out.
>Reply from 208.49.80.60: bytes=32 time=114ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=115ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=115ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=125ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=116ms TTL=52
>Reply from 208.49.80.60: bytes=32 time=115ms TTL=52

I pinged the same server from here :

>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Request timed out.
>Reply from 208.49.80.60: bytes=32 time=110ms TTL=47
>Reply from 208.49.80.60: bytes=32 time=111ms TTL=47

Odd... seems to be a traffic-issue... ill take another look later.

15-03-2006, 11:03	#54
KevAmiga Inactive Join Date: Jul 2004 Location: Swansea, South Wales Age: 43 Services: TiVo, V+, SH2. Phone, Mobile. Posts: 313	Re: Speed Issue - Nothing left to do but leave NTL? Right... im away from my desk for a while but i have been emailing back and forth, ill paste some stuff here for others to look at and ill check back later. Some traceroutes from Bolch : >> 5 15 ms 15 ms 15 ms 212.187.137.1 >> 6 15 ms 15 ms 16 ms so-6-1-0.mp2.manchesteruk1.level3.net >>[4.68.113.118] >> 7 105 ms 99 ms 97 ms as-0-0.bbr1.newyork1.level3.net >>[4.68.128.106] >> 8 98 ms 96 ms 97 ms ge-7-0-0-54.gar3.newyork1.level3.net >>[4.68.97.100] >> 9 88 ms 86 ms 90 ms ewr-brdr-02.inet.qwest.net [205.171.1.97] >>10 86 ms 114 ms 143 ms ewr-core-01.inet.qwest.net [205.171.17.125] >>11 129 ms 128 ms 127 ms tpa-core-01.inet.qwest.net [67.14.3.2] >>12 128 ms 129 ms 128 ms fl1-edge-03.inet.qwest.net [205.171.27.42] >>13 126 ms 126 ms 125 ms 65.115.128.14 >>14 126 ms 126 ms 126 ms 216.87.0.229 >>15 128 ms 127 ms 126 ms w5.fredlulu.com [64.239.76.225] ......... >> 7 24 ms 25 ms 26 ms telc-ic-1-as0-0.inet.ntl.com [62.253.188.121] >> 8 25 ms 49 ms 25 ms ldn-b2-link.telia.net [213.248.100.37] >> 9 41 ms 25 ms 25 ms ldn-bb2-pos0-3-0.telia.net [213.248.74.9] >>10 95 ms 94 ms 96 ms nyk-bb2-pos0-2-0.telia.net [213.248.65.94] >>11 99 ms 100 ms 107 ms ash-bb1-pos7-0-0-0.telia.net >>[213.248.80.138] >>12 115 ms 121 ms 116 ms atl-bb1-pos5-0-0.telia.net [213.248.80.142] >>13 123 ms * 122 ms uns-llc-112059-atl-bb1.c.telia.net >>[213.248.91.2] >>14 117 ms 115 ms 115 ms nntp1.usenetserver.com [208.49.80.60] And a ping .. >Reply from 208.49.80.60: bytes=32 time=123ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=114ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=114ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=115ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=126ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=117ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=115ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=114ms TTL=52 >Request timed out. >Reply from 208.49.80.60: bytes=32 time=114ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=115ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=115ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=125ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=116ms TTL=52 >Reply from 208.49.80.60: bytes=32 time=115ms TTL=52 I pinged the same server from here : >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Request timed out. >Reply from 208.49.80.60: bytes=32 time=110ms TTL=47 >Reply from 208.49.80.60: bytes=32 time=111ms TTL=47 Odd... seems to be a traffic-issue... ill take another look later.