slow telewest speeds (possibly)

[antz1970]

ok guys i got a problem (i think) i am on blueyonder 10mb(have been since the trial) i get nearly full speeds of 9.4mb from newsgroups , but for the last couple of weeks i have been getting slow surfing speeds(is this possible if full speed is possible thru newsgroups) i have phoned blueyonder a few times and always told basically its my pc, however after recently doing a full format and installing pc guard things aint any better.i have done the rounds with various speed tests and in my opinion i get poor results, i just used the test on www.speedtest.net (http://www.speedtest.net) , and ping times to london seem slow (last test was 179ms) and speeds can vary from between 2.5mb up to about 7mb, anyway my questions are, can slow surfing be a blueyonder problem(even tho newsgroups are running fast?) and what is a good reliable speedtest that i can use and blueyonder will listen to the results.the dan elwell one is a no go as it times out or server error on the download test.hope this all makes sense , and sorry for not using paragraphs etc lol

[don_fandango]

if u go to blueyonder and tell them about the speedtests you've done they'l tend to disregard them as unreliable and direct you to gamefiles.blueyonder.co.uk or microsoft and to under take a download of a large file.

if then you're downloading at a slower rate than u should b getting from these, its only really then they look into it further.

but in my opinion, these online speed test sites are all a bunch of bulls**t anyway. feel free to disagree guys, but they are unreliable...

[Markos1977]

u will only get full speed if the uploader has a good upload speed as for gamefiles.blueyonder.co.uk and microsoft u will get good speed cose thay got good upload speed and for speed test sites i allwiss get the propper speed that iam on


Edit and dont do a speed test wen u are downloading or uploading it wont tell u the propper speeds

[andyr2005]

When dowloading from newsgroups, you are not downloading from a 'seeder' as like torrents.

A user uploads content to the newsgroup server, and you then download at the top speed your connection and the server can handle. No uploading is done by the user.

[The Jackal]

When dowloading from newsgroups, you are not downloading from a 'seeder' as like torrents.

A user uploads content to the newsgroup server, and you then download at the top speed your connection and the server can handle. No uploading is done by the user.

And the news server/games servers are located locally on by's network consider it like a machine connected directly to your cable modem.... Past this you go out to the real world or the internet as we call it. You're not using a lot of p2p software are u ?

Welcome to cwappy connections r 2.

---------- Post added at 03:40 ---------- Previous post was at 03:31 ----------

Check out these pings to a machine in a London datacentre a few hops away from the bbc....

With my line idle we average 10ms (not bad and prolly the best you get out of by) with the odd spike here or there ....

scroll down and see the pings go haywire from me just simply uploading a file.

If you're uploading or have a certain percentage of upstream expect to get your wrists slapped and told to stand in the corner


Reply from 84.246.193.103: bytes=32 time=9ms TTL=53
Reply from 84.246.193.103: bytes=32 time=14ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=14ms TTL=53
Reply from 84.246.193.103: bytes=32 time=12ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=15ms TTL=53
Reply from 84.246.193.103: bytes=32 time=10ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=12ms TTL=53
Reply from 84.246.193.103: bytes=32 time=9ms TTL=53
Reply from 84.246.193.103: bytes=32 time=553ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1397ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1283ms TTL=53
Reply from 84.246.193.103: bytes=32 time=629ms TTL=53
Reply from 84.246.193.103: bytes=32 time=74ms TTL=53
Reply from 84.246.193.103: bytes=32 time=597ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1068ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1143ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1178ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1141ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1142ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1192ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1185ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1280ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1235ms TTL=53
Reply from 84.246.193.103: bytes=32 time=1232ms TTL=53
Reply from 84.246.193.103: bytes=32 time=999ms TTL=53
Reply from 84.246.193.103: bytes=32 time=662ms TTL=53
Reply from 84.246.193.103: bytes=32 time=711ms TTL=53
Reply from 84.246.193.103: bytes=32 time=692ms TTL=53
Reply from 84.246.193.103: bytes=32 time=740ms TTL=53
Reply from 84.246.193.103: bytes=32 time=222ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=23ms TTL=53
Reply from 84.246.193.103: bytes=32 time=15ms TTL=53
Reply from 84.246.193.103: bytes=32 time=11ms TTL=53
Reply from 84.246.193.103: bytes=32 time=16ms TTL=53
Reply from 84.246.193.103: bytes=32 time=10ms TTL=53
Reply from 84.246.193.103: bytes=32 time=10ms TTL=53
Reply from 84.246.193.103: bytes=32 time=10ms TTL=53
Reply from 84.246.193.103: bytes=32 time=13ms TTL=53

Ping statistics for 84.246.193.103:
Packets: Sent = 114, Received = 114, Lost = 0 (0% loss),

---------- Post added at 03:52 ---------- Previous post was at 03:40 ----------

Let me ping news.blueyonder.co.uk from the datacentre

PING news.blueyonder.co.uk (194.117.143.53) from xx.xx.xx.xx : 56(84) bytes of data.
64 bytes from 194.117.143.53: icmp_seq=1 ttl=246 time=8.68 ms
64 bytes from 194.117.143.53: icmp_seq=2 ttl=246 time=8.86 ms
64 bytes from 194.117.143.53: icmp_seq=3 ttl=246 time=8.95 ms
64 bytes from 194.117.143.53: icmp_seq=4 ttl=246 time=8.75 ms
64 bytes from 194.117.143.53: icmp_seq=5 ttl=246 time=8.88 ms
64 bytes from 194.117.143.53: icmp_seq=6 ttl=246 time=9.30 ms
64 bytes from 194.117.143.53: icmp_seq=7 ttl=246 time=8.97 ms
64 bytes from 194.117.143.53: icmp_seq=8 ttl=246 time=8.88 ms
64 bytes from 194.117.143.53: icmp_seq=9 ttl=246 time=8.93 ms
64 bytes from 194.117.143.53: icmp_seq=10 ttl=246 time=8.91 ms
64 bytes from 194.117.143.53: icmp_seq=11 ttl=246 time=8.80 ms
64 bytes from 194.117.143.53: icmp_seq=12 ttl=246 time=8.87 ms
64 bytes from 194.117.143.53: icmp_seq=13 ttl=246 time=8.88 ms
64 bytes from 194.117.143.53: icmp_seq=14 ttl=246 time=8.68 ms
64 bytes from 194.117.143.53: icmp_seq=15 ttl=246 time=8.98 ms
64 bytes from 194.117.143.53: icmp_seq=16 ttl=246 time=8.98 ms
64 bytes from 194.117.143.53: icmp_seq=17 ttl=246 time=9.03 ms
64 bytes from 194.117.143.53: icmp_seq=18 ttl=246 time=8.67 ms
64 bytes from 194.117.143.53: icmp_seq=19 ttl=246 time=8.77 ms
64 bytes from 194.117.143.53: icmp_seq=20 ttl=246 time=8.77 ms
64 bytes from 194.117.143.53: icmp_seq=21 ttl=246 time=9.04 ms
64 bytes from 194.117.143.53: icmp_seq=22 ttl=246 time=9.12 ms
64 bytes from 194.117.143.53: icmp_seq=23 ttl=246 time=9.07 ms
64 bytes from 194.117.143.53: icmp_seq=24 ttl=246 time=8.95 ms
64 bytes from 194.117.143.53: icmp_seq=25 ttl=246 time=8.83 ms
64 bytes from 194.117.143.53: icmp_seq=26 ttl=246 time=8.70 ms
64 bytes from 194.117.143.53: icmp_seq=27 ttl=246 time=9.18 ms
64 bytes from 194.117.143.53: icmp_seq=28 ttl=246 time=8.76 ms
64 bytes from 194.117.143.53: icmp_seq=29 ttl=246 time=8.70 ms
64 bytes from 194.117.143.53: icmp_seq=30 ttl=246 time=8.92 ms
64 bytes from 194.117.143.53: icmp_seq=31 ttl=246 time=8.92 ms
64 bytes from 194.117.143.53: icmp_seq=32 ttl=246 time=8.87 ms
64 bytes from 194.117.143.53: icmp_seq=33 ttl=246 time=8.94 ms
64 bytes from 194.117.143.53: icmp_seq=34 ttl=246 time=9.10 ms
64 bytes from 194.117.143.53: icmp_seq=35 ttl=246 time=8.85 ms
64 bytes from 194.117.143.53: icmp_seq=36 ttl=246 time=8.98 ms
64 bytes from 194.117.143.53: icmp_seq=37 ttl=246 time=8.80 ms

Oh man what beautiful pings !

Lets ping my cable modem wahay u can see the spikes

~> ping home
PING home (80.195.237.115) from xx.xx.xx.xx : 56(84) bytes of data.
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=1 ttl=54 time=9.67 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=2 ttl=54 time=9.46 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=3 ttl=54 time=9.30 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=4 ttl=54 time=11.4 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=5 ttl=54 time=9.60 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=6 ttl=54 time=9.60 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=7 ttl=54 time=12.9 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=8 ttl=54 time=9.49 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=9 ttl=54 time=35.4 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=10 ttl=54 time=12.1 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=11 ttl=54 time=9.47 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=12 ttl=54 time=9.54 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=13 ttl=54 time=9.68 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=14 ttl=54 time=9.90 ms
64 bytes from 80-195-237-115.cable.ubr03.enfi.blueyonder.co.uk (80.195.237.115): icmp_seq=15 ttl=54 time=11.6 ms

If only I had pings like this at home :shocked: :

ping the bbc
ping www.bbc.co.uk
PING www.bbc.net.uk (212.58.224.114) from xxxxxxxxxx : 56(84) bytes of data.
64 bytes from 212.58.224.114: icmp_seq=1 ttl=252 time=0.858 ms
64 bytes from 212.58.224.114: icmp_seq=2 ttl=252 time=0.838 ms
64 bytes from 212.58.224.114: icmp_seq=3 ttl=252 time=0.711 ms

It aint gonna happen for many years yet

[andyr2005]

CrC-err0r,

Which cable modem do you have from Blueyonder?

[The Jackal]

CrC-err0r,

Which cable modem do you have from Blueyonder?

Some ugly old rubbish one : Had it for around 5 years why can you help me get better speeds ? Can the cable modem be tweaked ?

Anyway it lives downstairs in a little closet with my electricity meter if you really want to know I could go and get the model number.

I think its this one : http://broadband.motorola.com/catalog/productdetail.asp?image=large&productID=216

[Markos1977]

i would get a new modem from telewest the modem u hav has cr*p firmware all sb4100 and sb4200 firmware is cr*p

[andyr2005]

Depends on what aspect of the service you want tweaked.

I can guide you how to make Firefox or Internet Explorer browsing quicker, the use of BitTorrent can also be tweaked slightly. As for others, newgroups can also be, depending upon which software you use.

[The Jackal]

i would get a new modem from telewest the modem u hav has cr*p firmware all sb4100 and sb4200 firmware is cr*p

And what happens after they replace it better or worse speeds ?
Has this got something to do with it being only DOCSIS 1.0 1.1 compatible ?

Someone please enlighten me to as to whether going from DOCSIS 1.1 -> 2 will benefit me or telewest ?

[janipewter]

No - Telewest's network is DOCSIS1.0 and I highly doubt they will be moving to DOCSIS1.1 or even 2.0 in the future at all, as FTTH is now the next step.