Communication between WBS & iBurst Customers

[Shaun Green]

Contact Me

Could you please contact me in the morning, or the call centre manager, to look into your problem on the mail side.

When it comes to the bandwidth maybe others can be of assistance. Have check out a ADSL 512K connection. IBurst is definetly outperforming this by far. There seems to be a speed issue. Not as bad as the weekend and today, but it is there..... NOW TO IDENTIFY????????

Thank you

Shaun Green

 

[Shaun Green]

What kind of noise

I have sensitive ears.

I am here... Looking.... Reading..... Listening..... Assisting.... NOW WHAT OTHER INGS ARE THERE..

Just kidding.

Call me or the call centre manager. Would like to chat and find out what problems are effecting you.

Thanks In Advance

Shaun Green

 

[8321]

NOW WHAT OTHER INGS ARE THERE..

Serving, Responding, Managing, Facilitating, for a start. Good to have you on board.

 

[Shaun Green]

Sense of humour

Needed.

Thanks for the welcome.

Keep the humour coming too. My prozac budget is hitting the ceiling.

Keep the speed.

Shaun Green

 

[8321]

Shaun, 1stly welcome to the iBurst forum, I hope you stick around, and thank you for this thread & your posts.

Have a look at the tremendous effort Vodacom 3G put into communicating with the real world, elsewhere in this forum as a goal.

 

[sihen]

current speeds on Sanfton tower at 00:06

Bandwidth: (Current Downstream: 117.91kb/s ¤ Current Upstream: 10.09kb/s)
Bandwidth: (Current Downstream: 126.57kb/s ¤ Current Upstream: 7.2kb/s)

 

[sihen]

Ping statistics for 196.4.160.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 102ms, Average = 73ms

 

[Ravilj]

1st set

Pinging 196.30.31.120 with 32 bytes of data:

Request timed out.
Reply from 196.30.31.120: bytes=32 time=117ms TTL=126
Reply from 196.30.31.120: bytes=32 time=45ms TTL=126
Reply from 196.30.31.120: bytes=32 time=75ms TTL=126

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 117ms, Average = 79ms

2nd set

Pinging 196.30.31.120 with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=377ms TTL=126
Reply from 196.30.31.120: bytes=32 time=105ms TTL=126
Reply from 196.30.31.120: bytes=32 time=95ms TTL=126
Reply from 196.30.31.120: bytes=32 time=44ms TTL=126

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 377ms, Average = 155ms

3rd set

Pinging 196.30.31.120 with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=62ms TTL=126
Reply from 196.30.31.120: bytes=32 time=58ms TTL=126
Reply from 196.30.31.120: bytes=32 time=67ms TTL=126
Reply from 196.30.31.120: bytes=32 time=64ms TTL=126

Ping statistics for 196.30.31.120:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 67ms, Average = 62ms

I am also on the Bryanston Tower on the Sandton side.

 

[Ravilj]

I dont call the help desk anymore, I get more information from calling telkom :/

 

[alchamy]

Ok Mine looks something like this

Local Speeds are good

Your line speed is approximately 1261.2 Kbps or 154.6 kBytes/sec (Telkom Test)

Reply from 196.25.1.200: bytes=32 time=88ms TTL=246
Reply from 196.25.1.200: bytes=32 time=88ms TTL=246
Reply from 196.25.1.200: bytes=32 time=95ms TTL=246
Reply from 196.25.1.200: bytes=32 time=92ms TTL=246

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 95ms, Average = 90ms

International I am afraid is still terrible

running 10s inbound test (server to client) . . . . . . 16.20kb/s (Stanford Test)

Reply from 64.233.187.99: bytes=32 time=1229ms TTL=232
Reply from 64.233.187.99: bytes=32 time=2909ms TTL=232
Request timed out.
Reply from 64.233.187.99: bytes=32 time=1124ms TTL=232

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1124ms, Maximum = 2909ms, Average = 1754ms

 

[alchamy]

[RANT]

ic, I see your ranting and I need to do the same, saving the most of it for a visit to the offices but here are a few of my thoughts. These add onto what you have said, not going to quote it due to size. Apologies to those that have not yet discovered the wonder of firefox and tabbed browsing

a. It might be better if they listened to us when we say we have problems with a tower, rather then giving the standard "its perfect on our side". And 4 days down the line figuring out that something is wrong with the tower.

b. Judging by Sasans comments in the ITWEB article I do suspect that he still feels this way. However the article did stir the cauldron enough to get Shaun here and I noticed a post from Dylan as well (first post in ages and it was useless)

c.Do not get me started on the speed issues, however I will mention one thing again, "towers limited to 24Mbit".

d.Erm, on that note the IVR has a option for network status, I pressed 1 and it told me where the new towers are, I phoned the helpdesk not the salesdesk I dont need the IVR telling me about coverage when 90% of the users are unable to connect

e. Agreed, I am a bit tired of speaking to Luis each time and getting told, "its because your so far from the tower" Then 4 days/20 phonecalls later "We have found a problem with that tower" For the record I get download rates higher than advertised when it works, my signal is fine. Find another excuse for your incompetance.

f. Mailed WBS twice wrt this issue, no reply

ok, onto the MTU story, another magic answer from the helpdesk, you tell them that you have no signal and they rattle off for 10 minutes trying to explain MTU changes. I have no signal its like trying to make a phonecall without the line plugged in.

I agree with ic, need to get some answers regarding speed issues, anything less than advertised is not acceptable. I can understand international dropping 10% below advertised nothing more.

Futhermore, the question of antennas, when will they be available, do you plan to make 300% profit on them as with the modems? Since I have had iburst each time I ask the helpdesk tells me 2 weeks, been 7 sets of 2 weeks already.

Last thing, heard rumours of a transparent proxy, please comment on this.

[/RANT]

 

[guest2013-1]

4 pings quite doesnt do it. I experience alot of loss on the northcliff one :

Ping statistics for 196.30.31.120:
Packets: Sent = 22553, Received = 20694, Lost = 1859 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 4485ms, Average = 150ms

Thats with random disconnecting several times during the evening.

I did some tests on my own, download international single threaded : 15.06kb/s average (never going higher) Local single threaded download at 86kb/s average, never going higher.

Multithreaded international download, 72kb/s, very spikey/unstable. Not what I'm used to.

These tests have been done off HTTP/FTP on SAIX (Telkom) and my own server in the US on a 100 meg backbone. (so yes, no one truely uses it, da dum dish)

Sandton might be looking up, but definately not Northcliff

 

[twixt]

Re: Ping Results

Ping statistics for 216.239.57.99:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 383ms, Maximum = 470ms, Average = 409ms

Btw that's google.com.

Pings seem pretty good and reliable to me as opposed to the travesty that was this weekend. I am still not getting massive bandwith though - about 100kbs international. On the other hand at the moment I am mostly using the iburst for playing WoW atm - which doesn't require high bandwith just good pings and it played very smoothly last night.

Current Tower = North Ridge (Durban)

 

[kaspaas]

Hi,

I know there are many lurkers amazed that one can get more than 4 pings from a MS-Win machine.

The trick is to add -t to the ping statement

eg. ping -t www.iburst.co.za

Another command for the not-so-techinical inclined is

tracert www.iburst.co.za that will return some information about the route the data packets take - and the time it takes to hop from the start (your PC) to the node. This helps in identifying bottlenecks.

If this does initially not make sense, just keep trying - the numbers will start speaking to you after a few attempts!

 

[kaspaas]

Could you please contact me in the morning, or the call centre manager, to look into your problem on the mail side.

<cut a few words>

Shaun Green

According to the IT-Web article iBurst technicians should have stampeded to the poor critters that are having problems... No need for them to call iBurst again!

Sorry Shaun, I know you are trying your best. Please tell the "mouths" at iBurst how the users outside interpret what they are saying.

What we don't need is a Sentech clone. Your presense here makes a big difference in the perception of iBurst's clientcare.

 

[Crash]

Feel the Packet Loss

Right... my turn to post some pings. <crash cracks his fingers>

Pinging www.is.co.za [196.35.72.14] with 32 bytes of data:

Reply from 196.35.72.14: bytes=32 time=103ms TTL=117
Reply from 196.35.72.14: bytes=32 time=119ms TTL=117
Reply from 196.35.72.14: bytes=32 time=143ms TTL=117
Reply from 196.35.72.14: bytes=32 time=86ms TTL=117
Reply from 196.35.72.14: bytes=32 time=120ms TTL=117
Reply from 196.35.72.14: bytes=32 time=90ms TTL=117
Reply from 196.35.72.14: bytes=32 time=84ms TTL=117
Reply from 196.35.72.14: bytes=32 time=46ms TTL=117
Reply from 196.35.72.14: bytes=32 time=98ms TTL=117
Reply from 196.35.72.14: bytes=32 time=101ms TTL=117
Reply from 196.35.72.14: bytes=32 time=102ms TTL=117
Reply from 196.35.72.14: bytes=32 time=87ms TTL=117
Reply from 196.35.72.14: bytes=32 time=51ms TTL=117
Reply from 196.35.72.14: bytes=32 time=45ms TTL=117
Reply from 196.35.72.14: bytes=32 time=247ms TTL=117
Request timed out.
Request timed out.
Reply from 196.35.72.14: bytes=32 time=93ms TTL=117
Reply from 196.35.72.14: bytes=32 time=159ms TTL=117
Reply from 196.35.72.14: bytes=32 time=423ms TTL=117
Request timed out.
Reply from 196.35.72.14: bytes=32 time=181ms TTL=117
Reply from 196.35.72.14: bytes=32 time=191ms TTL=117
Reply from 196.35.72.14: bytes=32 time=176ms TTL=117
Request timed out.
Reply from 196.35.72.14: bytes=32 time=170ms TTL=117
Reply from 196.35.72.14: bytes=32 time=104ms TTL=117
Request timed out.
Reply from 196.35.72.14: bytes=32 time=141ms TTL=117
Reply from 196.35.72.14: bytes=32 time=168ms TTL=117
Reply from 196.35.72.14: bytes=32 time=103ms TTL=117
Reply from 196.35.72.14: bytes=32 time=52ms TTL=117
Reply from 196.35.72.14: bytes=32 time=189ms TTL=117

Ping statistics for 196.35.72.14:
Packets: Sent = 33, Received = 28, Lost = 5 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 423ms, Average = 131ms

If Sihen or Shaun would kindly ask a Radio Engineer to check this out please. Packet loss is affecting my UT2k4 games....

It happens all the time... no particular weather pattern. The UTD sometimes does the "Deranged Traffic Light Thang".... i.e signal jumps from between 20% and 100% quite rapidly... I move the modem maybe 1m and the signal stabilises. Goes funny... move modem, signal stabilises..... I think you get the idea.

BTW.... I can't get to Iburst.co.za this morning either.....

I connect to the Dredded Northcliff Tower.

 

[Shaun Green]

Connecting to IBurst

Hi there.. have just connected to Iburst.co.za.

Will contact Sihen to get more info on your ping/signal problem.

Later in this week i will be going to Northcliff for a while to test out my
UTC on the connection status there.

Thank you for the feedback.

Shaun Green

 

[guest2013-1]

Thanks Shaun, just some comparitive speed tests, I'm in Bedfordview at this moment, single threaded download international is 40kb/s average and 118kb/s average on multithreaded. Didn't test local as I'm sure that is on par.

Not doing any ping type tests.

 

[Shaun Green]

Wow

Quite a lot to look into here. Please give me a while to sort through it all and respond in an organised fashion. My response to the forum being around and the responses from the community is summed up in one word "GREAT".

I have discovered that this is a great way to get feedback on the pro's and con's in the community.

This is definetly not a minority that i will ignore. Any feedback is appreciated.

Thank you all

Shaun Green

 

[TheRoDent]

How about instead of trying to pacify people with how good it works for you, you start talking about how you're going to refund them for this crap they've been experiencing.

I'm sure that'll be a lot more welcome than excuses about how "you're working on it"...