more unreliability!!

J

jamieb

Well-Known Member
Joined
Dec 13, 2004
Messages
228
Reaction score
0
I haven't been able to work the ENTIRE day to the unreliability of the iBurst service. It amazing me that there are people still signing up to this service (if you can call it that).

See below.

Reply from 66.249.85.99: bytes=32 time=2125ms TTL=233
Reply from 66.249.85.99: bytes=32 time=673ms TTL=233
Reply from 66.249.85.99: bytes=32 time=656ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=899ms TTL=234
Reply from 66.249.85.99: bytes=32 time=768ms TTL=234
Reply from 66.249.85.99: bytes=32 time=644ms TTL=234
Reply from 66.249.85.99: bytes=32 time=969ms TTL=234
Reply from 66.249.85.99: bytes=32 time=1303ms TTL=234
Reply from 66.249.85.99: bytes=32 time=713ms TTL=234
 
Sandton / Rosebank Area

It appears WBS does not have adequate infrastructure in place to service users in Sandton / Rosebank. Our connection is speedy at night, yet during the day it crawls to snails pace (if you're lucky to have a connection at all).

I am so utterly frustrated. The people at iBurst have promised to send a technie around, no less than five times. Each time, no one pitched up. Instead, they keep telling you to change your MTU.... which I did loong time ago.

These guys basically have a license to print money with that broadband wireless license, YET they STILL cannot get it together. Another Sentech story.
 
With latency that bad, no matter how big your bandwidth pipe, web pages will take forever to load.

Take for example News24:
Total page size: 260K
Total HTTP requests: 45
Total time to initiate HTTP transfers: (45x2) = 90 seconds

So much then for broadband...
 
jamieb: what sites/downloads giving you trouble?

Anyone else in this area experiencing problems?
 
no it will take 2 seconds to initiate transfers because the latency time between point A and point B is 2000ms, however when the network is degraded to the point you have such bad latency then you cannot expect normal bandwith, so rather than having a 1mbit pipe for the moment he probably has a 20kbit pipe (just guessing on that one, could be any size)
 
slimothy said:
no it will take 2 seconds to initiate transfers because the latency time between point A and point B is 2000ms, however when the network is degraded to the point you have such bad latency then you cannot expect normal bandwith, so rather than having a 1mbit pipe for the moment he probably has a 20kbit pipe (just guessing on that one, could be any size)
Click to expand...
Sounds right
 
sites

Just about every site on the Internet is SLOW. i.e. finance.yahoo.com, www.google.com, etc.

Please iBurst do something ABOUT THIS.
 
In this sort of situation, Tyrone at WBS Helpdesk has taught me that
a) nothing's wrong with the network
b) if I dont tell anyone else, he'll send me his 'special' MTU settings which work really well for him.
c) I probably have spyware or a trojan on my PC
and
d) I'm the only one with a problem..

a possible shortcut can be phoning WBS office, and asking them to put you through to Dylan, NOT the helpdesk, but specifically Dylan - thus bypassing the endless waiting on hold - and making it his problem..?
 
Last edited:
iburst

Thanks for the suggestion. We've decided to leave iBurst permanently. I've given them six months to get their act together. Judging by past performance, I don't expect that the situation will improve further.


Reply from 66.249.85.99: bytes=32 time=538ms TTL=234
Request timed out.
Request timed out.
Reply from 66.249.85.99: bytes=32 time=549ms TTL=234
Reply from 66.249.85.99: bytes=32 time=455ms TTL=234
Reply from 66.249.85.99: bytes=32 time=834ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=757ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=828ms TTL=234
Reply from 66.249.85.99: bytes=32 time=526ms TTL=234
Reply from 66.249.85.99: bytes=32 time=565ms TTL=234
Reply from 66.249.85.99: bytes=32 time=750ms TTL=234
Reply from 66.249.85.99: bytes=32 time=496ms TTL=234
Reply from 66.249.85.99: bytes=32 time=494ms TTL=234
Reply from 66.249.85.99: bytes=32 time=636ms TTL=234
Reply from 66.249.85.99: bytes=32 time=547ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=992ms TTL=234
Request timed out.
Request timed out.
Reply from 66.249.85.99: bytes=32 time=589ms TTL=234
Reply from 66.249.85.99: bytes=32 time=767ms TTL=234
Reply from 66.249.85.99: bytes=32 time=510ms TTL=234
Reply from 66.249.85.99: bytes=32 time=530ms TTL=234
Reply from 66.249.85.99: bytes=32 time=725ms TTL=234
Reply from 66.249.85.99: bytes=32 time=495ms TTL=234
Reply from 66.249.85.99: bytes=32 time=567ms TTL=234
Reply from 66.249.85.99: bytes=32 time=511ms TTL=234
Reply from 66.249.85.99: bytes=32 time=765ms TTL=234
Reply from 66.249.85.99: bytes=32 time=1144ms TTL=23
Reply from 66.249.85.99: bytes=32 time=565ms TTL=234
Reply from 66.249.85.99: bytes=32 time=593ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=526ms TTL=234
Reply from 66.249.85.99: bytes=32 time=519ms TTL=234
Reply from 66.249.85.99: bytes=32 time=518ms TTL=234
Reply from 66.249.85.99: bytes=32 time=544ms TTL=234
Reply from 66.249.85.99: bytes=32 time=534ms TTL=234
Reply from 66.249.85.99: bytes=32 time=541ms TTL=234
Reply from 66.249.85.99: bytes=32 time=640ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=538ms TTL=234
Reply from 66.249.85.99: bytes=32 time=456ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=505ms TTL=234
Reply from 66.249.85.99: bytes=32 time=615ms TTL=234
Reply from 66.249.85.99: bytes=32 time=559ms TTL=234
Reply from 66.249.85.99: bytes=32 time=638ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=700ms TTL=234
Reply from 66.249.85.99: bytes=32 time=483ms TTL=234
Reply from 66.249.85.99: bytes=32 time=542ms TTL=234
Request timed out.
Reply from 66.249.85.99: bytes=32 time=729ms TTL=234
Reply from 66.249.85.99: bytes=32 time=767ms TTL=234
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X