Ping saix.net

--- 196.25.1.200 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7006ms
rtt min/avg/max/mdev = 91.399/161.090/256.906/51.702 ms
 
bytes=32 time=564ms
bytes=32 time=489ms
bytes=32 time=345ms
bytes=32 time=467ms

thats wat i got. thats y i hate iburst
 
JasonH said:
Hi..

Can someone please ping saix.net from iBurst and post your results here

IP : 196.25.1.200

Thanks
Jason
Click to expand...

best of four packets or what you want?

Pinging 196.25.1.200 with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=212ms TTL=243
Reply from 196.25.1.200: bytes=32 time=119ms TTL=243
Reply from 196.25.1.200: bytes=32 time=114ms TTL=243
Reply from 196.25.1.200: bytes=32 time=105ms TTL=243

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 105ms, Maximum = 212ms, Average = 137ms
 
DaGGa BuNNy said:
bytes=32 time=564ms
bytes=32 time=489ms
bytes=32 time=345ms
bytes=32 time=467ms

thats wat i got. thats y i hate iburst
Click to expand...

Boet we in the same area. what gives? your antenna probably facing the wrong way or something else is wrong!:confused: Call your reseller.
 
Thanks Guys, Appriciate it :D

Averages or whatever i just want to see around what you get :(

See I was getting 60-90's until today.

Iburst.co.za is still 60-80ms but saix is 140ms +- :(

UUNET to Saix does this something but not for long periods seems like we have to wait till they fix :(
 
And i'm in the middle of bunny and Justin..

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

Reply from 196.25.1.200: bytes=32 time=295ms TTL=244
Reply from 196.25.1.200: bytes=32 time=174ms TTL=244
Reply from 196.25.1.200: bytes=32 time=238ms TTL=244
Reply from 196.25.1.200: bytes=32 time=152ms TTL=244
Reply from 196.25.1.200: bytes=32 time=216ms TTL=244
Reply from 196.25.1.200: bytes=32 time=380ms TTL=244
Reply from 196.25.1.200: bytes=32 time=300ms TTL=244
Reply from 196.25.1.200: bytes=32 time=109ms TTL=244
Reply from 196.25.1.200: bytes=32 time=177ms TTL=244
Reply from 196.25.1.200: bytes=32 time=165ms TTL=244
Reply from 196.25.1.200: bytes=32 time=153ms TTL=244
Reply from 196.25.1.200: bytes=32 time=191ms TTL=244
Reply from 196.25.1.200: bytes=32 time=195ms TTL=244
Reply from 196.25.1.200: bytes=32 time=185ms TTL=244
Reply from 196.25.1.200: bytes=32 time=174ms TTL=244

Ping statistics for 196.25.1.200:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 380ms, Average = 206ms
 
Also not doing too good for myself, but ive never tried anything for the sweetspot on my aerial, I left that to my reseller.

I thaught he knew what he was doing and I should leave it alone, but from what i remember, he didnt do too much hard work to find a sweet spot, plus he only checked speeds. I'll go mess around with it in my free time nxt week.
 
But Daggabunny, I dont remember your connection being this bad when i used it, it seemed a bit worse than mine, but you coul play battle.net dota's fine and mine lagged sometimes.

So is this refcent ting? the nsomething fixable must have gone wrong, maby ur UTD fuked out? I could come try mine over there.
 
----196.25.1.200 PING Statistics----
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms) min/avg/max = 80/122/180
 
odd this past week iburst has been up to crap. i usually got around 50-100ms to saix and about 300-500 to google.com . now look at this
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=527ms TTL=245
Reply from 196.25.1.200: bytes=32 time=398ms TTL=245
Reply from 196.25.1.200: bytes=32 time=585ms TTL=245
Reply from 196.25.1.200: bytes=32 time=444ms TTL=245

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 398ms, Maximum = 585ms, Average = 488ms
 
How close are you guys to your station because I'm about a km or 2 max away from mine and I get this

Reply from 196.25.1.200: bytes=32 time=349ms TTL=246
Reply from 196.25.1.200: bytes=32 time=342ms TTL=246
Reply from 196.25.1.200: bytes=32 time=481ms TTL=246
Reply from 196.25.1.200: bytes=32 time=377ms 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 = 342ms, Maximum = 481ms, Average = 387ms
 
It also depends when you are doing the test, huge difference in ping times during the day compared to at night.

I am 6km or so away with an antenna though, your pings should be better though if you are only 2km away. It could be a slightly congested tower during the day, but even then it is a bit high i geuss.

No idea why everyone is so interested in pinging saix.net anyway, that is the telkom netwrok there could be other problems causing bad pings are interconnections issues between SAIX and UUNET/IS.
rather ping 172.17.0.100 (iburst gateway, think i got it rite from memory...) for a more unbiased result to check your connection adn not the iburst connection to other servers.
 
Reply from 172.17.0.100: bytes=32 time=127ms TTL=246
Reply from 172.17.0.100: bytes=32 time=144ms TTL=246
Reply from 172.17.0.100: bytes=32 time=151ms TTL=246
Reply from 172.17.0.100: bytes=32 time=123ms TTL=246

Ping statistics for 172.17.0.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 123ms, Maximum = 151ms, Average = 136ms

Well that looks a little better:)
I'll try again later tonight and see how it does, I'm on the RandPark Ridge Tower and far as I know, it wasn't overloaded or at least I think it isn't:) oh well.
 
172.17.0.100 is only relavent if you live in CT, the gatewy for JHB is different. Do a tracert to any site, the first IP you get will be the iBurst gateway
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X