My farking local ping

K

killadoob

Honorary Master
Joined
Jan 30, 2004
Messages
46,571
Reaction score
17
Location
South Africa.
Ok guys so i have reported the fault with telkom.

Maybe someone has the same problem with high local pings as i do, never below 100 and today over 400.

I have tried

IS
Saix unshaped
IS unshaped
mweb uncapped

All got high pings. Could it be my router? (doubtful) Will telkom be able to fix it?
 
In the same boat. I ping 120+ to the majority of servers in the day and it settles at night to normal 35/40. I'm on an IS-based 4096 Uncapped account. Saix accounts are usually 100% stable although I haven't tested one in a while.
 
Which area are you in?

I live in Randpark Ridge and connect to Bromhof exchange and have a similar problem during business hours where local pings are above 100ms and tests with www.speedtest.net do not go above above 1 mbps. My ADSL router syncs fine at 4096/512 with the DSLAM at the exchange and I have excellent SNR and line attenuation values.

I have also tested with WA unshaped, Nexus shaped, Mweb uncapped and Telkom unshaped accounts and get the same problem with all of them, so the problem is not specific to any ISP. I suspect that there is a bottleneck somewhere on Telkom's ADSL network that services my area.
 
Last edited:
killadoob said:
All got high pings. Could it be my router? (doubtful) Will telkom be able to fix it?
Click to expand...
As counter-intuitive as it may seem, if you were to place one "(doubtful)" between those two possible reasons as you did, you should rather have placed it on the latter option. Yeah, I doubt it's your router... chances of that are incredibly slim, but I doubt even more that Telkom will be able to fix it ;)

Ok but realistically now, the reason for the high pings is because of national infrastructure congestion between service providers during office hours, especially now with the uncapped story going on. This is mostly the case with peering points between SAIX and IS, but obviously applies elsewhere also. How are your pings at night? Can you do some traceroutes?
Log into the Telkom guest account (username: guest@telkomadsl, password: guest) and do a traceroute (tracert in dos/cmd) to 196.43.1.11, and then paste your results here, then we'll be able to see if its your localized area Your modem/Your Telkom DSLAM that's at fault, or if it's just the expected national peering congestion (which has been going on for years, affects us all, and is unacceptable, but what can we do...)
 
Last edited:
same here telkom capped and mweb uncapped seems to be better atm
 
Yeah, I've got this annoying problem too.
Tried everything, new router, new copper as far as i can, different ISP's, IS/SAIX...all the same.

If you get this resolved, which I highly doubt you will (since I've been battling with Telkom for a year now on this), please let me know what/how/who etc.

I'm in the Centurion/Pierre van Ryneveld area if that helps.
 
Well i am in fountainbleau which is not far from randpark ridge so i think we both connect to the same telkom exchange, the one across from rhema i would imagine.

Anyhow i have no problems with a high ping during office hours i do have a problem with having a ping over 100 24/7 now :(. Last night at 12 my ping was averaging 134 :(.
 
killadoob said:
Well i am in fountainbleau which is not far from randpark ridge so i think we both connect to the same telkom exchange, the one across from rhema i would imagine.

Anyhow i have no problems with a high ping during office hours i do have a problem with having a ping over 100 24/7 now :(. Last night at 12 my ping was averaging 134 :(.
Click to expand...

If your phone number starts with 011791, 011792 or 011793 your are on Bromhof which is opposite the Rhema church.
 
With the current problems we have I wonder what will happen when Telkom rolls out the 8mbps lines as this will put more strain on the ADSL infrastructure. :(
 
The only major reason why it *could* be your router, is if you installed some custom firmware, like DD-WRT, or White Russian, Or any other Linux distro, combined with incorrect iptables/filters/rules.... I had that once, I had a loop.
 
I have been struggling for about 2 years with High ping and slow connections speeds, I tried everything in the book to sort this out. After many fights with Telkom I found out that they Overload the two D-SLAMS in our exchange. One of my friends works for Telkom and he did a bit of research. He told me that our two D-SLAMS are so congested that they are working at 110% nearly 24 hours a day, and that they flatline regularly due to the overloading . To make maters worse is that the one D-SLAM only has a 4Meg capacity and the second D-SLAM a 8Meg capacity. And there are 4 suburbs running of these two overworked D-SLAMS. I think the overloading of D-SLAMS can be a big factor in many of the complaints as listed in this thread. So unless Telkom upgrade their Infrastructure soon, I think this problem will never go away.
 
Wow fun times :(

Reply from 196.43.22.222: bytes=32 time=432ms TTL=245
Reply from 196.43.22.222: bytes=32 time=427ms TTL=245
Reply from 196.43.22.222: bytes=32 time=617ms TTL=245
Reply from 196.43.22.222: bytes=32 time=699ms TTL=245
 
killadoob said:
Wow fun times :(

Reply from 196.43.22.222: bytes=32 time=432ms TTL=245
Reply from 196.43.22.222: bytes=32 time=427ms TTL=245
Reply from 196.43.22.222: bytes=32 time=617ms TTL=245
Reply from 196.43.22.222: bytes=32 time=699ms TTL=245
Click to expand...

Seems playable Killa. Stop whining.




:D
 
had these issues a few backs ago, all I can say is keep at them, everyday. Port refresh or a port reset at the exchange, keep on them for it.
 
Hahah i think telkom sorted me out :D

Pinging games.saix.net [196.43.22.222] with 32 bytes of dat
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=13ms TTL=245
Reply from 196.43.22.222: bytes=32 time=14ms TTL=245
Reply from 196.43.22.222: bytes=32 time=14ms TTL=245

The last few weeks i have not seen these pings, been averaging 100 :D. Hope they fixed it and it is not just a good couple days.
 
You complain about your local ping? Look at mine on the MWEB uncapped lol:

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=1450ms TTL=243
Reply from 196.43.22.222: bytes=32 time=1690ms TTL=243
Reply from 196.43.22.222: bytes=32 time=1506ms TTL=243
Reply from 196.43.22.222: bytes=32 time=1625ms TTL=243

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1450ms, Maximum = 1690ms, Average = 1567ms
 
Local ping telkom problem

If you do tracert you will see the problem is with the dslam.
For example if you gaming on the european battlenet server (Blizzard) do a
tracert europe.battle.net
You will see the first hop should be about 20ms under normal load.
The first hop where i stay goes to 800ms during peak hours. This is because telkom overload the DSLAM in your area. I do the same trace route at work in braamfontein where the infrastructure has to be good because of the businesses it never goes above 18ms for the first hop with my same ADSL account. It is not your ISP it is TELKOM if the ping is high on the first two hops.
See below (at work)
1 15 ms 14 ms 16 ms 196-209-7-1-rndf-esr-3.dynamic.isadsl.co.za [196
209.7.1]
2 20 ms 20 ms 21 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
3 15 ms 16 ms 15 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
4 15 ms 16 ms 16 ms core2b-rba-te2-0-0.ip.isnet.net [196.26.0.182]
5 310 ms 309 ms 310 ms mi-za-rba-p6-gi2-0-0-304.ip.isnet.net [168.209.1
4.175]
6 309 ms 309 ms 309 ms mi-us-25b-p2-gi1-0-4.ip.isnet.net [168.209.160.2
9]
7 304 ms 304 ms 305 ms core2a-ny-gi1-0-19-304.ip.isnet.net [168.209.164
126]
8 306 ms 308 ms 306 ms 168.209.244.3

If

Telkom need to upgrade there local existing infrastructure and they are not doing this. Im trying to get them to upgrade my dslam in Quellerina but they just don't seem to care.
When they start releasing 8mb lines this will get even worse. If you a gamer this is unplayable.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X