Weird ping behaviour

aktor

Senior Member
Joined
Mar 27, 2009
Messages
841
Reaction score
18
Location
Cape Town
Hi guys,

Experiencing some really weird ping behaviour the last couple of days. I'm on MWeb Uncapped (but I also tried on my Afrihost cap-based account with the same results).

When I ping a local site, for instance www.take2.co.za, I get:

Pinging www.take2.co.za [196.33.12.47] with 32 bytes of data:
Reply from 196.33.12.47: bytes=32 time=13ms TTL=58
Reply from 196.33.12.47: bytes=32 time=13ms TTL=58
Reply from 196.33.12.47: bytes=32 time=13ms TTL=58
Reply from 196.33.12.47: bytes=32 time=12ms TTL=58

Same for www.mweb.co.za:

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=13ms TTL=118
Reply from 196.2.63.110: bytes=32 time=13ms TTL=118
Reply from 196.2.63.110: bytes=32 time=12ms TTL=118
Reply from 196.2.63.110: bytes=32 time=13ms TTL=118

But when I ping games.saix.net, I get:

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250

Also, my ping in CoDMW2 and BFBC2 are 35ish. Normal, in other words.

Anyone know what could be causing this? That 12ms can't be right, sometimes it's even as low as 9ms.
 
You're lucky to get such low ping values. The latencies would vary a lot depending on the location (and ISP) of the destination server you're trying to access.

I got 35ms avg to www.take2.co.za / www.aardvark.co.za when using Afrihost Uncapped or OpenWeb 30GB IS Local Only, however when I used my OpenWeb 1GB Prepaid Local Only, I got 13ms to www.take2.co.za, and 35ms to www.aardvark.co.za.
 
Strange thing is though, I never used to get low latencies like that - it's a recent thing. Isn't it impossible to get 9ms to a local site though? 9ms to the exchange maybe, but to the webserver in another city?

Another thing, btw - anyone else getting higher than normal latencies internationally? In WoW specifically?
 
9ms is definitely possible. I've played CS1.6 online with people getting latencies lower than 10ms all the time!

Since the whole Free the Web launch, my latencies seem to change dramatically throughout the day. Like last night at 23:00, my latencies was about 140ms instead of the usual 40ms!
 
My high international latencies happen pretty much all the time - I used to get about 300ms in WoW using SmoothPing, now it's up to 400. Not horrible, but still higher than it used to be a few days ago. As for the local latencies, they're fine for the most part, BUT they do spike alot. For instance, it'd be solid at 35ms then suddenly spike to 250 or so, and come back down again. If it's a known issue I'm not really worried, I'm just concerned it could be something on my side.
 
I've been experiencing fluctuating pings recently as well. Where I would usually get 30-40ms ping, I'm get 60-100ms. It's extremely noticeable if you play online.

I'm using Axxess Express.
 
They probably upgraded the exchange and switched over to fibre.
In my area, there was a cable fault (fibre line got damaged) and they switched us to some sort of backup line....pings went from 15ms to 40ms....
Then later on they switched back to fibre (months later sigh...) and it went back to 15.

As for getting 9ms...u lucky little s****. :)
 
But then, I get results like these:

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=108ms TTL=118
Reply from 196.2.63.110: bytes=32 time=120ms TTL=118
Reply from 196.2.63.110: bytes=32 time=32ms TTL=118
Reply from 196.2.63.110: bytes=32 time=12ms TTL=118

Oh joy.
Could be a problem with the exchange uplink, actually.
 
You think that's bad?

Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=150ms TTL=107
Reply from 196.2.63.110: bytes=32 time=172ms TTL=107
Reply from 196.2.63.110: bytes=32 time=196ms TTL=107
Reply from 196.2.63.110: bytes=32 time=154ms TTL=107
 
Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=170ms TTL=47
Reply from 196.2.63.110: bytes=32 time=187ms TTL=47
Reply from 196.2.63.110: bytes=32 time=171ms TTL=47
Reply from 196.2.63.110: bytes=32 time=187ms TTL=47

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 170ms, Maximum = 187ms, Average = 178ms

Gota love it......... :(
 
Pinging mweb.co.za [196.2.63.110] with 32 bytes of data:
Reply from 196.2.63.110: bytes=32 time=80ms TTL=109
Reply from 196.2.63.110: bytes=32 time=88ms TTL=109
Reply from 196.2.63.110: bytes=32 time=102ms TTL=109
Reply from 196.2.63.110: bytes=32 time=122ms TTL=109

Ping statistics for 196.2.63.110:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 122ms, Average = 98ms


Pinging take2.co.za [196.33.12.47] with 32 bytes of data:
Reply from 196.33.12.47: bytes=32 time=182ms TTL=53
Reply from 196.33.12.47: bytes=32 time=171ms TTL=53
Reply from 196.33.12.47: bytes=32 time=169ms TTL=53
Reply from 196.33.12.47: bytes=32 time=151ms TTL=53

Ping statistics for 196.33.12.47:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 182ms, Average = 168ms
 
Well tomorrow mweb is gona have one less client.
 
It's not specifically just MWeb, I got the same on Afrihost a few minutes ago.
 
SO capped is the way to go for lower pings....always a bitter aftertaste with this lot
 
Nope, I have the same bad ping problems on capped accounts on both Afrishost and Telkom tonight, its terrible!
 
Yeah, confirmed with both Afrihost and Imaginet capped accounts as well, now.
 
Top
Sign up to the MyBroadband newsletter
X