Latency is up...

My Modem Status as at 27 Feb 2005.

System up Time: 42:41:49
CPU Load: 3.10%

WAN Port Statistics:
Link Status: Up
Upstream Speed: 512 kbps
Downstream Speed: 2048 kbps
 
wouldn't getting a new faster router help??
considering that the interleaving is done on router
and at exchange??/
 
razor, afaik the exchange selects the interleaving mode and our routers dont have a say. well, i know my modem doesnt :(
 
Contrary to popular belief, Interleaved mode is better for VOIP because of the error correction.

Secondly, this mode is enabled per Virtual Circuit. It can be done remotely (normally).

For the records, I'm still on Fast Path :)
 
I spoke to a tech this weekend at my home and he says these decisions come from upper management without consulting the people who actually know how the hardware works. Apparently the whole lower sync rate decision was made after meetings along the lines of "our infrastructure is so ****, so how are we going to provide DSL to people on crappy old lines". The answer was to lower the sync rate to 640/384. But the Tech said this makes no sense. If you resctrict a DSL modem to 640k, then you are effectively strangling the available amount of bandwidth that it can use to transmit uncorrupted data. With a higher sync rate of 1 or 2+ Mbps, the DSL modem can select exact frequencies with the clearest signal. If you know how a DSL modem works, it's basically 256 virtual 56k modems spaced over a wide frequency band. The DSL modem tailors each one of those 256 virtual modems to the specific conditions on the line. Now if you reduce the sync rate to 640kbps, the DSL modem now only has 20 out of 256 virutal modems to transmit, so it can't "choose" from a large pool of modems. Hope this makes sense, it's monday morning.
 
Source Latency

3 People I know of that have higher latency all use SAIX(Telkom) as their ISP.
The one person in particuler had a ping of 150 this weekend. The other 2 about 130.
Cant say if their is a direct connection yet, but it is likely their exchanges have been altered to the lower speeds.
They are however not very happy.

I am referring them to this thread.
 
Last edited:
Contacting SAIX

As I am not an SAIX(Telkom) customer, perhaps someone would like to refer SAIX to this issue, as they are the biggest when it comes to gaming servers in SA.
Maybe they could shed some light on the topic.
 
Thanks

MansoN said:
There are two posts on the SGS forums regarding this issue:

1. Online gaming hanging by a thread

and

2. latency

In spite of the wealth of admins, no light has been shed on this subject, aside from the fact that Telkom has changed that setting at a lot of the exchanges which is causing this increase in latency.
Click to expand...


Thanks for posting this Monsoon.
Interesting.
 
Thank ***!

I'm in bergvliet, cape town, and my 30 ping to SGS (Yes, CS) is now 70 to 100.
I've checked router, smoothwall gateway and re-installed (after a miriad of troubleshooting, and not a practise I prefer...at all...ever) and still this persists. I'm not even going to bother complaining to telkom, as the speed test indicates a "fast speed".

check this trace route --->>

Start|| tracert 196.25.1.1

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

1 1 ms 1 ms 1 ms 192.168.10.200
2 51 ms 50 ms 51 ms wbs-146-128-01.telkomadsl.co.za [165.146.128.1]

3 52 ms 50 ms 51 ms wbs-ip-er-1-fe-4-0-0-1.telkom-ipnet.co.za [196.4
3.23.10]
4 53 ms 52 ms 52 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [1
96.43.11.30]
5 53 ms 53 ms 53 ms igubu.saix.net [196.25.1.1]

Trace complete. ||END

50 milliseconds from the far side of my gateway to the next hop??

"O Lord, grant me the serenity for that which I cannot change, Lend me thy shotgun, for I art thou agent against high latency"
 
Uninet 256 Home account ping times:

- - - - - - - - - - - - - - - - - -

Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=22ms TTL=114
Reply from 196.2.128.100: bytes=32 time=16ms TTL=114
Reply from 196.2.128.100: bytes=32 time=16ms TTL=114
Reply from 196.2.128.100: bytes=32 time=25ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=16ms TTL=114
Reply from 196.2.128.100: bytes=32 time=19ms TTL=114
Reply from 196.2.128.100: bytes=32 time=22ms TTL=114
Reply from 196.2.128.100: bytes=32 time=20ms TTL=114
Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=15ms TTL=114
Reply from 196.2.128.100: bytes=32 time=22ms TTL=114
Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=19ms TTL=114
Reply from 196.2.128.100: bytes=32 time=23ms TTL=114
Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=15ms TTL=114
Reply from 196.2.128.100: bytes=32 time=18ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=23ms TTL=114
Reply from 196.2.128.100: bytes=32 time=13ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=17ms TTL=114
Reply from 196.2.128.100: bytes=32 time=24ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=13ms TTL=114
Reply from 196.2.128.100: bytes=32 time=29ms TTL=114
Reply from 196.2.128.100: bytes=32 time=14ms TTL=114
Reply from 196.2.128.100: bytes=32 time=20ms TTL=114

Ping statistics for 196.2.128.100:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 29ms, Average = 18ms

- - - - - - - - - - - - - - - - - -

Is that good? :D
 
Pinging karoo.mweb.co.za [196.2.128.100] with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=65ms TTL=116
Reply from 196.2.128.100: bytes=32 time=69ms TTL=116
Reply from 196.2.128.100: bytes=32 time=64ms TTL=116
Reply from 196.2.128.100: bytes=32 time=66ms TTL=116

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

My Exchange has not been altered yet. So I await my fate.
But spoken to a few people and they are complaining big time.
 
ping -n 16 igubu.saix.net

Pinging igubu.saix.net [196.25.1.1] with 32 bytes of data:

Reply from 196.25.1.1: bytes=32 time=10ms TTL=244
Reply from 196.25.1.1: bytes=32 time=11ms TTL=244
Reply from 196.25.1.1: bytes=32 time=23ms TTL=244
Reply from 196.25.1.1: bytes=32 time=10ms TTL=244
Reply from 196.25.1.1: bytes=32 time=9ms TTL=244
Reply from 196.25.1.1: bytes=32 time=12ms TTL=244
Reply from 196.25.1.1: bytes=32 time=9ms TTL=244
Reply from 196.25.1.1: bytes=32 time=12ms TTL=244
Reply from 196.25.1.1: bytes=32 time=11ms TTL=244
Reply from 196.25.1.1: bytes=32 time=12ms TTL=244
Reply from 196.25.1.1: bytes=32 time=27ms TTL=244
Reply from 196.25.1.1: bytes=32 time=9ms TTL=244
Reply from 196.25.1.1: bytes=32 time=29ms TTL=244
Reply from 196.25.1.1: bytes=32 time=18ms TTL=244
Reply from 196.25.1.1: bytes=32 time=12ms TTL=244
Reply from 196.25.1.1: bytes=32 time=13ms TTL=244

Ping statistics for 196.25.1.1:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 29ms, Average = 14ms

- - - - - - - - - - - - - - - - - -

Someone faster than Telkom themselves and thats even at half the speed of ADSL
 
Ok I am using a SMC7204BRA Annex B modem/router/switch.

It works great, never loses sync like a friend who is 2 houses from me.

Anyhow, it used to show 2048/512 down/up both fast latency.

Today I cant ping anything and look at what it shows....

http://www.restricted.co.za/screenshots/telkom_adsl_broken.JPG

its... : 262752 Kbps / 0 Kbps down/up

im bloody sure something on my dslam port is fooked
 
Nothing posted on SGS ever seems to get resolved. Anything hinting at criticism of Telkom seems to get locked. Complaints about the game servers are usually met with a "Shaddup and be grateful you get the service for free" type response.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X