Iburst getting worse by the week

Isn’t Iburst part of some sort of franchise?
If so we can complaint to the big guys there, I’m sure they will be interested to know how the SA Iburst is dragging the general Iburst name thru the mud?
 
Pinging google.com [72.14.207.99] with 32 bytes of data:

Request timed out.
Reply from 72.14.207.99: bytes=32 time=538ms TTL=239
Reply from 72.14.207.99: bytes=32 time=527ms TTL=239
Reply from 72.14.207.99: bytes=32 time=535ms TTL=239
Reply from 72.14.207.99: bytes=32 time=578ms TTL=239
Reply from 72.14.207.99: bytes=32 time=566ms TTL=239
Reply from 72.14.207.99: bytes=32 time=534ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=538ms TTL=239
Reply from 72.14.207.99: bytes=32 time=571ms TTL=239
Request timed out.
Request timed out.
Reply from 72.14.207.99: bytes=32 time=524ms TTL=239
Reply from 72.14.207.99: bytes=32 time=581ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=674ms TTL=239
Reply from 72.14.207.99: bytes=32 time=552ms TTL=239

Ping statistics for 72.14.207.99:
Packets: Sent = 17, Received = 12, Lost = 5 (29% loss),
Approximate round trip times in milli-seconds:
Minimum = 524ms, Maximum = 674ms, Average = 559ms
 
Pinging 72.14.207.99 with 1 bytes of data:

Reply from 72.14.207.99: bytes=1 time=557ms TTL=240
Reply from 72.14.207.99: bytes=1 time=565ms TTL=240
Reply from 72.14.207.99: bytes=1 time=548ms TTL=240
Reply from 72.14.207.99: bytes=1 time=623ms TTL=240
Reply from 72.14.207.99: bytes=1 time=551ms TTL=240
Reply from 72.14.207.99: bytes=1 time=590ms TTL=240
Reply from 72.14.207.99: bytes=1 time=584ms TTL=240
Reply from 72.14.207.99: bytes=1 time=558ms TTL=240
Reply from 72.14.207.99: bytes=1 time=547ms TTL=240
Reply from 72.14.207.99: bytes=1 time=546ms TTL=240
Reply from 72.14.207.99: bytes=1 time=591ms TTL=240
Reply from 72.14.207.99: bytes=1 time=575ms TTL=240
Reply from 72.14.207.99: bytes=1 time=573ms TTL=240
Reply from 72.14.207.99: bytes=1 time=592ms TTL=240
Reply from 72.14.207.99: bytes=1 time=545ms TTL=240
Reply from 72.14.207.99: bytes=1 time=569ms TTL=240

Ping statistics for 72.14.207.99:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 545ms, Maximum = 623ms, Average = 569ms

Pinging 72.14.207.99 with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=558ms TTL=240
Reply from 72.14.207.99: bytes=32 time=542ms TTL=240
Reply from 72.14.207.99: bytes=32 time=546ms TTL=240
Reply from 72.14.207.99: bytes=32 time=546ms TTL=240
Reply from 72.14.207.99: bytes=32 time=535ms TTL=240
Reply from 72.14.207.99: bytes=32 time=554ms TTL=240
Reply from 72.14.207.99: bytes=32 time=558ms TTL=240
Reply from 72.14.207.99: bytes=32 time=552ms TTL=240
Reply from 72.14.207.99: bytes=32 time=556ms TTL=240
Reply from 72.14.207.99: bytes=32 time=609ms TTL=240
Reply from 72.14.207.99: bytes=32 time=553ms TTL=240
Reply from 72.14.207.99: bytes=32 time=571ms TTL=240
Reply from 72.14.207.99: bytes=32 time=545ms TTL=240
Reply from 72.14.207.99: bytes=32 time=545ms TTL=240
Reply from 72.14.207.99: bytes=32 time=550ms TTL=240
Reply from 72.14.207.99: bytes=32 time=564ms TTL=240

Ping statistics for 72.14.207.99:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 535ms, Maximum = 609ms, Average = 555ms
 
Last edited:
Date: 17/05/07
Incident: Connectivity Degradation
Estimated: Resolution17/05/07
Impact: All iBurst subscribers excluding Cape Town.
Priority: CRITICAL
Status: RESOLVED
Resolution: 17/05/07

Resolved? Really? Could have fooled me!! :confused:

Even accessing or posting on this forum has become a tedious task!! :mad:
 
Steinie said:
Date: 17/05/07
Incident: Connectivity Degradation . . .
Status: RESOLVED
. . .
Click to expand...
Agreed - blooming cr@p.
Have you noticed that they removed the "Speed Test" option from their website as well - only links are to the bandwidth monitor.
That's about as much of an admission of guilt as you'll ever get.

They've probably oversold their capacity.
 
Ping times not acceptable

Pinging 72.14.207.99 with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=681ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=666ms TTL=239
Reply from 72.14.207.99: bytes=32 time=565ms TTL=239
Reply from 72.14.207.99: bytes=32 time=529ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=740ms TTL=239
Reply from 72.14.207.99: bytes=32 time=663ms TTL=239
Reply from 72.14.207.99: bytes=32 time=511ms TTL=239
Reply from 72.14.207.99: bytes=32 time=605ms TTL=239
Reply from 72.14.207.99: bytes=32 time=514ms TTL=239
Reply from 72.14.207.99: bytes=32 time=638ms TTL=239
Reply from 72.14.207.99: bytes=32 time=552ms TTL=239
Reply from 72.14.207.99: bytes=32 time=716ms TTL=239
Request timed out.
Reply from 72.14.207.99: bytes=32 time=680ms TTL=239

Ping statistics for 72.14.207.99:
Packets: Sent = 16, Received = 13, Lost = 3 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 511ms, Maximum = 740ms, Average = 620ms
 
International slowest Ping Times

ping www.iburst.co.za -n 16
<SNIP>...</SNIP>
Ping statistics for 196.30.31.120:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 101ms, Average = 70ms

ping www.webmail.co.za -n 16
<SNIP>...</SNIP>
Ping statistics for 196.25.210.70:
Packets: Sent = 16, Received = 15, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 628ms, Average = 111ms


ping www.google.co.za -n 16
<SNIP>...</SNIP>
Ping statistics for 64.233.183.147:
Packets: Sent = 16, Received = 14, Lost = 2 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 519ms, Maximum = 2061ms, Average = 1283ms


ping www.serv.co.za -n 16 (USA Hosting)
Ping statistics for 209.31.112.18:
Packets: Sent = 16, Received = 11, Lost = 5 (31% loss),
Approximate round trip times in milli-seconds:
Minimum = 538ms, Maximum = 3654ms, Average = 1332ms

ping www.bbc.co.uk -n 16
Ping statistics for 212.58.240.110:
Packets: Sent = 16, Received = 11, Lost = 5 (31% loss),
Approximate round trip times in milli-seconds:
Minimum = 544ms, Maximum = 1964ms, Average = 814ms



Maybe it's only international that is slow / retarded / shaped ?
 
Methuselah said:
Agreed - blooming cr@p.
Have you noticed that they removed the "Speed Test" option from their website as well - only links are to the bandwidth monitor.
That's about as much of an admission of guilt as you'll ever get.

They've probably oversold their capacity.
Click to expand...

It's still there ... both under SALES and YOUR ACCOUNT in the Menu.

Just checked mine now. Download = 345!! :mad:

It's usually between 600 qnd 950!!

WTF is going on with "i-iBest"?? :confused:
 
Microsoft

Ping statistics for 207.46.197.32:
Packets: Sent = 13905, Received = 11751, Lost = 2154 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 386ms, Maximum = 1380ms, Average = 579ms

iBurst SMTP

Ping statistics for 196.30.31.207:
Packets: Sent = 18040, Received = 18014, Lost = 26 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 1184ms, Average = 99ms
 
They are shaping on PDFs at the mo as well. Have no problem with html, but as soon as I hit a pdf (which I really want), get the first page and it stops :sick:
 
Pinging 207.46.197.32 with 32 bytes of data:

Reply from 207.46.197.32: bytes=32 time=434ms TTL=108
Reply from 207.46.197.32: bytes=32 time=443ms TTL=108
Reply from 207.46.197.32: bytes=32 time=432ms TTL=108
Reply from 207.46.197.32: bytes=32 time=430ms TTL=109
Reply from 207.46.197.32: bytes=32 time=434ms TTL=108
Reply from 207.46.197.32: bytes=32 time=468ms TTL=109
Reply from 207.46.197.32: bytes=32 time=452ms TTL=108
Reply from 207.46.197.32: bytes=32 time=440ms TTL=109
Reply from 207.46.197.32: bytes=32 time=439ms TTL=109
Reply from 207.46.197.32: bytes=32 time=433ms TTL=109
Reply from 207.46.197.32: bytes=32 time=432ms TTL=108

Ping statistics for 207.46.197.32:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 430ms, Maximum = 468ms, Average = 439ms
 
BigAl-sa said:
They are shaping on PDFs at the mo as well. Have no problem with html, but as soon as I hit a pdf (which I really want), get the first page and it stops :sick:
Click to expand...
Interestingly, 5 mins after I posted this, I got the pdf at monumental download rates...
 
Seems iBurst has gone belly up in CT for the past hour I've had to change IP many times to even get it to browse, and downloading is completely "dead" my side.:mad:
 
Well it seems i am not only one having problems ..... who would have guessed. Well today my internation just went down and all they say is degraded now they say resolved well yeah they have managed to get international to same level as local which is not saying much, today i logged into a website then when i clicked to go to another page my account log in timed out before i got into website now as you can imagine not being able to download my work could be very annoying but i eventually got on without it timing out.

Well i seriously think its about time to just get rid of iburst unless its back to full speed by end of month.
 
Actually just need to add my point the only thing iburst has over other products is your bandwidth carryover but i would like to point out that it doesn't help when you can never even use up your full initial 3 gigs no matter how much you download because its all so shaped i just can't ever get downloads done, i did a 200meg p2p download over 3 months :( its a real long time to wait.
 
I'm still sad that I'm leaving iBurst after 3 years (been with them right from the start), but after testing an E220 Huawei modem at home (get 5 bars with Vodacom HSDPA! :)), I realised it's time to move on.

Tired of all the disconnects, no connections & slow speeds. Oh, and the mail server is also damn slow....
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X