easy way to tell if its dns server issue is opening a command prompt and do nslookup commands, also its obvious when all net applications fail to do dns lookups properly. This is what happens when i use ntl's dns servers, there was a massive thread on this on .com and any new person entering the forums would have noticed there was a defenite dns issue but with the site down ntl have hidden the problem.
here is test result, demon dns servers ntl 600kbit and no transparent proxy.
check section 5
Speed Test Report
Broadband Speed Test - for ntl:World - 512k 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:
22ms - Normal - it's about right!
UK Server 1 (
www.demon.net):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 194.159.254.213 over a maximum of 20 hops
1 7 ms 7 ms 7 ms 10.146.151.254
2 19 ms 10 ms 9 ms 80.7.30.145
3 11 ms 8 ms 17 ms 80.1.79.197
4 13 ms 45 ms 9 ms 62.253.188.37
5 14 ms 10 ms 17 ms 62.253.185.117
6 13 ms 23 ms 15 ms 62.253.185.98
7 16 ms 16 ms 15 ms 62.253.185.74
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.
Trace complete.
UK Server 2 (
www.bbc.co.uk):
21ms - Normal - it's about right!
UK Server 3 (
www.ic24.net):
27ms - Normal - it's about right!
USA East Coast Server (
www.yahoo.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 64.58.76.176 over a maximum of 20 hops
1 8 ms 7 ms 7 ms 10.146.151.254
2 14 ms 9 ms 11 ms 80.7.30.145
3 12 ms 9 ms 9 ms 80.1.79.197
4 11 ms 52 ms 14 ms 62.253.185.37
5 11 ms 15 ms 16 ms 62.253.185.102
6 14 ms 11 ms 20 ms 62.253.187.186
7 16 ms 32 ms 17 ms 62.253.185.193
8 14 ms 15 ms 13 ms 208.175.252.89
9 19 ms 23 ms 19 ms 166.63.209.201
10 100 ms 100 ms 102 ms 206.24.226.99
11 * 206.24.238.38 reports: Destination host unreachable.
Trace complete.
USA West Coast Server (
www.lycos.com):
101ms - Fast - very fast response
European Server (
www.marcopoly.com):
35ms - Better than average - very quick response
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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:
Tracing route to 194.117.138.249 over a maximum of 20 hops
1 7 ms 15 ms 30 ms 10.146.151.254
2 9 ms 8 ms 8 ms 80.7.30.17
3 14 ms 9 ms 8 ms 80.1.79.69
4 13 ms 13 ms 14 ms 62.253.185.33
5 19 ms 15 ms 17 ms 62.253.185.238
6 65 ms 59 ms 62 ms 62.253.185.82
7 194.117.147.69 reports: Destination host unreachable.
Trace complete.
Blueyonder Team-Fortress Leage 1:
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 194.117.138.225 over a maximum of 20 hops
1 10 ms 8 ms 8 ms 10.146.151.254
2 7 ms 17 ms 8 ms 80.7.30.17
3 63 ms 10 ms 8 ms 80.1.79.69
4 28 ms 14 ms 10 ms 62.253.188.33
5 16 ms 24 ms 14 ms 62.253.185.238
6 70 ms * * 62.253.185.82
7 194.117.147.69 reports: Destination host unreachable.
Trace complete.
BarrysWorld Master Server (all games):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 213.221.174.165 over a maximum of 20 hops
1 12 ms 7 ms 10 ms 10.146.151.254
2 10 ms 8 ms 7 ms 80.7.30.17
3 8 ms 15 ms 14 ms 80.1.79.69
4 14 ms 11 ms 10 ms 62.253.185.33
5 20 ms 17 ms 51 ms 62.253.185.238
6 55 ms 118 ms 60 ms 62.253.185.82
7 43 ms 14 ms 17 ms 195.66.224.162
8 18 ms 20 ms 14 ms 213.221.179.115
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.
Trace complete.
Barrysworld Quake III Arena:
16ms -
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 - 512k service Server Download:
70KB/s (560Kb/s) - Superb - much higher than expected
Download through Transparent Cache:
70KB/s (560Kb/s) - Superb - much higher than expected
Download through alternative Cache (webcache.bt.net):
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, 50 bounced back; 0% loss (estimated)
Fantastic - no packets dropped!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 5: Transparent Cache Page Fetch Time
This test times how long your Transparent Cache takes to fetch a page from the Internet. Please note that this test is subject to many different parameters and sometimes may not be 100% accurate. This test can be used to show delays when trying to view Internet sites. The timing takes place from the moment the request for the file is sent to the moment the proxy server responds.
Average time taken to retrieve a page: 0ms - At least one of the pages requested failed to download. This may indicate problems with your Webcache. Run the test again to confirm this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test Statistics:
Information on the test
Time and Date: 03/01/2004 19:44:44
Test duration: 175 secondsIP address: [Not Disclosed]
Username: [Not disclosed]
Test Version: 2.81
Broadband Speed Test -
www.vantage.pwp.blueyonder.co.uk