Poor Poor Speeds GL2 Area

volatile · 02-01-2006, 23:26

Live in Gloucester the past 3weeks the speeds just get worse and worse. Ping times, packetloss is the worst download speeds are reasonable and i can live with that personally i rather stick to 470kb/sec instead of a measly 145lb/sec max on 10mb, i just ran a speed test using Dan Elwells test and these are my results:

[IMG]file:///C:/DOCUME%7E1/Colin/LOCALS%7E1/Temp/moz-screenshot.jpg[/IMG][IMG]file:///C:/DOCUME%7E1/Colin/LOCALS%7E1/Temp/moz-screenshot-1.jpg[/IMG]Dan Elwell's Broadband Speed Test
Speed Test Report 06/01/02 22:16 - Quick test

Test conducted at: 02/01/2006 22:16:00
Test sequence: Quick test

Please note that these results are a snapshot of this particular moment. Run the test a few times to ensure maximum accuracy. Although the test has been constructed to be highly accurate, no guarantees can be made to the level of accuracy experienced in everyday use.

Test 1: Ping times to UK servers

Ideally, you should get a result of around 30 ms (lower is better)

worcester.ac.uk: 217.7 ms
vantage.myby.co.uk: 191.5 ms
f2s.com: 182.8 ms

This result shows serious problems with your ping times, and should be investigated.

Test 2: Ping times to European servers

Ideally, you should get a result of around 50 ms (lower is better)

club-internet.fr: 183.5 ms
lycos.es: 271 ms
univ-rennes1.fr: 158 ms

This result shows serious problems with your ping times, and should be investigated.

Test 3: Ping times to east-coast USA servers

Ideally, you should get a result of around 120 ms (lower is better)

internet2.edu: 269.5 ms
mirror.nocservices.com: 264 ms
internet2.edu: 276.7 ms

This result shows serious problems with your ping times, and should be investigated.

Test 4: Ping times to west-coast USA servers

Ideally, you should get a result of around 160 ms (lower is better)

redhat.netnitco.net: 367 ms
mirror.ats.ucla.edu: This test failed due to a server timeout or other error.
redhat.netnitco.net: 369.7 ms

This result is much poorer than expected and should be investigated.

Test 5: Download speeds from UK servers

Ideally, you should get a result of around 1000 Kb/s (higher is better)

apache.mirror.positive-internet.com: This test failed due to a server timeout or other error.

Too many server errors occurred therefore this test is inconclusive.

Test 6: Upload speeds to the Speed Test Server

Ideally, you should get a result of around 358 Kb/s (higher is better)

broadbandspeedtest.net: 261 Kb/s

This result is much poorer than expected and should be investigated.

Test 7: Packet loss en route to a UK server

Ideally, you should get a result of around 0 % (lower is better)

zeniiia.linux.org.uk: 8 %
swansea.ac.uk: 0 %

A small amount of packet loss has been detected. This should be investigated.

End of testing.

This report was collated using Dan Elwell's Broadband Speed Test. For more information or to download, please visit www.broadbandspeedtest.net.

Generated 02/01/2006 22:17:52 using test version 3.0.316 - registered copy.

I know you peeps are gonna ask about virus scanning, spyware, adware etc and i can tell you my PC is clean and upto date in all my software, harware
has all the latest firmware. Im running XP Pro all upto date. Im thinking of switching over to another ISP at this point cos i cant take having a crappy service.

Ignition · 02-01-2006, 23:44

Looks like upstream congestion dude, have you called Telewest? What did they say about the upstream load in your area? Do you have a Surfboard modem? Can you move to another upstream?

volatile · 03-01-2006, 16:46

I have not contacted TW as of yet, im using a surboard sb4100 modem. Im gonna contact TW in a sec actually. Gonna run another speed test.

---------- Post added at 15:46 ---------- Previous post was at 15:39 ----------

Just did a traceroute to bbc.co.uk and these are following results.

Quote:

Tracing route to bbc.co.uk [212.58.224.131]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 10.24.128.1
3 15 ms 7 ms 7 ms gsr01-st.blueyonder.co.uk [62.30.65.1]
4 13 ms 11 ms 13 ms 195.188.230.49
5 17 ms 17 ms 15 ms 195.188.230.6
6 17 ms 16 ms 16 ms tele1-azt-pos.telewest.net [194.117.136.2]
7 16 ms 17 ms 17 ms 194.117.136.146
8 89 ms 18 ms 39 ms 194.117.148.171
9 11 ms 11 ms 12 ms 212.58.238.153
10 13 ms 11 ms 11 ms rdirwww-vip.thdo.bbc.co.uk [212.58.224.131]

Trace complete.

Same speed test as i posted in original post:

Quote:

Test 1: Ping times to UK servers

Ideally, you should get a result of around 30 ms (lower is better)

bbc.co.uk: 12.3 ms
clara.net: 18.3 ms
gnu.teleglobe.net: 17.3 ms

The results of this test indicate no problems.

Test 2: Ping times to European servers

Ideally, you should get a result of around 50 ms (lower is better)

uvsq.fr: 25.5 ms
sunsite.cnlab-switch.ch: 43 ms
lycos.es: 50.3 ms

The results of this test indicate no problems.

Test 3: Ping times to east-coast USA servers

Ideally, you should get a result of around 120 ms (lower is better)

the-city.seas.upenn.edu: This test failed due to a server timeout or other error.
unet.brandeis.edu: 95.8 ms
dulug.duke.edu: 93.3 ms

The results of this test indicate no problems.

Test 4: Ping times to west-coast USA servers

Ideally, you should get a result of around 160 ms (lower is better)

mirrors.usc.edu: 160 ms
mirrors.usc.edu: 161.5 ms
ucsb.edu: 174.3 ms

The results of this test indicate no problems.

Test 5: Download speeds from UK servers

Ideally, you should get a result of around 1000 Kb/s (higher is better)

download.mirror.ac.uk: 5983 Kb/s

The results of this test indicate no problems.

Test 6: Upload speeds to the Speed Test Server

Ideally, you should get a result of around 358 Kb/s (higher is better)

speedtestapi.co.uk: This test failed due to a server timeout or other error.

Too many server errors occurred therefore this test is inconclusive.

Test 7: Packet loss en route to a UK server

Ideally, you should get a result of around 0 % (lower is better)

plig.net: This test failed due to a server timeout or other error.
bristol.ac.uk: 0 %

Too many server errors occurred therefore this test is inconclusive.

End of testing.

Ignition · 03-01-2006, 17:21

Good! See if it holds up or if it starts going completely wrong around 6 - 7PM (when all those people who've been off work for the Christmas break get back and start wanting to use their connections again).