iBurst very slow

Your line speed is approximately 61 Kbps or 7.5 kBytes/sec

and day 4 of the slow down saga continues....
 
yeah it looks like they might be shaping in the day and opening up the tap at night, I won't even bother to download untill tonight
 
Telkom speed test loaded on third attempt. Result:

* Estimated line speed: 830.3 (kilobits/second)
* Estimated line speed: 101.8 (kiloBytes/second)

Trio of ping tests:

----195.92.95.5 PING Statistics----
66 packets transmitted, 56 packets received, 15% packet loss
round-trip (ms) min/avg/max = 330/359/470

----196.4.160.2 PING Statistics----
66 packets transmitted, 57 packets received, 13% packet loss
round-trip (ms) min/avg/max = 50/71/210

----196.30.31.120 PING Statistics----
66 packets transmitted, 58 packets received, 12% packet loss
round-trip (ms) min/avg/max = 50/68/280

MyADSL loaing slowly. Personal news server timing out on both local and international news server connections. Mail fetch successful on second attempt.

The network is wobbling again!
 
* Download time: 4.422 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 922.7 (kilobits/second)
* Estimated line speed: 113.1 (kiloBytes/second)

This is at 9:30 this morning, much the same as last night, ping rate much the same as Mercury
 
Download time: 6.453 seconds
Size of file: 500 KiloBytes
Estimated line speed: 632.3 (kilobits/second)
Estimated line speed: 77.5 (kiloBytes/second)
 
then i get this...
Below is the data used to calculate your download speed:

Download time: 0.047 seconds
Size of file: 500 KiloBytes
Estimated line speed: 86808.5 (kilobits/second)
Estimated line speed: 10638.3 (kiloBytes/second)
 
Eish man..whew!!!
Download time: 3.39 seconds
Size of file: 500 KiloBytes
Estimated line speed: 1203.5 (kilobits/second)
Estimated line speed: 147.5 (kiloBytes/second)

not bad
 
Bjorn said:
then i get this...
Below is the data used to calculate your download speed:

Download time: 0.047 seconds
Size of file: 500 KiloBytes
Estimated line speed: 86808.5 (kilobits/second)
Estimated line speed: 10638.3 (kiloBytes/second)

probably got it from the browser cache, even if you tried to force a reload.
Or the timing script going haywire...
Get it from time to time as well :)
 
5 consecutive tests, #4 obviously flaky...

1 * Download time: 4.366 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 934.5 (kilobits/second)
* Estimated line speed: 114.5 (kiloBytes/second)

2 * Download time: 4.907 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 831.5 (kilobits/second)
* Estimated line speed: 101.9 (kiloBytes/second)

3 * Download time: 4.576 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 891.6 (kilobits/second)
* Estimated line speed: 109.3 (kiloBytes/second)

4 * Download time: 0.561 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 7272.7 (kilobits/second)
* Estimated line speed: 891.3 (kiloBytes/second)

5 * Download time: 5.488 seconds
* Size of file: 500 KiloBytes
* Estimated line speed: 743.4 (kilobits/second)
* Estimated line speed: 91.1 (kiloBytes/second)
 
Your line speed is approximately 746 Kbps or 91.4 kBytes/sec

i am happy :)
 
From the consistently good Telkom speed test results, I would think that WBS have made sure their peering is well set up in this regard. Makes sense since it is an obvious marketing tool.

There must be other issues on the WBS network, given the pattern of packet loss. My trio go from international (Netcraft), local on another net (Internet Solution), to local on the WBS network (the iBurst web site).

----195.92.95.5 PING Statistics----
66 packets transmitted, 55 packets received, 16% packet loss
round-trip (ms) min/avg/max = 330/365/510

----196.4.160.2 PING Statistics----
66 packets transmitted, 62 packets received, 6% packet loss
round-trip (ms) min/avg/max = 60/78/180

----196.30.31.120 PING Statistics----
66 packets transmitted, 58 packets received, 12% packet loss
round-trip (ms) min/avg/max = 50/77/180
 
PING 195.92.95.5 (195.92.95.5) 56(84) bytes of data.
--- 195.92.95.5 ping statistics ---
66 packets transmitted, 66 received, +1 duplicates, 0% packet loss, time 65067ms
rtt min/avg/max/mdev = 358.558/396.052/713.600/52.244 ms, pipe 2

PING 196.4.160.2 (196.4.160.2) 56(84) bytes of data.
--- 196.4.160.2 ping statistics ---
66 packets transmitted, 66 received, 0% packet loss, time 65072ms
rtt min/avg/max/mdev = 47.133/84.479/297.499/41.581 ms, pipe 2

PING 196.30.31.120 (196.30.31.120) 56(84) bytes of data.
--- 196.30.31.120 ping statistics ---
66 packets transmitted, 66 received, 0% packet loss, time 65051ms
rtt min/avg/max/mdev = 45.387/79.336/318.895/39.964 ms, pipe 2
 
Your line speed is approximately 859.5 Kbps or 105.3 kBytes/sec
( Where kb = kilobits and kB = kiloBytes )

Just got the fright of my life - downloaded a 35Mb file from downloads.worldonline.co.za in a couple of minutes! DUSpeed says max 129.5 kB/s - and IE topped out at 100. Is this going to last?
 
My connection was fast from 18:30 yesterday till I accidentally restarted my pc. Right now my speed is about 20kb/s. I reached my cap 2 days ago but I managed to get 4GB last night so maybe the speeds will improve after 18:00.

I'm happy with 20kb/s after being capped.
 
ya...i think its a very fair speed to have after capping, you can still download allot with that speed
 
im capped and my local speed test is 1.7kb/s or 14kbps

So maybe there was some miscommunication between management and marketing which filtered through to the techies actually capping you to 14.4 modem speeds, which is effectively throwing back the whole "broadband" internet to narrowband days when internet first came to south africa in the 90's.

Telkom, touching tomorrow with yesterday's technology
iBurst, touching yesterday with tomorrow's technology
 
Top
Sign up to the MyBroadband newsletter
X