LOW PINGS, Please advise

[UncleOswald]

Hi Everyone,

I live in Kensington, my UTD always shows full signal strength, downloading is always great and fast. Problem is that when I ping local sites, my responses are all over the place, ie in command prompt i type in....
ping -t www.iburst.co.za

the responses go like this

78ms
81ms
198ms
569ms
4487ms
46ms
158ms
198ms
78ms
71ms

Is there anyway to stabilize the conenction to give me a constant ping of under 100 ms?

I spoke to Shaun at wbs and all he suggested was that I lay out an additional 500bucks for an antenna, being in the telecommunications lien of work im doubtful that this will solve the issue. Any suggestions?

Many thanks in advance!

 

[ic]

IMO up & down latency has more to do with WBS' nazi shaping & contention at base-stations, than much to do with signal strength or even signal quality...

PS: UncleOswald, welcome to MyADSL .

 

[P0tenc]

What I see you paste there looks very familiar. In the beginning of the month I also got ping's of 3000 4000 while the rest was relativly low usually under 70ms peaking at 250.

I immediatly knew when this happened cause I could'nt play world of warcraft anymore, where i use to be able to play it fine. I emialed one of the techies he got back to me the next day and told me that ping's to my tower was fine, and it must therefore be a radio issue and he fowarded my querry to the radio team. 2 days later it was fixed and my pings were back to normal.

Don't even try phone the helpdesk they will only try change your mtu

 

[P0tenc]

IMO up & down latency has more to do with WBS' nazi shaping & contention at base-stations, than much to do with signal strength or even signal quality...

PS: UncleOswald, welcome to MyADSL .

True but a 4k latency ? with full signal strenght.....and other pings are low. I smell a rat. phone the helpdesk UncleOswald and ask for a techies email or one of the radio guy's.

Here's a example of my pings now-->
Reply from 196.30.31.120: bytes=32 time=81ms TTL=126
Reply from 196.30.31.120: bytes=32 time=48ms TTL=126
Reply from 196.30.31.120: bytes=32 time=113ms TTL=126
Reply from 196.30.31.120: bytes=32 time=67ms TTL=126
Reply from 196.30.31.120: bytes=32 time=41ms TTL=126
Reply from 196.30.31.120: bytes=32 time=43ms TTL=126
Reply from 196.30.31.120: bytes=32 time=114ms TTL=126
Reply from 196.30.31.120: bytes=32 time=136ms TTL=126
Reply from 196.30.31.120: bytes=32 time=66ms TTL=126
Reply from 196.30.31.120: bytes=32 time=59ms TTL=126
Reply from 196.30.31.120: bytes=32 time=91ms TTL=126
Reply from 196.30.31.120: bytes=32 time=71ms TTL=126
Reply from 196.30.31.120: bytes=32 time=58ms TTL=126
Reply from 196.30.31.120: bytes=32 time=60ms TTL=126
Reply from 196.30.31.120: bytes=32 time=59ms TTL=126
Reply from 196.30.31.120: bytes=32 time=58ms TTL=126

Also UncleOswald, have a look at your UTD while you ping www.iburst.co.za and pay attention to your signal strenght, check if a drop in signal coincides with a high ping. I experienced lots of loss in signal just for a second and then it would jump right back to full, and this for me atleast was when my pings were high. I am convinced that you have the same problem I had.

Hope you get it sorted soon

 

[UncleOswald]

Thanks!

Hi guys, thanks for the responses, please could you give em the email addy of the radio guys that sorted you out so I can ask them to do the same for me

 

[woobydog]

Also UncleOswald, have a look at your UTD while you ping www.iburst.co.za and pay attention to your signal strenght, check if a drop in signal coincides with a high ping. I experienced lots of loss in signal just for a second and then it would jump right back to full, and this for me atleast was when my pings were high. I am convinced that you have the same problem I had.

Hope you get it sorted soon

I have the same problem as this "any solutions" i phoned helpdesk who phoned me back 1/2 hour later and told me to move my external antenna around until the ping was stable.

 

[P0tenc]

Don't have the email addy anymore uncleoswald.....I got it from tshepo on helpdesk. (At least I think that was his name).

 

[UncleOswald]

roger that, thanks m8, have called the helpdesk and they said their manager will get one of the radio guys to contact me, will keep u all updated

 

[UncleOswald]

ATT POTenc

been running a test ping -t www.iburst.co.za -l 1 , ie pinging iburst with 1 byte, looking at the UTD as you suggested, 1 or 2 seconds before one of the disgusting(over 99ms) results theres a flickering of the green light, second from the bottom heres a result

Reply from 196.30.31.120: bytes=1 time=156ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=124ms TTL=126
Reply from 196.30.31.120: bytes=1 time=374ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=328ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=156ms TTL=126
Reply from 196.30.31.120: bytes=1 time=109ms TTL=126
Reply from 196.30.31.120: bytes=1 time=62ms TTL=126
Reply from 196.30.31.120: bytes=1 time=109ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=218ms TTL=126
Reply from 196.30.31.120: bytes=1 time=93ms TTL=126
Reply from 196.30.31.120: bytes=1 time=124ms TTL=126
Reply from 196.30.31.120: bytes=1 time=499ms TTL=126
Reply from 196.30.31.120: bytes=1 time=234ms TTL=126
Reply from 196.30.31.120: bytes=1 time=171ms TTL=126
Reply from 196.30.31.120: bytes=1 time=77ms TTL=126
Reply from 196.30.31.120: bytes=1 time=124ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=93ms TTL=126
Reply from 196.30.31.120: bytes=1 time=281ms TTL=126
Reply from 196.30.31.120: bytes=1 time=312ms TTL=126
Reply from 196.30.31.120: bytes=1 time=156ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=390ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=155ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=109ms TTL=126
Reply from 196.30.31.120: bytes=1 time=124ms TTL=126
Reply from 196.30.31.120: bytes=1 time=62ms TTL=126
Reply from 196.30.31.120: bytes=1 time=62ms TTL=126
Reply from 196.30.31.120: bytes=1 time=140ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=156ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=93ms TTL=126
Reply from 196.30.31.120: bytes=1 time=78ms TTL=126
Reply from 196.30.31.120: bytes=1 time=155ms TTL=126
Reply from 196.30.31.120: bytes=1 time=374ms TTL=126

There must be something making it go up and down like that, these pings are all over the place.

BTW, no one called me back from Iburst today

 

[jmn]

Flickering of the green light indicates traffic, watch the 5 signal strength LEDs above that one for changes.

 

[UncleOswald]

Green lights

no flicker at all in the green light, never ever, I have great signal, I think the radio guy idea is the only one left to me, if of course I can get hold of one

 

[Crash]

Well... if you have an electromagetic wave flying through the air, it's not gonna arrive at exactly the same time. It's the nature of wireless.

Here's my ping stats.

ping www.iburst.co.za -t

Pinging www.iburst.co.za [196.30.31.120] with 32 bytes o

Reply from 196.30.31.120: bytes=32 time=116ms TTL=126
Reply from 196.30.31.120: bytes=32 time=140ms TTL=126
Reply from 196.30.31.120: bytes=32 time=344ms TTL=126
Reply from 196.30.31.120: bytes=32 time=78ms TTL=126
Reply from 196.30.31.120: bytes=32 time=78ms TTL=126
Reply from 196.30.31.120: bytes=32 time=63ms TTL=126
Reply from 196.30.31.120: bytes=32 time=78ms TTL=126
Reply from 196.30.31.120: bytes=32 time=94ms TTL=126
Reply from 196.30.31.120: bytes=32 time=94ms TTL=126
Reply from 196.30.31.120: bytes=32 time=250ms TTL=126
Reply from 196.30.31.120: bytes=32 time=78ms TTL=126
Reply from 196.30.31.120: bytes=32 time=344ms TTL=126
Reply from 196.30.31.120: bytes=32 time=125ms TTL=126
Reply from 196.30.31.120: bytes=32 time=125ms TTL=126
Reply from 196.30.31.120: bytes=32 time=375ms TTL=126
Reply from 196.30.31.120: bytes=32 time=219ms TTL=126
Reply from 196.30.31.120: bytes=32 time=94ms TTL=126
Reply from 196.30.31.120: bytes=32 time=93ms TTL=126
Reply from 196.30.31.120: bytes=32 time=156ms TTL=126

Ping statistics for 196.30.31.120:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 375ms, Average = 154ms

This is about the norm for iBurst. Even during the Beta Network, the pings jumped around a bit.

 

[UncleOswald]

Sad

ouch! this isnt the toy for me then I think. I wanted to cancel with Iburst last month, but Phuleng there was so helpful and obliging that I decided to give them a concerted bash, but I think im going to have to go ahead and cancell, its a pity coz the company itself is great, but they seem to have mountains of tech morons. The system always works great for downloading, the speeds are phenomenal, but who really needs great download speed when theres a cap? I guess hellkom adsl in the only way to get the speeds I need

 

[Clipse]

Sorry, but what about the company is great uncleoswald?

Just very curious

 

[jmn]

Obviously not our uncle in the ISP business

 

[UncleOswald]

whats great...

well, I have a 2 year contract, but when I explained to Phuleng that it wasnt working for me and that I would need to cancel she didnt try strongarm me and obliged straight away. A company that can admit to its faults and to the fact that it isnt livign up to its clients expectations and which is prepared to call it quits with minimum stress to the client has to be respected.

Sentech would have my ass in court if I tried that. WBS are being very forthcoming and if ever they sort their issues out I would gladly rejoin