ADSL speed

Status
Not open for further replies.
02 August 2003

Time 14:45

Speed test = 51.96 kbits/second or 6.495 kbytes/second

Not what i'm paying for !
 
Tried another type of speed test. The site is download.com and you can clock the download speed on every file you want to download. Here is an example of one I did now:


File I clocked
Microsoft Internet Explorer 479K 35.7k 1 min. 49 sec.

Compare your download speed to other ISPs available in your area.
Download Time Connection Type/Speed ISP Price Range

2 sec. DSL 1.5MB SBC Yahoo! $34.95 - 59.95

5 sec. DSL 768k View ISPs

10 sec. DSL 384k View ISPs

30 sec. ISDN 128k Aplus.Net $39.95

1 min. 1 sec. ISDN 64k View ISPs

1 min. 13 sec Dialup 53.3k IVWNET $8.25

<b>1 min. 49 sec 35.7 kbps You(Telkom) R 900-00+ or $115.00+</b>

1 min. 56 sec Dialup 33.6k

I edited their response and put in the cost for ADSL in South Africa. Quite a big difference.
 
Hi folks

Thanks a bunch for all the info. This is valuable to anybody visiting the site and looking for info regarding ADSL.

Regards,

RPM


RPM
[email protected]
 
I realy have to stop posting to this forum[;)], but with such a crappy service i have nothing better to do.

Here is a few pings i made to the outgoing router before it hits the international bandwidth. This server is located in Cape Town btw. Speaking to someone at SAIX, they say the reason is that the router is congested!

london-dir-telecity-pos-8-0-0.telkom-ipnet.co.za
[196.43.9.50]


Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1263ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1263ms, Maximum = 1263ms, Average = 1263ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1181ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1181ms, Maximum = 1181ms, Average = 1181ms

Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1524ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1524ms, Maximum = 1524ms, Average = 1524ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=947ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 947ms, Maximum = 947ms, Average = 947ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=2114ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2114ms, Maximum = 2114ms, Average = 2114ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1510ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1510ms, Maximum = 1510ms, Average = 1510ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1442ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1442ms, Maximum = 1442ms, Average = 1442ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=879ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 879ms, Maximum = 879ms, Average = 879ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=439ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 439ms, Maximum = 439ms, Average = 439ms

Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.

Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1620ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1620ms, Maximum = 1620ms, Average = 1620ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1922ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1922ms, Maximum = 1922ms, Average = 1922ms

Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.

Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=659ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 659ms, Maximum = 659ms, Average = 659ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1359ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1359ms, Maximum = 1359ms, Average = 1359ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1496ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1496ms, Maximum = 1496ms, Average = 1496ms

Pinging 196.43.9.50 with 1425 bytes of data:
Request timed out.
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Pinging 196.43.9.50 with 1425 bytes of data:
Reply from 196.43.9.50: bytes=1425 time=1058ms TTL=253
Ping statistics for 196.43.9.50:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1058ms, Maximum = 1058ms, Average = 1058ms

I ran this ping with a 3 second delay. Notice the number of timeouts and packets lost.

No wonder we are complaining. What confuses the hell out of me is that this is on a local server. The issue of international bandwidth does not feature here. Or am I missing the point?
 
Hi Merlin

Thanks a bunch for the postings. You are making a great contribution…please don’t talk about quitting. You are our star player :-)

The service is becoming a mess…a joke.

RPM


RPM
[email protected]
 
Is it just me or does international browsing seem faster now? I am currently capped and getting very good browsing speeds internationally (+- 30k/sec)
Any ideas?
No i'm not using anything 'special' just plain default settings the works...

?[?]

=TT=
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Revix</i>
<br />Is it just me or does international browsing seem faster now? I am currently capped and getting very good browsing speeds internationally (+- 30k/sec)
Any ideas?
No i'm not using anything 'special' just plain default settings the works...

?[?]

=TT=
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">
No, it isn't faster-it's atrocious-since yesterday evening the speed has progressively just gone to hell.
How on earth do you manage to get capped on the 3rd day of the month?

10.3 kilobits per second
Compared to all connection types worldwide, yours is poor
That's consistent with my browsing experience.
 
Hi guys

It is now around 10 pm on Sunday 3 Aug, and my speed is a whopping 15.63 kbits/s. This is more than 3 times slower than a standard dial up modem connection. And let us remember that all businesses with many PC’s connected to their line are offline. We are in for a laugh tomorrow.

And let us remember that we are using a prioritized port to do this testing!


Regards,

RPM


RPM
[email protected]
 
Don't know what the hell is going on but if this is the kind of thing we can expect from now on, it's going to make a grown man like me, cry. I've been trying to download MSN Messenger 6 but even prayer fails.
 
Hi Plug

It is indeed getting worse every month. The real damage is only seen in the beginning of the month when all users are on the same pipe. And what a mess it is. I timeout quite frequently now…and it is weekend.

Regards,

RPM


RPM
[email protected]
 
Running a staff lan (12 users) through a proxy off "512" ADSL
getting :
your speed is :
30.9 kbits/sec


This is my first visit to this site and have spent a few minutes reading through old postings. It appears that some people are under the impression that the 3G cap consists of only international traffic. That is not the case (according to Telkom - but what do they know!?). The way it works is : once your <b>combined</b> traffic reaches 3Gb then your international traffic is capped.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Revix</i>
<br />Is it just me or does international browsing seem faster now? I am currently capped and getting very good browsing speeds internationally (+- 30k/sec)
Any ideas?
No i'm not using anything 'special' just plain default settings the works...

?[?]

=TT=
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

Its possible you may get some speed internationally if you have been capped really early. Works like this , everyone starts the month with full speed (sort of) so everyone is on the uncapped bandwidth...so if you get capped early you will be one of the few using the throttled international bandwith - as there is still realatively few users that are capped all the throttled bandwith will be available...as the month progresses you will notice your speed gets slower due to more people getting capped.

Works the other way around too...at the beginning of the month the entire ADSL subscriber base is on the main international bandwidth so naturally we all suffer..and when we use up our quota we all end up on the throttled bandwidth...either way we lose.

I actually phone the fault line to ask if I was uncapped .... I didn't even notice the difference at first.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X