Pinging results

Tjorriemorrie

Well-Known Member
Joined
Apr 26, 2006
Messages
316
Reaction score
0
I started to note down my pinging results. I used the average over 30 pings.

Here it is. Clearly some days are just bad days... :(

I think from today i'll start using the speedtest and record my speeds everyday. and of course the qos...
 
My pings recently got alot better and more stable. Im averaging around 80ms during the day to myadsl.co.za, but with spikes that would kick the uaverage to almost 100ms.

But watch out for when you record those results, youve got to make shure its at the same time, otherwise it will obviously be very different.
 
Nice graph ,Tjorriemorrie!

30 Pings to Iburst:

Code:
Pinging www.iburst.co.za [196.30.31.120] with 32 bytes of data:

Reply from 196.30.31.120: bytes=32 time=68ms TTL=125
Reply from 196.30.31.120: bytes=32 time=93ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=218ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=140ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=93ms TTL=125
Reply from 196.30.31.120: bytes=32 time=156ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=109ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125
Reply from 196.30.31.120: bytes=32 time=62ms TTL=125
Reply from 196.30.31.120: bytes=32 time=140ms TTL=125
Reply from 196.30.31.120: bytes=32 time=78ms TTL=125

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

30 pings to Google

Code:
Pinging www.l.google.com [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=347ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=374ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=375ms TTL=234
Reply from 64.233.187.99: bytes=32 time=531ms TTL=234
Reply from 64.233.187.99: bytes=32 time=375ms TTL=234
Reply from 64.233.187.99: bytes=32 time=375ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=421ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=421ms TTL=234
Reply from 64.233.187.99: bytes=32 time=359ms TTL=234
Reply from 64.233.187.99: bytes=32 time=375ms TTL=234
Reply from 64.233.187.99: bytes=32 time=390ms TTL=234
Reply from 64.233.187.99: bytes=32 time=453ms TTL=234
Reply from 64.233.187.99: bytes=32 time=375ms TTL=234

Ping statistics for 64.233.187.99:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 347ms, Maximum = 531ms, Average = 380ms
 
Damn Gatecrasher.. while your pings to iburst are closer to mine, those pings to google are way better.

I think you guys in jhb are just closer to things... you seem to always have a better international ping.

Myadsl is better for me as im not in joburg where Iburst servers are.

Pinging www.mybroadband.co.za [196.7.147.186] with 32 bytes of data:

Reply from 196.7.147.186: bytes=32 time=51ms TTL=249
Reply from 196.7.147.186: bytes=32 time=71ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=76ms TTL=249
Reply from 196.7.147.186: bytes=32 time=95ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=70ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249
Reply from 196.7.147.186: bytes=32 time=75ms TTL=249

Ping statistics for 196.7.147.186:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 95ms, Average = 74ms

Okay at the moment these look about as stable as ADSL pings. Like I said, something has become alot better for me in the las tfew days as far as pings go.


Pinging www.l.google.com [64.233.179.99] with 32 bytes of data:

Reply from 64.233.179.99: bytes=32 time=531ms TTL=238
Reply from 64.233.179.99: bytes=32 time=557ms TTL=239
Reply from 64.233.179.99: bytes=32 time=557ms TTL=238
Reply from 64.233.179.99: bytes=32 time=558ms TTL=239
Reply from 64.233.179.99: bytes=32 time=568ms TTL=239
Reply from 64.233.179.99: bytes=32 time=558ms TTL=238
Reply from 64.233.179.99: bytes=32 time=557ms TTL=239
Reply from 64.233.179.99: bytes=32 time=558ms TTL=238
Reply from 64.233.179.99: bytes=32 time=587ms TTL=239
Reply from 64.233.179.99: bytes=32 time=558ms TTL=238
Reply from 64.233.179.99: bytes=32 time=552ms TTL=239
Reply from 64.233.179.99: bytes=32 time=553ms TTL=238
Reply from 64.233.179.99: bytes=32 time=558ms TTL=238
Reply from 64.233.179.99: bytes=32 time=557ms TTL=239
Reply from 64.233.179.99: bytes=32 time=552ms TTL=238
Reply from 64.233.179.99: bytes=32 time=557ms TTL=239
Reply from 64.233.179.99: bytes=32 time=578ms TTL=238
Reply from 64.233.179.99: bytes=32 time=577ms TTL=239
Reply from 64.233.179.99: bytes=32 time=567ms TTL=238
Reply from 64.233.179.99: bytes=32 time=562ms TTL=239

Ping statistics for 64.233.179.99:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 531ms, Maximum = 587ms, Average = 560ms

Now at the same time I can keep up teh stability for international, but the numbers are simply about 200ms higher than you guys. It irritates me, becuase that is what makes browsing feel slow, not speed or anything.
 
My pings recently got alot better and more stable. Im averaging around 80ms during the day to myadsl.co.za, but with spikes that would kick the uaverage to almost 100ms.

But watch out for when you record those results, youve got to make shure its at the same time, otherwise it will obviously be very different.

I realised that when i started, so i did it when i got home. so i did it at around 5-6 in the evenings.
 
Top
Sign up to the MyBroadband newsletter
X