R1000 to the telkom Techie that can fix this for me

M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,474
Reaction score
43
Location
Nice try FBI / I won't say NSA
I have had latency problems since about March last year.

I've tried everything:
Replaced/tried different hardware and software (routers, OS's, computers, new wiring all round etc etc etc)
Tried ADSL support a gazillion times, they just say all is fine all the time....fail!
Basically everything.

The problem lies with the exchange/dslam/whateveridontcare.

An example (taken 2 minutes ago)
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=36ms TTL=254
Reply from 41.240.128.1: bytes=32 time=92ms TTL=254
Reply from 41.240.128.1: bytes=32 time=60ms TTL=254
Reply from 41.240.128.1: bytes=32 time=104ms TTL=254
Reply from 41.240.128.1: bytes=32 time=82ms TTL=254
Reply from 41.240.128.1: bytes=32 time=62ms TTL=254
Reply from 41.240.128.1: bytes=32 time=124ms TTL=254
Reply from 41.240.128.1: bytes=32 time=120ms TTL=254
Reply from 41.240.128.1: bytes=32 time=125ms TTL=254
Reply from 41.240.128.1: bytes=32 time=32ms TTL=254
Reply from 41.240.128.1: bytes=32 time=117ms TTL=254
Reply from 41.240.128.1: bytes=32 time=151ms TTL=254
Reply from 41.240.128.1: bytes=32 time=179ms TTL=254
Reply from 41.240.128.1: bytes=32 time=203ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 203ms, Average = 106ms

This happens ALWAYS in the evening and over weekends. It basically never happens in business hours.

Now,

If a telkom dude can fix this I will pay him R500, if its still fine after 30 days I'll give you the other R500. (Sorry I dont have more than that, so don't expect R25,000 like that other guys did...)


Hope this works, its my last hope.

PS

NO DOWNLOADS/UPLOADS/HACKING/STEALING/ETC occurs when this problem arises....its a telkom equipment fault.
 
Looks like you using an uncapped account.

R80 000? Is that what it cost to get ADSL availability?
 
traceroute to 41.240.128.1 (41.240.128.1), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 10.426 ms 10.491 ms 10.629 ms
2 196-210-150-1.dynamic.isadsl.co.za (196.210.150.1) 345.351 ms 345.634 ms 347.612 ms
3 cdsl1-rba-vl2460.ip.isnet.net (196.38.72.217) 377.687 ms 380.123 ms 388.741 ms
4 cdsl1-rba-vl150.ip.isnet.net (196.38.73.17) 390.947 ms 392.572 ms 396.837 ms
5 168.209.1.139 (168.209.1.139) 398.546 ms 404.466 ms 410.864 ms
6 196.26.0.10 (196.26.0.10) 4373.792 ms 383.770 ms 382.144 ms
7 rrba-ip-spe-2-wan.telkom-ipnet.co.za (196.25.127.181) 383.952 ms 385.853 ms 386.215 ms
8 196.43.25.137 (196.43.25.137) 392.854 ms 398.018 ms *
9 tvwt-ip-esr-2-pos-8-0-0.telkom-ipnet.co.za (196.43.24.238) 399.196 ms 385.907 ms *


Where is your problem? :-)
 
Srack0verflow said:
only gona cost the techie r80 000 for an additional port card
Click to expand...

Crap! Telkom carries the cost like they should not the Techie - this is another desperate client trying to get some service out of a company that just gives a rats a#@# about service!
Mr.Jax, I feel for you - same issue here! I am so tired of some guy always giving the "other" view defending such bad service!

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Request timed out.
Reply from 196.43.22.222: bytes=32 time=1512ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1580ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1623ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1573ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1866ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1921ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1721ms TTL=244

Ping statistics for 196.43.22.222:
Packets: Sent = 8, Received = 7, Lost = 1 (12% loss),
Approximate round trip times in milli-seconds:
Minimum = 1512ms, Maximum = 1921ms, Average = 1685ms
 
No. Shaped/unshaped, SAIX, IS, MWEB...no difference, same problem every time.

Well, if bribing a technician wont fix this then WTF WILL????

FYI...41.240.128.1 is the first internet side hop, eg, the ISP assigned default gateway for my connection.
 
Cancel telephone line.

Wait till line is dead.

Subscribe to new service.

Add note to new service subscribtion to use diferent ADSL port on exchange.
 
OH well, this is obviously going nowhere.
Whatever...How stupid of me to think that someone at Telkom would actually give a damn about customer satisfaction. Gaan maar aan, jaag al julle kliente weg.
 
See my "Good News" post looks sorted

Pinging 41.240.128.1 with 32 bytes of data:

Reply from 41.240.128.1: bytes=32 time=39ms TTL=244
Reply from 41.240.128.1: bytes=32 time=34ms TTL=244
Reply from 41.240.128.1: bytes=32 time=33ms TTL=244
Reply from 41.240.128.1: bytes=32 time=34ms TTL=244

Ping statistics for 41.240.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 39ms, Average = 35ms
 
Another good news reply!
Mine is also fixed for now - let us see if it stays that way!

Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=21ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=21ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243

Ping statistics for 196.43.22.222:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 25ms, Average = 20ms
 
Firstly - try another ADSL account - purchase a prepay 1 Gb from Engen Garage to test with (R70/Gb)
Secondy - When I had lousy latency I called the 0800375375 call center and asked them to "reset my sync profile"
Was working like a dream thereafter , I cannot explain what happened
 
Been there, done it ALL, nothing solves the problem. TRied ifferent accounts, different routers, port reset etc etc etc...nothing fixes the problem.

Right now:
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=147ms TTL=254
Reply from 41.240.128.1: bytes=32 time=213ms TTL=254
Reply from 41.240.128.1: bytes=32 time=215ms TTL=254
Reply from 41.240.128.1: bytes=32 time=240ms TTL=254
Reply from 41.240.128.1: bytes=32 time=226ms TTL=254
Reply from 41.240.128.1: bytes=32 time=152ms TTL=254
Reply from 41.240.128.1: bytes=32 time=210ms TTL=254
Reply from 41.240.128.1: bytes=32 time=237ms TTL=254
Reply from 41.240.128.1: bytes=32 time=220ms TTL=254
Reply from 41.240.128.1: bytes=32 time=61ms TTL=254
Reply from 41.240.128.1: bytes=32 time=116ms TTL=254
Reply from 41.240.128.1: bytes=32 time=216ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 240ms, Average = 187ms

Nice eh?

So much for Telkom's "next generation network"....suck fail!
 
No surprize, same story every evening:
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=139ms TTL=254
Reply from 41.240.128.1: bytes=32 time=81ms TTL=254
Reply from 41.240.128.1: bytes=32 time=124ms TTL=254
Reply from 41.240.128.1: bytes=32 time=156ms TTL=254
Reply from 41.240.128.1: bytes=32 time=93ms TTL=254
Reply from 41.240.128.1: bytes=32 time=113ms TTL=254
Reply from 41.240.128.1: bytes=32 time=157ms TTL=254
Request timed out.
Reply from 41.240.128.1: bytes=32 time=107ms TTL=254
Reply from 41.240.128.1: bytes=32 time=102ms TTL=254
Reply from 41.240.128.1: bytes=32 time=134ms TTL=254
Reply from 41.240.128.1: bytes=32 time=135ms TTL=254
Reply from 41.240.128.1: bytes=32 time=46ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 13, Received = 12, Lost = 1 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 157ms, Average = 115ms

Is there seriously nobody in Telkom willing to help ?
 
Will you be able to apply for a 2nd line, if better results then simply cancel the existing one. This was suggested by another forumite in another thread (kudos to u).

Hope you get sorted.
 
Ok here goes

Let me guesse your problems start at around 18:00 in the evening and continues to about 08:00 the next day and then also the same times apply over weekends and public holidays from the Friday evening to the Monday morning. What happens is as follows.

In the exchange the DSLAM is provided with a few 2MB ATM links that provides the connection to the WWW. If it so happens that there is an overutilisation of the DSLAM and not enough ATM bandwidth it creates a bottleneck and results in high latency and packet loss. Now between the times mention above all port shaping by IS and SAIX is removed and users have a fully unshaped account with which they can download torrentz and so forth and there is also more users online in the evenings than during the day. Depending on your ISP the port shaping can still be in play after hours anyway as they can control the type of service from their side.

Now the only way to really get it fixed and have all the users in your area satisfied is by getting the ammount of ATM bandwidth to the DSLAM increased and making more bandwidth available to the WWW.

In my area where I stay it was exactly the same problem and it only got fixed about a week ago after a 3month waiting period for all the equipment to be upgraded and cut over to be done.

Hope this explains your problem a bit better.
 
Agreed,

Getting Telkom to do anything about that seems impossible and that's the damn issue I have. That's why I'm whining like a 9 year old, 0800DSLDSL is not worth my time, been there 25 times, got the t-shirt 0 times...

Welcome to Africah!
AcidT said:
Ok here goes

Let me guesse your problems start at around 18:00 in the evening and continues to about 08:00 the next day and then also the same times apply over weekends and public holidays from the Friday evening to the Monday morning. What happens is as follows.

In the exchange the DSLAM is provided with a few 2MB ATM links that provides the connection to the WWW. If it so happens that there is an overutilisation of the DSLAM and not enough ATM bandwidth it creates a bottleneck and results in high latency and packet loss. Now between the times mention above all port shaping by IS and SAIX is removed and users have a fully unshaped account with which they can download torrentz and so forth and there is also more users online in the evenings than during the day. Depending on your ISP the port shaping can still be in play after hours anyway as they can control the type of service from their side.

Now the only way to really get it fixed and have all the users in your area satisfied is by getting the ammount of ATM bandwidth to the DSLAM increased and making more bandwidth available to the WWW.

In my area where I stay it was exactly the same problem and it only got fixed about a week ago after a 3month waiting period for all the equipment to be upgraded and cut over to be done.

Hope this explains your problem a bit better.
Click to expand...
 
Cyclone said:
Another good news reply!
Mine is also fixed for now - let us see if it stays that way!

Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=21ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=21ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243
Reply from 196.43.22.222: bytes=32 time=20ms TTL=243

Ping statistics for 196.43.22.222:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 25ms, Average = 20ms
Click to expand...

And as I thought this was over the next day - now back to 1000ms-2000ms to a local SAIX server!!!
I can not believe a company so important to this country is allowed to be so BAD!!

We can host a world cup but sorry, we can not do a Telkom ADSL line to your house...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X