Is IS just this slow, or am I doing something wrong?

[Gothan]

I hope its me, but the speeds I get from IS, is terrible

A Normal website, without flashy graphics, flash or gif's (not that this should matter on adsl), takes up to 5 minutes to load, and that is if I refresh it every minute, else it times out.

I have read about everyone stating how happy they are with their IS connection and the speed they get, so that why I am hoping its just me, else comming end of the month, I'll have to crawl back with my tail between my legs to saix

 

[Franna]

The international browsing speed on my IS uncapped ADSL 512K has been terrible since last week. The weekend was especially bad, with google.com taking up to 30 second to load.

Even Lynx had trouble opening webpages...

 

[Gothan]

I just timed it now, a jpeg, of a 160kb's takes close to 5 minutes to load, thats worse then the speed I got when I lived on a farm with a normal 56k modem!

 

[Franna]

I know it is frustrating - nearly pulled my hair out over the weekend.

Go to http://www.mybroadband.co.za/myadsl/speedtest.php and do a local and international speed test. Then send the results to IS support, demanding to know what is wrong.


My IS 512K speed tests
-----------------------

[A] Telkom speed test www.telkom.co.za/minisites/dsl/speed.html
* Download time: 49.406 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 82.6 (kilobits/second)
* Estimated line speed: 10.1 (kiloBytes/second)

BroadbandReports USA speed test http://www.broadbandreports.com/stest?loc=1
Your download speed : 46 kbps or 5.8 KB/sec.
Your upload speed is much faster than down.. have you tweaked?
Your upload speed : 98 kbps or 12.3 KB/sec.

 

[Gothan]

Well this is mine, looks fine on paper, till you try to open that website, and you go and get some coffee, and come back, and you go and get some coffee and you come back and then you go and get some alcohol and you come back, and then it has timed out:

Local:
Below is the data used to calculate your download speed:
Download time: 12.656 seconds
Size of file: 500 KiloBytes
Estimated line speed: 322.4 (kilobits/second)
Estimated line speed: 39.5 (kiloBytes/second)

International:
2005-11-01 15:05:56 EST: 255 / 238
Your download speed : 255 kbps or 31.9 KB/sec.
Your upload speed : 238 kbps or 29.8 KB/sec.

Tried to download the new f.e.a.r. patch from two different servers, the downloads hovers around 10-12 kB/second, where I use to get 39 - 42 kB/second

 

[[3]Shadow]

Here are my stats from local - and yes i did clear the cache - and I am on a 512 DSL
Below is the data used to calculate your download speed:

Download time: 5.656 seconds
Size of file: 500 KiloBytes
Estimated line speed: 721.4 (kilobits/second)
Estimated line speed: 88.4 (kiloBytes/second)

International - you have got to be kidding me - I get 0.00 kilobits per second.

 

[Franna]

What about a ping test "ping www.google.com -w 1000 -t"
Press <control>+<c> to stop the command.

The 14% packet loss is no good.

--------------------------------------------

C:\>ping www.google.com -w 1000 -t

Pinging www.l.google.com [72.14.207.104] with 32 bytes of data:

Reply from 72.14.207.104: bytes=32 time=518ms TTL=231
Reply from 72.14.207.104: bytes=32 time=501ms TTL=231
Reply from 72.14.207.104: bytes=32 time=609ms TTL=231
Reply from 72.14.207.104: bytes=32 time=483ms TTL=231
Reply from 72.14.207.104: bytes=32 time=479ms TTL=231
Request timed out.
Request timed out.
Reply from 72.14.207.104: bytes=32 time=505ms TTL=231
Reply from 72.14.207.104: bytes=32 time=511ms TTL=231
Reply from 72.14.207.104: bytes=32 time=616ms TTL=231
Reply from 72.14.207.104: bytes=32 time=575ms TTL=231
Reply from 72.14.207.104: bytes=32 time=480ms TTL=231
Reply from 72.14.207.104: bytes=32 time=501ms TTL=231
Reply from 72.14.207.104: bytes=32 time=517ms TTL=231
Reply from 72.14.207.104: bytes=32 time=481ms TTL=231
Reply from 72.14.207.104: bytes=32 time=624ms TTL=231
Reply from 72.14.207.104: bytes=32 time=491ms TTL=231
Reply from 72.14.207.104: bytes=32 time=546ms TTL=231
Request timed out.
Reply from 72.14.207.104: bytes=32 time=503ms TTL=231
Reply from 72.14.207.104: bytes=32 time=650ms TTL=231

Ping statistics for 72.14.207.104:
Packets: Sent = 21, Received = 18, Lost = 3 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 479ms, Maximum = 650ms, Average = 456ms

 

[Gothan]

Here's mine

Pinging www.l.google.com [216.239.59.103] with 32 bytes of data:

Reply from 216.239.59.103: bytes=32 time=698ms TTL=238
Reply from 216.239.59.103: bytes=32 time=693ms TTL=238
Reply from 216.239.59.103: bytes=32 time=692ms TTL=238
Reply from 216.239.59.103: bytes=32 time=692ms TTL=238
Reply from 216.239.59.103: bytes=32 time=695ms TTL=238
Reply from 216.239.59.103: bytes=32 time=694ms TTL=238
Reply from 216.239.59.103: bytes=32 time=700ms TTL=238
Request timed out.
Reply from 216.239.59.103: bytes=32 time=690ms TTL=238
Reply from 216.239.59.103: bytes=32 time=698ms TTL=238
Reply from 216.239.59.103: bytes=32 time=700ms TTL=238
Reply from 216.239.59.103: bytes=32 time=696ms TTL=238
Reply from 216.239.59.103: bytes=32 time=694ms TTL=238
Reply from 216.239.59.103: bytes=32 time=694ms TTL=238
Reply from 216.239.59.103: bytes=32 time=692ms TTL=238
Reply from 216.239.59.103: bytes=32 time=700ms TTL=238
Reply from 216.239.59.103: bytes=32 time=691ms TTL=238
Reply from 216.239.59.103: bytes=32 time=695ms TTL=238
Reply from 216.239.59.103: bytes=32 time=689ms TTL=238
Reply from 216.239.59.103: bytes=32 time=693ms TTL=238
Reply from 216.239.59.103: bytes=32 time=690ms TTL=238
Reply from 216.239.59.103: bytes=32 time=692ms TTL=238
Reply from 216.239.59.103: bytes=32 time=695ms TTL=238
Reply from 216.239.59.103: bytes=32 time=698ms TTL=238
Reply from 216.239.59.103: bytes=32 time=700ms TTL=238
Reply from 216.239.59.103: bytes=32 time=692ms TTL=238

Ping statistics for 216.239.59.103:
Packets: Sent = 26, Received = 25, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 689ms, Maximum = 700ms, Average = 694ms

 

[[3]Shadow]

Here are my stats for ping to www.google.com
C:\>ping www.google.com -w 1000 -t

Pinging www.l.google.com [216.239.59.104] with 32 bytes of data:

Reply from 216.239.59.104: bytes=32 time=701ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=703ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=703ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=703ms TTL=238
Reply from 216.239.59.104: bytes=32 time=700ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=703ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238
Reply from 216.239.59.104: bytes=32 time=703ms TTL=238
Reply from 216.239.59.104: bytes=32 time=687ms TTL=238

Ping statistics for 216.239.59.104:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 687ms, Maximum = 703ms, Average = 690ms

Total different IP for Google than the one that Franna got?

 

[Highflyer_GP]

mine seems to be fine on local test on 192

Below is the data used to calculate your download speed:

Download time: 15.047 seconds
Size of file: 500 KiloBytes
Estimated line speed: 271.2 (kilobits/second)
Estimated line speed: 33.2 (kiloBytes/second)

international is slow, don't know yet if it's just IS that's experiencing this or everyone

 

[Roman4604]

Been warning ppl for a while now .... IS international experience is not the same as SAIX.

 

[Highflyer_GP]

screw this i'd rather deal with a hardcap for the last few days in the month. transfer speeds of 4-5KB/s is not acceptable on adsl. got an urge to change back to saix tomorrow

 

[Compl33t]

Yeah...I'm going to give it a month or so.

Chances are that everything's in shambles because of the November changes.

Mine's super-slow too, btw. (Maybe it's a good thing...slower, my cap will last longer)

 

[Faffy]

mines been fine, atleast my international torrents have been going well, havent done much browsing. Torrents actually going better than what they went on saix ;p

 

[Compl33t]

Oh, forgot to mention that. Only my HTTP traffic's slow.

Torrents, FTP, etc...they're moving along as expected.
Azurues even gives me an OK on the port test. Never happened on my SAIX account.

Like I said...I'm giving IS a chance.

 

[Highflyer_GP]

same here, P2P, FTP & torrents moving ok, just HTTP is crawling

 

[Gothan]

Well I'm still standing strong and in defiance of SAIX. MrBEEP has been very helpful, I'll test it again when I get home tonight

 

[JayM]

I managed to get hold of an IS test account. During the day, it is slower than a 56K modem for browsing. SAIX is superior - no doubt about it. Even though I'd rather not use Telkom, I'm not going to cut off my nose to spite my face and endure IS speed (or lack thereof).

 

[Gothan]

MrBEEP quickly created a backup proxy for me to use while IS is looking into the problem, now that is service and its only 7:50 am in the morning, doesnt he ever sleep??

 

[kilos]

Web based traceroute & ping utility on IS 512k Business ADSL

http://196.211.2.162/cgi-bin/traceroute.cgi
http://196.211.2.162/cgi-bin/ping.cgi

Downloaded 640 Mb frile from Dell HTTP in 3.5 hrs ave 51k/s

Time: 14:04
PING www.l.google.com (66.249.85.104) 56(84) bytes of data.
64 bytes from 66.249.85.104: icmp_seq=0 ttl=237 time=725 ms
64 bytes from 66.249.85.104: icmp_seq=1 ttl=236 time=719 ms
64 bytes from 66.249.85.104: icmp_seq=2 ttl=236 time=724 ms

No packet loss
Same IP as Franna no packet loss
PING 72.14.207.104 (72.14.207.104) 56(84) bytes of data.
64 bytes from 72.14.207.104: icmp_seq=0 ttl=236 time=665 ms
64 bytes from 72.14.207.104: icmp_seq=1 ttl=236 time=669 ms
64 bytes from 72.14.207.104: icmp_seq=2 ttl=236 time=674 ms
64 bytes from 72.14.207.104: icmp_seq=3 ttl=236 time=671 ms
64 bytes from 72.14.207.104: icmp_seq=4 ttl=236 time=661 ms
64 bytes from 72.14.207.104: icmp_seq=5 ttl=236 time=663 ms
64 bytes from 72.14.207.104: icmp_seq=6 ttl=236 time=670 ms
64 bytes from 72.14.207.104: icmp_seq=7 ttl=236 time=674 ms

--- 72.14.207.104 ping statistics ---
9 packets transmitted, 8 received, 11% packet loss, time 8084ms
rtt min/avg/max/mdev = 661.464/668.906/674.717/4.689 ms, pipe 2

PING 196.25.1.1 (196.25.1.1) 56(84) bytes of data.
64 bytes from 196.25.1.1: icmp_seq=0 ttl=245 time=100 ms
64 bytes from 196.25.1.1: icmp_seq=1 ttl=245 time=102 ms
64 bytes from 196.25.1.1: icmp_seq=2 ttl=245 time=96.9 ms
64 bytes from 196.25.1.1: icmp_seq=3 ttl=245 time=91.5 ms
64 bytes from 196.25.1.1: icmp_seq=4 ttl=245 time=98.9 ms
64 bytes from 196.25.1.1: icmp_seq=5 ttl=245 time=104 ms
64 bytes from 196.25.1.1: icmp_seq=6 ttl=245 time=94.0 ms
64 bytes from 196.25.1.1: icmp_seq=7 ttl=245 time=101 ms
64 bytes from 196.25.1.1: icmp_seq=8 ttl=245 time=136 ms

VERY GOOD traceroute to SAIX 196.25.1.1 (normally 230ms during the day)
traceroute to 196.25.1.1 (196.25.1.1), 30 hops max, 38 byte packets
1 196.211.2.161 (196.211.2.161) 1.514 ms 2.105 ms 1.387 ms
2 196.211.129.13 (196.211.129.13) 79.110 ms 80.541 ms 83.634 ms
3 196.36.80.209 (196.36.80.209) 85.997 ms 92.147 ms 90.101 ms
4 196.26.96.203 (196.26.96.203) 92.719 ms 85.724 ms 82.843 ms
5 196.26.0.250 (196.26.0.250) 89.586 ms 85.794 ms 89.254 ms
6 168.209.86.166 (168.209.86.166) 88.267 ms 78.624 ms 81.675 ms
7 196.25.5.29 (196.25.5.29) 122.502 ms 126.622 ms 126.101 ms
8 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30) 143.648 ms 135.705 ms 129.223 ms
9 igubu.saix.net (196.25.1.1) 126.942 ms 127.921 ms 116.961 ms