Cable Forum - View Single Post

zovat · 20-03-2004, 00:20

Running REally slow ATM - test results below - I am on the 1M service..

Speed Test Report

Broadband Speed Test - for ntl:World - 1Mb service
By Daniel Elwell - dannyelwell2001@msn.com
Get this test from http://www.vantage.pwp.blueyonder.co.uk

*** THIS TEST IS NOT OWNED OR PAID FOR BY BLUEYONDER ***
If you like this Speed Test, please make a donation to help me
meet the development costs. No ISPs pay me to maintain this test.
More information: http://www.vantage.pwp.blueyonder.co.uk/donate.htm

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
These results are only a snapshot of this particular moment. They are dependant
on any other Internet use on this computer and any delays
on the Internet. To improve accuracy, run the test several times.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Section 1: General Ping Results
A Ping test is the time taken for a server to reply to a request

ntl:World Server:
9ms - Excellent - better than expected

UK Server 1 (www.demon.net):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

UK Server 2 (www.bbc.co.uk):
22ms - Normal - it's about right!

UK Server 3 (www.ic24.net):
17ms - Excellent - better than expected

USA East Coast Server (www.yahoo.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

USA West Coast Server (www.lycos.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

European Server (www.marcopoly.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Section 2: Custom Server Ping Results
These results are to four user-definable servers.

Blueyonder Counter-Strike 1:
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

Blueyonder Team-Fortress Leage 1:
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

BarrysWorld Master Server (all games):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

Japanese Ping Server (VERY long distance!):
0ms - *** PING timed out ***
Tracert to specified location:
Tracert was cancelled

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Section 3: Download Speed Results
Three downloads are tested; one from one of your ISPs servers, one through your Transparent Cache and one through an alterntive cache. This will give you an idea of how capable your connection is. Note: You should take the highest download speed into account.

ntl:World - 1Mb service Server Download:
121KB/s (968Kb/s) - Perfect - running at full speed!

Download through Transparent Cache:
23KB/s (184Kb/s) - Dismal - this is extremely poor

Download through alternative Cache (webcache.blueyonder.co.uk):
0KB/s (0Kb/s) - **** SERVER ERROR: Unexpected error from Server****

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Section 4: Packet Loss
50 Ping Requests are sent to your server. The packet loss is measured by how many of the packets don't bounce back to the client. High packet loss may slow down your connection.

50 packets were sent, 22 bounced back; 56% loss (estimated)
Very Poor - more than half of your packets are lost
----

Your Webcache: 62.253.96.40

************************************************** ****

*** PLEASE IGNORE THE PACKET LOSS TEST ***

Blueyonder have recently put their web server behind a firewall, meaning that when the Speed Test attempts to ping the server none of the packets are returned, therefore the Speed Test thinks you have a problem with your connection.

************************************************** ****

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Test Statistics:
Information on the test

Time and Date: 20/03/2004 00:04:35
Test duration: 142 seconds
IP address: 192.168.1.100
Username: [Not disclosed]
Test Version: 2.81

Ping to yahoo:

C:\>ping www.yahoo.co.uk

Pinging www.euro.yahoo.akadns.net [217.12.3.11] with 32 bytes of data:

Reply from 217.12.3.11: bytes=32 time=11ms TTL=245
Reply from 217.12.3.11: bytes=32 time=24ms TTL=245
Request timed out.
Reply from 217.12.3.11: bytes=32 time=13ms TTL=245

Ping statistics for 217.12.3.11:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 24ms, Average = 16ms

tracert to yahoo

C:\>tracert www.yahoo.co.uk

Tracing route to www.euro.yahoo.akadns.net [217.12.3.11]
over a maximum of 30 hops:

1 11 ms 27 ms 9 ms 10.152.103.254
2 12 ms 9 ms 9 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145]
3 10 ms 11 ms 11 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121.129]
4 11 ms 10 ms 9 ms win-bb-b-so-320-0.inet.ntl.com [62.253.184.117]
5 12 ms 15 ms 12 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201]
6 * 11 ms 18 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86]
7 13 ms * 52 ms linx2-g50.lng.yahoo.com [195.66.226.129]
8 13 ms 11 ms 12 ms bas2.3.ukl.yahoo.com [217.12.0.25]
9 * * * Request timed out.
10 * 10 ms 12 ms www2.vip.ukl.yahoo.com [217.12.3.11]

Ping to nthellworld.com timed out...

tracert to nthellworld.com below - kinda speaks for itself...
C:\>tracert www.nthellworld.com

Tracing route to www.nthellworld.com [62.253.167.55]
over a maximum of 30 hops:

1 10 ms 26 ms 11 ms 10.152.103.254
2 8 ms 22 ms 10 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145]

3 10 ms 9 ms 9 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121.
129]
4 10 ms 33 ms 29 ms win-bb-b-so-320-0.inet.ntl.com [62.253.184.117]

5 11 ms 11 ms 9 ms win-dc-b-v902.inet.ntl.com [62.253.187.226]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

any ideas ?

20-03-2004, 00:20	#2
zovat Inactive Join Date: Oct 2003 Location: Bracknell Age: 56 Services: NTL Telephone 3M Broadband - CM Sky TV Posts: 1,246	Slow connection in RG area - again ? Running REally slow ATM - test results below - I am on the 1M service.. Speed Test Report Broadband Speed Test - for ntl:World - 1Mb service By Daniel Elwell - dannyelwell2001@msn.com Get this test from http://www.vantage.pwp.blueyonder.co.uk * THIS TEST IS NOT OWNED OR PAID FOR BY BLUEYONDER * If you like this Speed Test, please make a donation to help me meet the development costs. No ISPs pay me to maintain this test. More information: http://www.vantage.pwp.blueyonder.co.uk/donate.htm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These results are only a snapshot of this particular moment. They are dependant on any other Internet use on this computer and any delays on the Internet. To improve accuracy, run the test several times. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 1: General Ping Results A Ping test is the time taken for a server to reply to a request ntl:World Server: 9ms - Excellent - better than expected UK Server 1 (www.demon.net): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled UK Server 2 (www.bbc.co.uk): 22ms - Normal - it's about right! UK Server 3 (www.ic24.net): 17ms - Excellent - better than expected USA East Coast Server (www.yahoo.com): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled USA West Coast Server (www.lycos.com): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled European Server (www.marcopoly.com): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 2: Custom Server Ping Results These results are to four user-definable servers. Blueyonder Counter-Strike 1: 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled Blueyonder Team-Fortress Leage 1: 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled BarrysWorld Master Server (all games): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled Japanese Ping Server (VERY long distance!): 0ms - * PING timed out * Tracert to specified location: Tracert was cancelled ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 3: Download Speed Results Three downloads are tested; one from one of your ISPs servers, one through your Transparent Cache and one through an alterntive cache. This will give you an idea of how capable your connection is. Note: You should take the highest download speed into account. ntl:World - 1Mb service Server Download: 121KB/s (968Kb/s) - Perfect - running at full speed! Download through Transparent Cache: 23KB/s (184Kb/s) - Dismal - this is extremely poor Download through alternative Cache (webcache.blueyonder.co.uk): 0KB/s (0Kb/s) - ** SERVER ERROR: Unexpected error from Server ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Section 4: Packet Loss 50 Ping Requests are sent to your server. The packet loss is measured by how many of the packets don't bounce back to the client. High packet loss may slow down your connection. 50 packets were sent, 22 bounced back; 56% loss (estimated) Very Poor - more than half of your packets are lost ---- Your Webcache: 62.253.96.40 ********************************************** * PLEASE IGNORE THE PACKET LOSS TEST * Blueyonder have recently put their web server behind a firewall, meaning that when the Speed Test attempts to ping the server none of the packets are returned, therefore the Speed Test thinks you have a problem with your connection. ********************************************** ** ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Test Statistics: Information on the test Time and Date: 20/03/2004 00:04:35 Test duration: 142 seconds IP address: 192.168.1.100 Username: [Not disclosed] Test Version: 2.81 Ping to yahoo: C:\>ping www.yahoo.co.uk Pinging www.euro.yahoo.akadns.net [217.12.3.11] with 32 bytes of data: Reply from 217.12.3.11: bytes=32 time=11ms TTL=245 Reply from 217.12.3.11: bytes=32 time=24ms TTL=245 Request timed out. Reply from 217.12.3.11: bytes=32 time=13ms TTL=245 Ping statistics for 217.12.3.11: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 24ms, Average = 16ms tracert to yahoo C:\>tracert www.yahoo.co.uk Tracing route to www.euro.yahoo.akadns.net [217.12.3.11] over a maximum of 30 hops: 1 11 ms 27 ms 9 ms 10.152.103.254 2 12 ms 9 ms 9 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145] 3 10 ms 11 ms 11 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121.129] 4 11 ms 10 ms 9 ms win-bb-b-so-320-0.inet.ntl.com [62.253.184.117] 5 12 ms 15 ms 12 ms pop-bb-a-so-000-0.inet.ntl.com [62.253.185.201] 6 * 11 ms 18 ms tele-ic-2-so-000-0.inet.ntl.com [62.253.185.86] 7 13 ms * 52 ms linx2-g50.lng.yahoo.com [195.66.226.129] 8 13 ms 11 ms 12 ms bas2.3.ukl.yahoo.com [217.12.0.25] 9 * * * Request timed out. 10 * 10 ms 12 ms www2.vip.ukl.yahoo.com [217.12.3.11] Ping to nthellworld.com timed out... tracert to nthellworld.com below - kinda speaks for itself... C:\>tracert www.nthellworld.com Tracing route to www.nthellworld.com [62.253.167.55] over a maximum of 30 hops: 1 10 ms 26 ms 11 ms 10.152.103.254 2 8 ms 22 ms 10 ms rdng-t2cam1-b-ge95.inet.ntl.com [62.253.122.145] 3 10 ms 9 ms 9 ms winn-t2core-b-ge-wan61.inet.ntl.com [62.253.121. 129] 4 10 ms 33 ms 29 ms win-bb-b-so-320-0.inet.ntl.com [62.253.184.117] 5 11 ms 11 ms 9 ms win-dc-b-v902.inet.ntl.com [62.253.187.226] 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. any ideas ?