Quote:
|
Originally Posted by jss
do i have the t2core issue?
|
Seems we both do:
Tracing route to zip.members.easynews.com [140.99.99.100]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.*.*
2 16 ms 9 ms 10 ms 10.145.*.*
3 9 ms 9 ms 10 ms nott-t2cam1-a-ge-wan53-137.inet.ntl.com [80.4.46
.65]
4 129 ms 148 ms 127 ms not-t2core-a-ge-wan61.inet.ntl.com [80.1.79.57]
5 120 ms 121 ms 148 ms lee-bb-a-so-300-0.inet.ntl.com [62.253.185.33]
6 127 ms 125 ms 124 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
7 128 ms 124 ms 131 ms pop-bb-a-ae0-0.inet.ntl.com [213.105.172.78]
8 125 ms 132 ms 127 ms so-7-0.hsa2.London1.Level3.net [212.113.14.129]
9 129 ms * 108 ms so-4-0-0.mp1.London1.Level3.net [212.187.131.121
]
10 107 ms 106 ms 113 ms so-1-0-0.mp1.London2.Level3.net [212.187.128.49]
11 179 ms 178 ms 180 ms so-1-0-0.bbr1.Washington1.Level3.net [212.187.12
8.138]
12 234 ms 253 ms 232 ms so-0-1-0.mp2.Phoenix1.Level3.net [64.159.1.122]
13 233 ms 231 ms 230 ms ge-11-0.hsa1.Phoenix1.Level3.net [64.159.3.110]
14 238 ms 261 ms 242 ms ge2-2-1000M.4iron.phx1.puregig.net [63.214.160.1
54]
15 231 ms 245 ms 238 ms ge2-4-1000m.sw1.core.phx1.puregig.net [140.99.96
.45]
16 230 ms 234 ms 236 ms zip.members.easynews.com [140.99.99.100]
Also from Robin's Test:
Thu, 18 Dec 2003 18:12:43 UTC
1st 128K took 1781 ms = 73595 Bytes/sec = approx 612 kbits/sec
2nd 128K took 1844 ms = 71080 Bytes/sec = approx 591 kbits/sec
3rd 128K took 2844 ms = 46087 Bytes/sec = approx 383 kbits/sec
4th 128K took 22453 ms = 5838 Bytes/sec = approx 49 kbits/sec
thats normally constant around the top 600 mark