Re: [Merged] BB Speed Upgrades
 

Mine states that mine was upgraded in August.....1meg customer with a new samsung box and still on 1meg.....

OT i know but whats CAK Callback Connection Failure all about?? its in the event log on the box, never had this with the pace ones

Re: [Merged] BB Speed Upgrades
 

Mine states that I was upgraded in August as well.....do these figures look like upgraded speeds to anyone? :confused:

Re: [Merged] BB Speed Upgrades
 

Ya tried that myself, just got off the phone with my friend down the road, he's on a SACM and his isn't showing any speed upgrade yet either, I'll prob leave it till i get up for work tomorrow if its not up by then i think it may be a "big turn on" for the set top boxes, any NTL techie people shed any light if this is the case or not? :)

Re: [Merged] BB Speed Upgrades
 

the 4th one does... have a look on the modem config page (http://192.168.100.1) and see what speed it is showing there.

Re: [Merged] BB Speed Upgrades
 

'Page cannot be displayed'......I'm on stb btw

Re: [Merged] BB Speed Upgrades
 

ah that would be why then... only works with SACMs ;)

Re: [Merged] BB Speed Upgrades
 

:cry: Thought as much :D

Re: [Merged] BB Speed Upgrades
 

im on a 600k service through a STB and am getting about 702k

Re: [Merged] BB Speed Upgrades
 

It also says that I'm already upgraded, I'm not though (stoke). I've rebooted my SACM and left it off for an hour also, it's status page still say 6000bps download though:(

Re: [Merged] BB Speed Upgrades
 

It's good to know other people are affected. Hopefully NTL will get round to us soon.

Re: [Merged] BB Speed Upgrades
 

Well according to the Postcode checker I'm supposed to have been upgraded today.

Does this look like I've been upgraded?

Wed, 11 Aug 2004 22:57:01 UTC
1st 128K took 4230 ms = 30986 Bytes/sec = approx 258 kbits/sec
2nd 128K took 6540 ms = 20042 Bytes/sec = approx 167 kbits/sec
3rd 128K took 6310 ms = 20772 Bytes/sec = approx 173 kbits/sec
4th 128K took 4840 ms = 27081 Bytes/sec = approx 225 kbits/sec

Wed, 11 Aug 2004 22:58:07 UTC
1st 128K took 12690 ms = 10329 Bytes/sec = approx 86 kbits/sec
2nd 128K took 3790 ms = 34584 Bytes/sec = approx 288 kbits/sec
3rd 128K took 9390 ms = 13959 Bytes/sec = approx 116 kbits/sec
4th 128K took 17910 ms = 7318 Bytes/sec = approx 61 kbits/sec

Wed, 11 Aug 2004 23:01:40 UTC
1st 128K took 15540 ms = 8434 Bytes/sec = approx 70 kbits/sec
2nd 128K took 18680 ms = 7017 Bytes/sec = approx 58 kbits/sec
3rd 128K took 3680 ms = 35617 Bytes/sec = approx 296 kbits/sec
4th 128K took 9500 ms = 13797 Bytes/sec = approx 115 kbits/sec

Incog.

Re: [Merged] BB Speed Upgrades
 

It's hard to tell from those results what speed you are on at all, they vary wildly - are you downloading or uploading stuff while doing the tests ?

Re: [Merged] BB Speed Upgrades
 

I'm doing nothing but get annoyed. :(

Re: [Merged] BB Speed Upgrades
 

Yeah, apparantly I've been upgraded too!! Whatever NTL, they can't even get this right.

Re: [Merged] BB Speed Upgrades
 

Mind using the old blueyonder BB speed test I get this

Speed Test Report

Broadband Speed Test - for ntl:World - 128k service
By Daniel Elwell

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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:
14ms - 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 13 ms <10 ms 14 ms 10.67.64.1
2 13 ms <10 ms 14 ms 80.3.162.161
3 14 ms 13 ms 14 ms 80.3.161.133
4 <10 ms 27 ms 14 ms 62.253.188.253
5 13 ms 14 ms 14 ms 62.253.185.74
6 14 ms 14 ms 14 ms 195.66.226.12
7 14 ms 14 ms <10 ms 194.159.36.233
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):
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 194.159.254.213 over a maximum of 20 hops
1 13 ms <10 ms 14 ms 10.67.64.1
2 13 ms <10 ms 14 ms 80.3.162.161
3 14 ms 13 ms 14 ms 80.3.161.133
4 <10 ms 27 ms 14 ms 62.253.188.253
5 13 ms 14 ms 14 ms 62.253.185.74
6 14 ms 14 ms 14 ms 195.66.226.12
7 14 ms 14 ms <10 ms 194.159.36.233
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 3 (www.ic24.net):
14ms - 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 13 ms <10 ms 14 ms 10.67.64.1
2 13 ms 14 ms <10 ms 80.3.162.161
3 13 ms 14 ms <10 ms 80.3.161.133
4 14 ms 14 ms 14 ms 62.253.188.253
5 14 ms <10 ms <10 ms 166.63.211.149
6 96 ms 82 ms 83 ms 195.2.1.3
7 82 ms 83 ms 82 ms 206.24.207.17
8 96 ms 82 ms 97 ms 206.24.226.99
9 206.24.227.106 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 41 ms 55 ms 42 ms 10.67.64.1
2 <10 ms 14 ms * 80.3.162.33
3 13 ms 14 ms 14 ms 80.3.161.5
4 <10 ms 14 ms 14 ms 62.253.188.249
5 27 ms 14 ms 13 ms 166.63.161.229
6 14 ms 14 ms <10 ms 166.63.209.205
7 82 ms 83 ms 96 ms 195.2.1.3
8 82 ms 83 ms 82 ms 206.24.207.17
9 82 ms 83 ms 83 ms 208.172.50.61
10 208.172.51.58 reports: Destination host unreachable.
Trace complete.


European Server (www.marcopoly.com):
17ms - Excellent - better than expected

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

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 41 ms 14 ms <10 ms 10.67.64.1
2 14 ms <10 ms <10 ms 80.3.162.161
3 14 ms <10 ms <10 ms 80.3.161.133
4 14 ms 14 ms 13 ms 62.253.188.253
5 <10 ms 14 ms 13 ms 213.105.172.5
6 14 ms 14 ms 13 ms 62.253.185.78
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 14 ms <10 ms 14 ms 10.67.64.1
2 14 ms 14 ms <10 ms 80.3.162.161
3 14 ms 14 ms <10 ms 80.3.161.133
4 14 ms 13 ms 14 ms 62.253.188.253
5 14 ms <10 ms 13 ms 213.105.172.5
6 14 ms 13 ms 14 ms 62.253.185.78
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 14 ms 14 ms <10 ms 10.67.64.1
2 14 ms 13 ms 14 ms 80.3.162.33
3 <10 ms 13 ms 14 ms 80.3.161.5
4 <10 ms 14 ms 13 ms 62.253.188.249
5 14 ms 13 ms 14 ms 213.105.172.130
6 <10 ms 13 ms 14 ms 213.105.172.5
7 13 ms 14 ms <10 ms 62.253.185.78
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.


Barrysworld Quake III Arena:
0ms - *** PING timed out ***
Tracert to specified location:

Tracing route to 213.221.176.6 over a maximum of 20 hops
1 <10 ms <10 ms 13 ms 10.67.64.1
2 14 ms <10 ms 14 ms 80.3.162.33
3 14 ms 14 ms <10 ms 80.3.161.5
4 14 ms 14 ms 13 ms 62.253.188.249
5 14 ms 13 ms 14 ms 213.105.172.130
6 <10 ms <10 ms 14 ms 213.105.172.5
7 13 ms 14 ms 14 ms 62.253.185.78
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.


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

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 - 128k service Server Download:
31KB/s (248Kb/s) - Superb - much higher than expected

Download through Transparent Cache:
28KB/s (224Kb/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, 46 bounced back; 8% loss (estimated)
Normal - to be expected
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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: 12/08/2004 00:19:51
Test duration: 374 seconds IP address: <removed>
Username: [Not disclosed]
Test Version: 2.81

Broadband Speed Test - www.vantage.pwp.blueyonder.co.uk