iBurst very slow

I am in bryanstone, and have had enough of the crap IBurst service, I have 4 accounts, which I have setup for my family, myself and a firiend, I am now getting to the point of cancelling all 4 contracts as well as selling the modems, if anyone want modems please give me a call, I have had enough of this **** ! and to consider I am a reseller, veeryy sad.
 
Gatecrasher said:
If those were my regular pings I would be too embarrassed to post them here. They are just plain shocking. Basically, you are driving along in a car with slashed tyres, smashed windows, and a jammed gear box.... and yet you are still wondering wtf is wrong.

SIMPLE. YOUR CONNECTION IS BROKEN. GET IT FIXED. IF THEY CAN'T FIX IT, GIVE IT ALL BACK TO THEM AND GET A REFUND.

And Drastik, if this is your reality then the same advice applies.

Hi Gatecrasher,

January and February have been hell on the Northcliff tower - I must be a masochist to continue with iburst, but having bought the modem I have to stick around and wait for improvments.

The pings are good today (around 50/60 ms to 200 ms on the iburst website) but FTP still sucks (correction to previous post I am trying to upload a 1.3 MB) starting at 7 kbps and rapidly decreasing to 0.3-0.4 kbps for 90% of the uplaod.
 
Speed pinging from Northcliff

Fairlady;

I used the same IP that you used and ping it AFTER the firmware upgrade at Northcliff on Fri 11th.

Results:

Pinging 196.30.31.120 with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=257ms TTL=126
Reply from 196.30.31.120: bytes=32 time=101ms TTL=126
Reply from 196.30.31.120: bytes=32 time=366ms TTL=126
Reply from 196.30.31.120: bytes=32 time=105ms TTL=126
Reply from 196.30.31.120: bytes=32 time=2359ms TTL=126
Reply from 196.30.31.120: bytes=32 time=110ms TTL=126
Reply from 196.30.31.120: bytes=32 time=84ms TTL=126
Reply from 196.30.31.120: bytes=32 time=133ms TTL=126
Reply from 196.30.31.120: bytes=32 time=137ms TTL=126
Reply from 196.30.31.120: bytes=32 time=122ms TTL=126
Reply from 196.30.31.120: bytes=32 time=85ms TTL=126
Reply from 196.30.31.120: bytes=32 time=99ms TTL=126
Reply from 196.30.31.120: bytes=32 time=119ms TTL=126
Reply from 196.30.31.120: bytes=32 time=607ms TTL=126
Reply from 196.30.31.120: bytes=32 time=251ms TTL=126
Reply from 196.30.31.120: bytes=32 time=666ms TTL=126
Reply from 196.30.31.120: bytes=32 time=594ms TTL=126
Reply from 196.30.31.120: bytes=32 time=149ms TTL=126
Reply from 196.30.31.120: bytes=32 time=82ms TTL=126
Reply from 196.30.31.120: bytes=32 time=86ms TTL=126
Reply from 196.30.31.120: bytes=32 time=141ms TTL=126
Reply from 196.30.31.120: bytes=32 time=135ms TTL=126
Reply from 196.30.31.120: bytes=32 time=99ms TTL=126
Reply from 196.30.31.120: bytes=32 time=123ms TTL=126
Reply from 196.30.31.120: bytes=32 time=222ms TTL=126
Reply from 196.30.31.120: bytes=32 time=666ms TTL=126
Reply from 196.30.31.120: bytes=32 time=584ms TTL=126
Reply from 196.30.31.120: bytes=32 time=759ms TTL=126
Reply from 196.30.31.120: bytes=32 time=89ms TTL=126
Reply from 196.30.31.120: bytes=32 time=189ms TTL=126
Reply from 196.30.31.120: bytes=32 time=103ms TTL=126
Reply from 196.30.31.120: bytes=32 time=103ms TTL=126
Reply from 196.30.31.120: bytes=32 time=196ms TTL=126
Reply from 196.30.31.120: bytes=32 time=170ms TTL=126
Reply from 196.30.31.120: bytes=32 time=189ms TTL=126
Reply from 196.30.31.120: bytes=32 time=119ms TTL=126
Reply from 196.30.31.120: bytes=32 time=192ms TTL=126
Reply from 196.30.31.120: bytes=32 time=191ms TTL=126
Reply from 196.30.31.120: bytes=32 time=305ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1144ms TTL=126
Reply from 196.30.31.120: bytes=32 time=59ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1944ms TTL=126
Reply from 196.30.31.120: bytes=32 time=44ms TTL=126
Reply from 196.30.31.120: bytes=32 time=113ms TTL=126
Reply from 196.30.31.120: bytes=32 time=62ms TTL=126
Reply from 196.30.31.120: bytes=32 time=61ms TTL=126
Reply from 196.30.31.120: bytes=32 time=251ms TTL=126
Reply from 196.30.31.120: bytes=32 time=280ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1214ms TTL=126
Reply from 196.30.31.120: bytes=32 time=584ms TTL=126
Reply from 196.30.31.120: bytes=32 time=124ms TTL=126
Reply from 196.30.31.120: bytes=32 time=1413ms TTL=126
Reply from 196.30.31.120: bytes=32 time=119ms TTL=126
Reply from 196.30.31.120: bytes=32 time=117ms TTL=126
Reply from 196.30.31.120: bytes=32 time=181ms TTL=126
Ping statistics for 196.30.31.120:

Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 44ms, Maximum = 2359ms, Average = 341ms

KrazyKid
 
This is my ping results International and local:

Pinging [204.127.135.135] with 32 bytes ->bytes=32 time=527ms TTL=44
Pinging [204.127.135.135] with 32 bytes ->bytes=32 time=318ms TTL=44
Pinging [204.127.135.135] with 32 bytes ->bytes=32 time=499ms TTL=44
Pinging [207.155.252.37] with 32 bytes ->bytes=32 time=436ms TTL=235
Pinging [207.155.252.37] with 32 bytes ->bytes=32 time=474ms TTL=235
Pinging [207.155.252.37] with 32 bytes ->bytes=32 time=405ms TTL=235
Pinging [128.171.94.42] with 32 bytes ->bytes=32 time=406ms TTL=32
Pinging [128.171.94.42] with 32 bytes ->bytes=32 time=444ms TTL=32
Pinging [128.171.94.42] with 32 bytes ->bytes=32 time=723ms TTL=32
Pinging [196.30.31.120] with 32 bytes ->bytes=32 time=56ms TTL=126
Pinging [196.30.31.120] with 32 bytes ->bytes=32 time=162ms TTL=126
Pinging [196.30.31.120] with 32 bytes ->bytes=32 time=111ms TTL=126
Pinging [193.10.252.19] with 32 bytes ->bytes=32 time=516ms TTL=234
Pinging [193.10.252.19] with 32 bytes ->bytes=32 time=349ms TTL=234
Pinging [193.10.252.19] with 32 bytes ->bytes=32 time=540ms TTL=234
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=346ms TTL=48
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=387ms TTL=48
Pinging [63.217.30.70] with 32 bytes ->bytes=32 time=386ms TTL=48
Ping statistics for above hosts:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss)
Approximate round trip times (RTT) in milli-seconds:
Minimum = 56ms, Maximum = 723ms, Average = 393ms
 
Plz fix the Bryanston Tower...if it even exists. 10:45pm 12/03/2005 Slowburst screech to a halt - to much inconsistency. I know everybody is sick of pings - its the only way I can show whats going on. I see its redlighted on the network status page. Got all latest firmware and connect UTD via ethernet, for some reason its better than USB.

ping ww.saix.net

Pinging ww.saix.net [196.25.1.200] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 196.25.1.200: bytes=32 time=3264ms TTL=247
Request timed out.

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 3264ms, Maximum = 3264ms, Average = 3264ms

ping ww.google.com
Pinging ww.google.akadns.net [216.239.63.104] with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 216.239.63.104: bytes=32 time=828ms TTL=235
Reply from 216.239.63.104: bytes=32 time=2828ms TTL=235

Ping statistics for 216.239.63.104:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 828ms, Maximum = 2828ms, Average = 1828ms
 
Last edited:
aborg said:
Plz fix the Bryanston Tower... I see its redlighted on the network status page.

I doubt those pings are from the Bryanston Tower then, more likely you've been palmed off to some distant tower.

Anyway, 19 March is D-day for the Iburst Network. If your connection still sucks after the upgrades then I think you're gonna have to conclude that your connection sucks period.
 
thx noone - basically it means no speed, no service, no 24 month contract if this sh*t continues after the launch date.
Gatechrasher - Bryanston BS is the only one I can see, my signal strength is 100% all the time but that seems to mean sweet blue nothing concerning speeds.
 
I am flying

Hi guys.

Connected to Roodepoort tower. Suddenly Flying at 919kbps as per telkom speed test. Had a bit of down time today - they were probably doing some upgrades / updates :D
 
Sigh...

Look at this!! It's PATHETIC!! This is to iburst's site... wtf?!

Reply from 196.30.31.120: bytes=32 time=402ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1426ms TTL=125
Reply from 196.30.31.120: bytes=32 time=2279ms TTL=125
Reply from 196.30.31.120: bytes=32 time=2707ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1981ms TTL=125
Reply from 196.30.31.120: bytes=32 time=982ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1704ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1963ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1271ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1741ms TTL=125
Reply from 196.30.31.120: bytes=32 time=876ms TTL=125
Reply from 196.30.31.120: bytes=32 time=1342ms TTL=125

I've been disconnected like four times allready... T minus 16 days...
 
hentie said:
Hi guys.

Connected to Roodepoort tower. Suddenly Flying at 919kbps as per telkom speed test. Had a bit of down time today - they were probably doing some upgrades / updates :D

same thing happened when primrose went down give it a few hours then check speeds again pls let us (me) know if speeds stay up there as mine dipped a few hours later
 
Karel_01 said:
same thing happened when primrose went down give it a few hours then check speeds again pls let us (me) know if speeds stay up there as mine dipped a few hours later

You'r right, Later it did go down a bit, but not completely. I will check again this afternoon.

This means only one thing. There is nothing wrong with the signal strength to the tower (for me in any case), it is the background management of the bandwidth by I-burst that is the problem. Hopefully this is what they are adressing with their upgrades of software etc.
 
Thx Iburst - it seems that the speed is back at the Bryanston BS - 90.4 KB/s local speedtest and 35 KB/s international single thread - thats more like it. :-)
 
Been getting fairly constant downloading speeds of 120KB/s. Pretty good :D .
 
Raithlin said:
Can anyone explain this? Check last 24 hrs

My upload speed beats the crap out of my download speed... I feel sick. :(

Those upload speeds does not seem realistic using Iburst. Some mixup somewhere with your speed test? Upload traffic routed through a different connection?
 
Raithlin said:
Can anyone explain this? Check last 24 hrs

My upload speed beats the crap out of my download speed... I feel sick. :(
I agree that's very strange, perhaps the UT[D?] is saying I'm feeling all topsy-turvy, I want to be turned upside-down...:D
 
Top
Sign up to the MyBroadband newsletter
X