If you have local latency problems, please post here.

[Mr.Jax]

Hey guys and gals.

If you battle with ADSL local latency/packet loss problems (not international) especially after hours and over weekends, please tell me:

Where do you live
At what times do you have the problem
For how long have you been experiencing this.
What ISP are you using.
What backbone are you using (e.g. SAIX or IS or whatever).

After battling with this issue for more than 6 months, and discovering that I'm no the only person in my area with this problem, my patience has run out with Telkom. My gut tells me its a congestion problem and that they're trying to ignore it because it will cost them money to 'fix'.

I'm hoping that this might help all of us battling with this nonsense.
(My next stop is the CEO of Telkom, if I'm ever lucky to be given his contact details by the support supervisors. If you didn't know, you have the right to escalate it right up to the CEO : http://www.hellkom.co.za/pages/resolving-a-telkom-dispute.php )

Thanks peeps.

 

[gryster]

I have 100-120ms local latency with any WEB AFRICA account when gaming on SGS. This is ever since they swopped over to their own back-bone.

My IS and SAIX accounts I get 40-50ms pings. I've done a traceroute and sent the into to WA identifying their gateway routers which are adding the additional latency, but nothing has changed of course.

 

[Peon]

Eish Mr Jax.

traceroute to your dsl gateway. Ive got 4MB and my first hop is 66ms. Ive dug up so much 'poop' regarding telkom and why you 'could' have high/poor latencies.

Suffice to say, if your exchange is congested and overloaded they will wait for the house to burn down before calling the fire department.

 

[Metalspawn]

I have the same problems...

Where do you live
Pierre van Ryneveld

At what times do you have the problem
1. From about 5ish in the evening till late (like 2 o'clock in the morning)
2. The whole weekend

For how long have you been experiencing this.
About 3-6 Months

What ISP are you using.
I tried everything -> Webafrica (SAIX), Telkom(SAIX), IS, Afrihost (Prob SEACOM) , Unshaped (SAIX and Verizon)

What backbone are you using
Better question : What backbone am I not using


The techie is still busy with my/our problem Mr. Jax. Well this morning 00:22 I spoke to someone from telkom who actually understands the problem.. He updated my fault and increased the priority (I think). They worked yesterday to try and fix the problem. Looks like someone actually cares.

 

[Mr.Jax]

Eish Mr Jax.

traceroute to your dsl gateway. Ive got 4MB and my first hop is 66ms. Ive dug up so much 'poop' regarding telkom and why you 'could' have high/poor latencies.

Suffice to say, if your exchange is congested and overloaded they will wait for the house to burn down before calling the fire department.

Ja, thats exactly what I do to test and I get poor results right at the first hop, ie. WAN side gateway. Also, switching to IS, makes no difference.

Off Topic: Peon from HL2DM ?

 

[bboy]

for the last 3 months i've been experiencing double the latency for local SAIX connections, but it somehow came magically right over the last week(I lived in two different locations during this time)however i see its climbing again

 

[Metalspawn]

Mr. Jax

Hy . Hulle het my na 'n ander port toe geskuif (op 'n hele ander module, daai een is gefudge!
Results :
Reply from 196.43.22.222: bytes=32 time=24ms TTL=241
Reply from 196.43.22.222: bytes=32 time=23ms TTL=241
Reply from 196.43.22.222: bytes=32 time=24ms TTL=241
Reply from 196.43.22.222: bytes=32 time=24ms TTL=241
Reply from 196.43.22.222: bytes=32 time=25ms TTL=241
Request timed out.
Reply from 196.43.22.222: bytes=32 time=25ms TTL=241
Reply from 196.43.22.222: bytes=32 time=24ms TTL=241
Reply from 196.43.22.222: bytes=32 time=24ms TTL=241

/cheer!!!
Ok maar ons kry nogsteeds packet loss. Die admins is besig om dit uit te sort


My ander buddy se pings in Pierre van Ryneveld (selfde tyd gedoen) :
eply from 196.35.164.204: bytes=32 time=72ms TTL=119
Reply from 196.35.164.204: bytes=32 time=115ms TTL=119
Reply from 196.35.164.204: bytes=32 time=57ms TTL=119
Reply from 196.35.164.204: bytes=32 time=76ms TTL=119
Request timed out.
Reply from 196.35.164.204: bytes=32 time=110ms TTL=119
Reply from 196.35.164.204: bytes=32 time=139ms TTL=119