What could cause this?

R

Re83L

Expert Member
Joined
Mar 28, 2007
Messages
1,258
Reaction score
5
Location
Cape Town - Northern Suburbs
Hey guys, over the past couple of days, I've been getting minimum 90-95ms pings from South-African servers...
I've checked my incoming and outgoing connections with Netlimiter, and no program is using the web when I do my pings...

I used to get about 30-40ms up until a week ago.
As you guys could probably figure, this sucks for online gaming...:mad:

Could it be because I haven't verified my ADSL line yet?

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

Reply from 198.54.202.4: bytes=32 time=92ms TTL=244
Reply from 198.54.202.4: bytes=32 time=93ms TTL=244
Reply from 198.54.202.4: bytes=32 time=93ms TTL=244
Reply from 198.54.202.4: bytes=32 time=92ms TTL=244

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

Thanks for the help...
 
Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=96ms TTL=117
Reply from 196.2.63.110: bytes=32 time=95ms TTL=117
Reply from 196.2.63.110: bytes=32 time=91ms TTL=117
Reply from 196.2.63.110: bytes=32 time=93ms TTL=117

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

Same here :/ I used to get ~60ms. Only noticed it after reading your thread. I don't manually ping often. International pings are up too. ~405 used to be ~250

I'm on saix - mweb.
 
It might also be useful to mention : I'm in the Bloemfontein area (Langenhovenpark exchange)
I've got a SAIX account and a IS account, the ping stay up there (90ms) ,no matter which account I use to ping from...

All the other guys on the saix games servers' ping are still as they used to be, seems like it's only mine that's become unplayable...
 
Pinging www.mybroadband.co.za [196.40.97.12] with 32 bytes of data:

Reply from 196.40.97.12: bytes=32 time=96ms TTL=247
Reply from 196.40.97.12: bytes=32 time=96ms TTL=247
Reply from 196.40.97.12: bytes=32 time=95ms TTL=247
Reply from 196.40.97.12: bytes=32 time=94ms TTL=247

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


Pinging www.mweb.co.za [196.2.63.110] with 32 bytes of data:

Reply from 196.2.63.110: bytes=32 time=93ms TTL=117
Reply from 196.2.63.110: bytes=32 time=94ms TTL=117
Reply from 196.2.63.110: bytes=32 time=93ms TTL=117
Reply from 196.2.63.110: bytes=32 time=93ms TTL=117

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


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

Reply from 64.233.161.104: bytes=32 time=400ms TTL=242
Reply from 64.233.161.104: bytes=32 time=415ms TTL=242
Reply from 64.233.161.104: bytes=32 time=415ms TTL=242
Reply from 64.233.161.104: bytes=32 time=417ms TTL=242

Ping statistics for 64.233.161.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 400ms, Maximum = 417ms, Average = 411ms


Pinging www.amazon.co.uk [87.238.85.129] with 32 bytes of data:

Reply from 87.238.85.129: bytes=32 time=425ms TTL=241
Reply from 87.238.85.129: bytes=32 time=426ms TTL=241
Reply from 87.238.85.129: bytes=32 time=1239ms TTL=241
Reply from 87.238.85.129: bytes=32 time=835ms TTL=241

Ping statistics for 87.238.85.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 425ms, Maximum = 1239ms, Average = 731ms


I live near spar in LHP, so yes, also LHP exchange.
 
what it means is that your DSLAM was probably routed via a distant edge router instead of your previous router. This could be due to maintenance or upgrades etc. Unfortunately there is not much you can do... if it persists, call SAIX NNOC directly and ask what is up.

do a tracert games.saix.net and look for the edge router (something like nngy,rrba,wblv,ndn etc in the router name). that will give an indication if your traffic is being carried across the country before heading to the SGS server.. hope this helps
 
Cannot trace this network node
Cannot trace this network node
Cannot trace this network node
198.54.202.4 (ctb-cache3-vif1.saix.net) 95ms

:(
 
I was recently connecting through new germany but it seems my esr is now in Centurion (so no looping halfway across the country). So now my latency is nice and low (31ms avg) whereas it was higher previously...

I think you should just hang on, I dont think this rerouting across the country is a permanent thing.

tip: if you cant trace, do a trace to your IP address using services.truteq.com and post here
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X