[Merged] RG area problems?

confused · 18-03-2004, 01:13

i was wondering if someone would be able to decipher these results from the blueyonder speed test as i dont really know much about this stuff. i live in Reading and am using the 1MB connection. for the last week or so i have been having consistent problems browsing and downloading and it is getting worse by the day. pages either half load or dont load at all and downloads almost always freeze up for 30 second periods every 30 seconds or so. also msn and yahoo messengers keep disconnecting every few minutes. i dont know if this is a problem with dns or if it is more serious than that. i have run the speed test several times and always get the same results. i have also changed the dns in case that was the problem but it hasnt affected anything. for those of you that know the speed test, the bit at the top says:

Your estimated download speed (through transparent cache) is:

0kb/s (0kb/s)
***SERVER ERROR: Timed out receiving data from the Server***

here are the rest of the results:

Section 1: General Ping Results
A Ping test is the time taken for a server to reply to a request
ntl:World Server:
8ms - Excellent - better than expected
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 10 ms 9 ms 10.152.143.254
2 6 ms 8 ms 17 ms 62.253.122.13
3 10 ms 7 ms 8 ms 62.253.121.1
4 8 ms 7 ms 22 ms 62.253.184.113
5 * * * Request timed out.
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.
Trace complete.

UK Server 2 (www.bbc.co.uk):
10ms - Excellent - better than expected
UK Server 3 (www.ic24.net):
12ms - Excellent - better than expected
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 6 ms 8 ms 9 ms 10.152.143.254
2 8 ms 11 ms 7 ms 62.253.122.13
3 9 ms 7 ms 8 ms 62.253.121.1
4 6 ms 9 ms 7 ms 62.253.184.113
5 8 ms 9 ms 8 ms 166.63.161.229
6 8 ms 11 ms 10 ms 166.63.209.205
7 79 ms 80 ms 82 ms 195.2.1.3
8 83 ms 85 ms 84 ms 195.2.3.1
9 84 ms 84 ms 85 ms 206.24.238.17
10 206.24.238.38 reports: Destination host unreachable.
Trace complete.

USA West Coast Server (www.lycos.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 209.202.192.26 over a maximum of 20 hops
1 6 ms 7 ms 8 ms 10.152.143.254
2 29 ms 9 ms 9 ms 62.253.122.13
3 10 ms 8 ms 8 ms 62.253.121.1
4 10 ms 7 ms 12 ms 62.253.184.113
5 8 ms 9 ms 7 ms 166.63.161.229
6 9 ms 9 ms 9 ms 166.63.209.205
7 82 ms 78 ms 81 ms 195.2.1.3
8 83 ms 84 ms 83 ms 195.2.3.1
9 84 ms 83 ms 83 ms 206.24.238.17
10 98 ms 95 ms 96 ms 208.172.50.61
11 93 ms 93 ms 96 ms 208.172.51.222
12 96 ms 97 ms 94 ms 64.14.70.2
13 94 ms 93 ms 96 ms 64.14.70.3
14 97 ms 96 ms 96 ms 209.67.240.218
15 95 ms 94 ms 108 ms 209.202.192.26
Trace complete.

European Server (www.marcopoly.com):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 195.44.63.5 over a maximum of 20 hops
1 10 ms 9 ms 6 ms 10.152.143.254
2 11 ms 8 ms 8 ms 62.253.122.141
3 19 ms 8 ms 11 ms 62.253.121.129
4 7 ms 8 ms 7 ms 62.253.184.117
5 8 ms 7 ms 12 ms 62.253.185.201
6 9 ms 10 ms 9 ms 62.253.185.86
7 9 ms 11 ms 11 ms 195.66.226.20
8 9 ms 11 ms 10 ms 194.177.181.250
9 10 ms 11 ms 9 ms 195.44.199.209
10 11 ms 11 ms 10 ms 195.44.192.9
11 * * * Request timed out.
12 * * * Request timed out.
13 * 12 ms 11 ms 195.44.63.5
Trace complete.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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 8 ms 7 ms 10.152.143.254
2 10 ms 7 ms 7 ms 62.253.122.13
3 7 ms 9 ms 8 ms 62.253.121.1
4 9 ms 30 ms 7 ms 62.253.184.113
5 12 ms 28 ms 7 ms 213.105.172.130
6 8 ms 29 ms 13 ms 213.105.172.5
7 9 ms 11 ms 11 ms 62.253.185.78
8 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 6 ms 9 ms 6 ms 10.152.143.254
2 7 ms 7 ms 23 ms 62.253.122.141
3 8 ms 7 ms 9 ms 62.253.121.129
4 21 ms 9 ms 8 ms 62.253.184.117
5 9 ms 10 ms 8 ms 62.253.185.201
6 8 ms 7 ms 12 ms 213.105.172.77
7 8 ms 9 ms 10 ms 62.253.185.82
8 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 7 ms 19 ms 9 ms 10.152.143.254
2 8 ms 7 ms 7 ms 62.253.122.13
3 11 ms 9 ms 8 ms 62.253.121.1
4 7 ms 10 ms 7 ms 62.253.184.113
5 9 ms 7 ms 10 ms 213.105.172.130
6 8 ms 9 ms 10 ms 213.105.172.5
7 11 ms 14 ms 9 ms 62.253.185.78
8 11 ms 13 ms 11 ms 212.250.14.14
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.

Japanese Ping Server (VERY long distance!):
0ms - *** PING timed out ***
Tracert to specified location:
Tracing route to 211.13.208.202 over a maximum of 20 hops
1 7 ms 30 ms 9 ms 10.152.143.254
2 21 ms 7 ms 8 ms 62.253.122.141
3 7 ms 7 ms 8 ms 62.253.121.129
4 7 ms 9 ms 10 ms 62.253.184.117
5 9 ms 9 ms 10 ms 62.253.185.201
6 8 ms 10 ms 27 ms 213.105.172.77
7 9 ms 9 ms 11 ms 62.253.185.82
8 85 ms 86 ms 83 ms 195.66.224.105
9 84 ms 87 ms 84 ms 64.200.87.153
10 84 ms 84 ms 84 ms 64.200.240.46
11 145 ms 150 ms 143 ms 64.200.240.29
12 149 ms 142 ms 144 ms 64.200.143.66
13 169 ms 170 ms 169 ms 64.200.139.110
14 167 ms 162 ms 160 ms 203.181.106.101
15 298 ms 300 ms 294 ms 203.181.100.21
16 268 ms 281 ms 266 ms 203.181.96.118
17 282 ms 283 ms 285 ms 202.239.171.142
18 266 ms 265 ms 274 ms 210.155.132.105
19 275 ms 303 ms 262 ms 210.155.139.8
20 * * * Request timed out.
Trace complete.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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:
0KB/s (0Kb/s) - **** SERVER ERROR: Valid name, no data record of requested type****
Download through Transparent Cache:
0KB/s (0Kb/s) - **** SERVER ERROR: Timed out receiving data from the Server****
Download through alternative Cache (webcache.blueyonder.co.uk):
0KB/s (0Kb/s) - **** SERVER ERROR: Valid name, no data record of requested type****
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Section 6: Network Connection Settings
The settings shown below are the settings that the system is currently using for connecting to the Internet
Receive Window: Default
Default TTL: Default
Windows IP Configuration
Host Name . . . . . . . . . . . . : ***
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-10-DC-4D-B6-4B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 81.107.91.***
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 81.107.91.***
DHCP Server . . . . . . . . . . . : 62.253.96.21
DNS Servers . . . . . . . . . . . : 194.168.8.100
194.168.4.100
Lease Obtained. . . . . . . . . . : 17 March 2004 23:16:13
Lease Expires . . . . . . . . . . : 18 March 2004 17:19:15

Your Webcache: <html><head><title>Server Application Error</title></head>
<body><h1>Server Application Error</h1>The server has reached the maximum recovery limit for the application during the processing of your request. Please contact the server administrator for assistance.</body></html>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Test Statistics:
Information on the test
Time and Date: 17/03/2004 23:52:04
Test duration: 293 secondsIP address: 81.107.91.***
Username: [Not disclosed]
Test Version: 2.81
Broadband Speed Test - www.vantage.pwp.blueyonder.co.uk

any help on what the problem might be would be very much appreciated!

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 ?

zovat · 20-03-2004, 00:34

ok - off to bed now - See if it is better in the morning.....

2old4this · 20-03-2004, 04:17

I have come from work and it very bad

markmarkymark · 20-03-2004, 05:27

hi

I'm in reading area - its terrible now at 6am ..

Mark

threadbare · 20-03-2004, 08:41

not sure how that test can say you have poor packet loss and good download speed. try downlaoding a file from www.tucows.com using one of the uk mirrors. if that is gogod then it is likely the problemis just slow browsing ie proxies etc

mattyduk · 20-03-2004, 09:11

Yeah,

dead slow in Basingstoke at 9:00am. Haven't got time to ring NTL "technical support", so hopefully it will be fixed when I get back this evening.

No sign of any problems on the wonder ful ntl status page.

chirpy · 20-03-2004, 09:36

I'm also in Reading and getting a great deal of packet loss. Rang support and they said they could not see a problem and that no-one else had reported anything

I'm at a loss as to what to do next.

Neil · 20-03-2004, 09:39

Quote:

Originally Posted by mattyduk

Yeah,

dead slow in Basingstoke at 9:00am. Haven't got time to ring NTL "technical support", so hopefully it will be fixed when I get back this evening.

No sign of any problems on the wonder ful ntl status page.

Quote:

Originally Posted by chirpy

I'm also in Reading and getting a great deal of packet loss. Rang support and they said they could not see a problem and that no-one else had reported anything

I'm at a loss as to what to do next.

You people have to ring ntl to stand any chance of them acknowledging the problem.

Welcome to nthw btw folks. :pp

chirpy · 20-03-2004, 09:42

Quote:

You people have to ring ntl to stand any chance of them acknowledging the problem.

I did, though, and they said that they couldn't see a problem so there was nothing they could do.

markmarkymark · 20-03-2004, 09:44

I have rung ... they so no problem at all....

this is quite simply the worse performance from the 1Mbit connection I have ever had. I am only able to even post by using VPN - and even then the connection between NTL and VPN is dodgy to say the least ....

Its not just slowm it more or less unusable now .....

Please everyone, DO phone as Neil says

MArk

Neil · 20-03-2004, 09:45

Quote:

Originally Posted by chirpy

I did, though, and they said that they couldn't see a problem so there was nothing they could do.

I know you did Chirpy, I was just highlighting the issue of how important it is to ringntl about these matters.

For example-if 10 peeps posted here saying they had spoken to <insert name> at Tech Support, then you phoned up & they said no one had reported it, you could prove they were bull$hitting you.

markmarkymark · 20-03-2004, 09:48

this is my speed result :

Sat, 20 Mar 2004 09:48:01 UTC
1st 128K took 891 ms = 147107 Bytes/sec = approx 1224 kbits/sec
2nd 128K took 1078 ms = 121588 Bytes/sec = approx 1012 kbits/sec
3rd 128K took 1062 ms = 123420 Bytes/sec = approx 1027 kbits/sec
4th 128K took 1078 ms = 121588 Bytes/sec = approx 1012 kbits/sec

There is no problem there

- its getting anything to load - DNS issue ?

th'engineer · 20-03-2004, 09:49

Quote:

Originally Posted by markmarkymark

this is my speed result :

Sat, 20 Mar 2004 09:48:01 UTC
1st 128K took 891 ms = 147107 Bytes/sec = approx 1224 kbits/sec
2nd 128K took 1078 ms = 121588 Bytes/sec = approx 1012 kbits/sec
3rd 128K took 1062 ms = 123420 Bytes/sec = approx 1027 kbits/sec
4th 128K took 1078 ms = 121588 Bytes/sec = approx 1012 kbits/sec

There is no problem there

- its getting anything to load - DNS issue ?

Use that contacts at NTL info to raise it to another level

chirpy · 20-03-2004, 09:51

Hmmm, have a b*tch on nthellworld and a few minutes later (I know kiss of death) it seems to have improved.