My Ping..

R

Re83L

Expert Member
Joined
Mar 28, 2007
Messages
1,258
Reaction score
5
Location
Cape Town - Northern Suburbs
Hi guys, a while back I had a problem with my ingame pings (to the SGS server) firstly being routed through Bellville (I'm in Bloem, and the SGS games server is in Centurion...), and secondly, my pings overnight changed to 110ms.

So : I went to my TelkomDirect outet, k@kd on peoples heads for nearly four hours, reported my line as faulty, and phoned everyone from Telkom's specialist to IPnet (their department that handles how the routing gets done).

A few days later, my ping was back to 50ms.(While still being routed through Belville)

It stayed like that for a month or so, and last week it shot up to +-110ms again.

Now : A guy I know that's also playing on the servers is currently playing on iBurst, and his pings are very similar to mine...

Is there any way that Telscum might be routing me through a satellite link or something?

Also :
1. If any of you know who I can call/speak to to find out what's wrong with my line it'd be much appreciated.
2. I've heard something about being able to sign up with Telkom as a Stockbroker and being ensured the lowest pings possible... Is that true?
 
If it was going through a satellite link then your pings would be 500ms+

If i have tried to ask about anything like that before to telkom, i get the "its a best effort service" answer :)
 
Frag..finally a response from you again. I thought you moved away or something. My ping got better a while back..but the past 1.5 weeks I have to cope with the following nonsense:

SAIX account:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 88 ms 89 ms 89 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
3 89 ms 89 ms 89 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

IS Account:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 71 ms 69 ms 69 ms 196.38.73.169
3 73 ms 73 ms 72 ms curp4-rba-gi2.isdsl.net [196.38.73.114]
4 71 ms 70 ms 71 ms cdsl1-rba-gi0-1-50-curp4-internal.isdsl.net [196
.38.73.109]
5 73 ms 72 ms 72 ms 196.26.96.203
6 281 ms 70 ms 72 ms 196.26.0.250
7 74 ms 72 ms 72 ms 168.209.86.166
8 73 ms 72 ms 72 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127
.181]
9 72 ms 72 ms 71 ms 196.43.25.137
10 92 ms 93 ms 95 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
11 96 ms 97 ms 93 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

My ingame ping is anything between 70 - 95ms. If I read correctly, your ping is horrible once again ?? How did you manage to rectify your ping that your ping got back to 50ms ? Was it because of the folks you phoned at IPnet, cause then I would like to phone them as well.

What I cant understand is how my friend, that lives in Universitas gets the following:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms login.router [10.0.0.2]
2 * * * Request timed out.
3 48 ms 49 ms 50 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
4 49 ms 50 ms 51 ms saix.net [196.25.1.200]

Trace complete.

At his fourth route, he gets routed via saix.net ? whereas I get routed via wblv-ip-www-1.saix.net. How the hell is it possible that he gets those type of pings ? is it because he gets route via saix.net ??

Both me and him are on 384k connections, and his ingame ping gets as low as 25ms !

Can an overloaded exchange also have an impact on increasing ping times ? I am really gatvol at having to cope with this nonsense !!!!

Let me know, what I can do about improving my situation.

Thanks
 
Hey, yeah, I was at the Telkom office for four hours after we last spoke, reported a line fault, etc etc...

The people at IPnet told me that Telkom doesn't guarantee pingtimes...
The idiots at Telkom's fault reporting service told me that I can't report a fault on a line that's working...
The Telkom specialist that I spoke with told me that there's nothing wrong with our DSLAM (apparantly you can load about 9000KB/s on every DSLAM and LHP is currently using only 2000KB/s)
Anyways, I have a friend in Heuwelsig that's also got ingame pings of 25ms, it sucks.

Me and my flatmate is going to p00p on the heads of Telkom again, I honestly don't know why our pings got better last time - the fault I reported came up fine (and we were still being routed via Bellville, it just miraculously got fixed about five days after I spoke with Telkom)
 
Hey StoneCold, I was at the Telkom shop again yesterday, called a specialist and finally someone at IPnet, seems like our ping has gone back to 50ms :) Yay!!!
 
That's good news Frag, I saw my ingame ping dropped down to 50ms - 65ms, so thats an improvement. I dont know if the fact that you had went and seen them had anything to do with my latency improvement ? If it did , thanx a lot then.

Are u still being routed via Belville ?? my results as follows:

IS Account:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 46 ms 47 ms 48 ms 196.38.73.169
3 51 ms 49 ms 49 ms curp4-rba-gi2.isdsl.net [196.38.73.114]
4 46 ms 47 ms 48 ms cdsl1-rba-gi0-1-50-curp4-internal.isdsl.net [196
.38.73.109]
5 49 ms 50 ms 48 ms 196.26.96.203
6 49 ms 49 ms 50 ms 196.26.0.250
7 49 ms 48 ms 49 ms 168.209.86.166
8 48 ms 49 ms 48 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127
.181]
9 48 ms 49 ms 49 ms 196.43.25.137
10 73 ms 73 ms 70 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
11 71 ms 72 ms 71 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

SAIX account:

Tracing route to saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 68 ms 67 ms 66 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
3 68 ms 69 ms 68 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

I know it can go down even more, the best ping tests I got was around 58ms...
 
Yes, I finally was refered to a guy called Derek who works at IPNet, he told me that I was supposed to be routed through Roodepoort, so I told him we weren't...

He saw that there was a conflict in their system, and re-adjusted the Router at Bellvilles settings to throw us back to Roodepoort if we connect...
(Thus, in effect : It'll still seems to us asif we're routed through Bellville, but they changed something so that we get routed to Roodepoort instead... Dunno why we're still getting the route through Bellville?)
 
LOL.. thats really weird man. I just hope it holds up, still can't understand why you and I must get the short end of the stick. Anyhow, keep me posted if you get any problems again, and I'll verify if I get the same.

Thanks alot for all your effort so far with regards to fixing things for us at our exchange. :)

PS: I know three other guys in Bloem that also play online. Will ask them to send me some tracert results as well. Just wana see where they get routed through...

PPS: Is your ingame ping at the 50-55ms mark ?
 
Last edited:
StoneCold said:
PS: I know three other guys in Bloem that also play online. Will ask them to send me some tracert results as well. Just wana see where they get routed through...

PPS: Is your ingame ping at the 50-55ms mark ?
Click to expand...

LOL, I'm just glad we could find the problem... I know Heuwelsig has pings of about 25ms, and they're also routed through wblv...

And I know of one other guy that plays COD aswell...
BTW, which games do you play again?
If you pm me your msn we could maybe stay in touch?
 
Leno said:
If it was going through a satellite link then your pings would be 500ms+

If i have tried to ask about anything like that before to telkom, i get the "its a best effort service" answer :)
Click to expand...

yeah, sat would be very very high... This is telkom end month syndrome :rolleyes:
 
I did a trace report for saix.net... but one thing sticks out...Mauritius :confused:

ummm any explanations ?

Report for saix.net [196.25.1.200]

This trace was started on Jul 3, 2007 7:31:23 PM. The host 'saix.net' has been found, and is reachable in 11 hops. Also, it responded to HTTP requests on port 80 (it is running server Apache/1.3.27 (Unix) PHP/4.3.2 mod_perl/1.27 mod_ssl/2.8.14 OpenSSL/0.9.7b, which responded in 953ms). The TTL value of packets received from it is 242.In general this route offers a good throughput, with hops responding on average within 24ms. The DNS lookup was completed almost instantaneously (less than 2ms - this may be the result of caching).

Hop %Loss IP Address Node Name Location Tzone ms Graph Network
0 41.***.92.*** private-9c6f934 * African Network Information Center NET41
1 100
2 196.38.73.181 - (Mauritius) +04:00 21 -x------ African Network Information Center NET196
3 196.38.73.142 - (Mauritius) +04:00 18 x- African Network Information Center NET196
4 196.38.73.137 - (Mauritius) +04:00 20 x-- African Network Information Center NET196
5 196.26.96.203 - ... 19 x-- The whole IPv4 address space
6 196.26.0.250 - ... 20 x---- The whole IPv4 address space
7 168.209.86.166 - (Mauritius) +04:00 19 x African Network Information Center AFRINIC-168-209-0-0
8 196.25.127.181 rrba-ip-spe-2-wan.telkom-ipnet.co.za ... 20 x- The whole IPv4 address space
9 196.43.25.137 - (Mauritius) +04:00 20 x- African Network Information Center NET196
10 196.43.11.30 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (Mauritius) +04:00 40 x- African Network Information Center NET196
11 196.25.1.200 saix.net ... 42 x- The whole IPv4 address space
Roundtrip time to saix.net, average = 42ms, min = 42ms, max = 44ms -- Jul 3, 2007 7:31:52 PM
 
Last edited:
I just thought this was end of month thing, but if this is still happening even after the 1st.... let me do some of my own tests. Is this on the SAIX network only, or Verizon aswell..

ISDSL I guess is excluded due to sat link?
 
My ping is bigger than your ping :D ;) :p but you would like to say: My ping is smaller than your ping ;) :D :p
 
MoH what do u type in to get those detailed tracert results of yours ? It looks quite impressive :D
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X