Telkom, please fix this

M

Mr.Jax

Expert Member
Joined
Sep 22, 2009
Messages
1,474
Reaction score
43
Location
Nice try FBI / I won't say NSA
So I have latency and throughput problems...been having these problems for a year now.

See this:
http://www.speedtest.net/result/777830748.png
and this:
Tracing route to dsl-240-128-01.telkomadsl.co.za [41.240.128.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 123 ms 146 ms 144 ms dsl-240-128-01.telkomadsl.co.za [41.240.128.1]

Trace complete.

This is on a 4Mbps line.

Dear Telkom, this only happens out of office hours, i.e. after 5PM week days and on weekends.
Mr. Jax has replaced everything on his side and reinstalled everything too.

So,

Do you think that you can fix this ?

After countless attempts logging faults this is going nowhere and it's making Mr. Jax extremely negative towards Telkom.

I hope someone competent at Telkom reads this and addresses the problem. 12 months of this and I'm really fed up.

I see people complaining here when they occasionally have bad latency. Now imagine enduring that for a long time and you'll know how irritated I'm with them.

FIXIT!

Some more info on the line:
ADSL Link Downstream Upstream
Connection Speed 4096 kbps 640 kbps
Line Attenuation 16.0 db 10.5 db
Noise Margin 29.5 db 14.0 db


Stuff I've tried:
- Different ISP (IS backbone, unshaped)
- Different router
- Different computers
- Replaced all cables, filters and connections.
 
Last edited:
Short ping to my DSL default gateway....
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=76ms TTL=254
Reply from 41.240.128.1: bytes=32 time=101ms TTL=254
Reply from 41.240.128.1: bytes=32 time=48ms TTL=254
Reply from 41.240.128.1: bytes=32 time=121ms TTL=254
Reply from 41.240.128.1: bytes=32 time=86ms TTL=254
Reply from 41.240.128.1: bytes=32 time=55ms TTL=254
Reply from 41.240.128.1: bytes=32 time=108ms TTL=254
Reply from 41.240.128.1: bytes=32 time=109ms TTL=254
Reply from 41.240.128.1: bytes=32 time=58ms TTL=254
Reply from 41.240.128.1: bytes=32 time=113ms TTL=254
Reply from 41.240.128.1: bytes=32 time=119ms TTL=254
Reply from 41.240.128.1: bytes=32 time=103ms TTL=254
Reply from 41.240.128.1: bytes=32 time=133ms TTL=254
Reply from 41.240.128.1: bytes=32 time=113ms TTL=254
Reply from 41.240.128.1: bytes=32 time=145ms TTL=254
Reply from 41.240.128.1: bytes=32 time=42ms TTL=254
Request timed out.
Request timed out.
Reply from 41.240.128.1: bytes=32 time=112ms TTL=254
Reply from 41.240.128.1: bytes=32 time=125ms TTL=254
Reply from 41.240.128.1: bytes=32 time=135ms TTL=254
Reply from 41.240.128.1: bytes=32 time=149ms TTL=254
Reply from 41.240.128.1: bytes=32 time=121ms TTL=254
Reply from 41.240.128.1: bytes=32 time=96ms TTL=254
Reply from 41.240.128.1: bytes=32 time=107ms TTL=254
Reply from 41.240.128.1: bytes=32 time=78ms TTL=254
Reply from 41.240.128.1: bytes=32 time=90ms TTL=254
Reply from 41.240.128.1: bytes=32 time=110ms TTL=254
Reply from 41.240.128.1: bytes=32 time=135ms TTL=254
Reply from 41.240.128.1: bytes=32 time=132ms TTL=254
Reply from 41.240.128.1: bytes=32 time=86ms TTL=254
Reply from 41.240.128.1: bytes=32 time=104ms TTL=254
Reply from 41.240.128.1: bytes=32 time=97ms TTL=254
Reply from 41.240.128.1: bytes=32 time=120ms TTL=254
Reply from 41.240.128.1: bytes=32 time=124ms TTL=254
Reply from 41.240.128.1: bytes=32 time=133ms TTL=254
Reply from 41.240.128.1: bytes=32 time=128ms TTL=254
Reply from 41.240.128.1: bytes=32 time=137ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 38, Received = 36, Lost = 2 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 149ms, Average = 106ms

Next post will be from an IS based unshaped account....
 
IS unshaped details:
Tracing route to 196-210-146-1-tvwt-esr-2.dynamic.isadsl.co.za [196.210.146.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 105 ms 113 ms 97 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 95 ms 98 ms 115 ms cdsl1-rba-vl11.ip.isnet.net [196.38.73.37]
5 105 ms 93 ms 99 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 148 ms 152 ms 139 ms cdsl2-rba-vl2.ip.isnet.net [196.26.77.2]
7 119 ms 97 ms 75 ms cdsl2-rba-vl153.ip.isnet.net [196.38.73.14]
8 35 ms 43 ms 49 ms cdsl2-rba-vl2562-ipc.ip.isnet.net [196.38.73.218
]
9 78 ms 75 ms 67 ms 196-210-146-1-tvwt-esr-2.dynamic.isadsl.co.za [1
96.210.146.1]

Trace complete.

Pinging 196.210.146.1 with 32 bytes of data:
Reply from 196.210.146.1: bytes=32 time=76ms TTL=254
Reply from 196.210.146.1: bytes=32 time=115ms TTL=254
Reply from 196.210.146.1: bytes=32 time=92ms TTL=254
Reply from 196.210.146.1: bytes=32 time=129ms TTL=254
Reply from 196.210.146.1: bytes=32 time=97ms TTL=254
Reply from 196.210.146.1: bytes=32 time=97ms TTL=254
Reply from 196.210.146.1: bytes=32 time=98ms TTL=254
Reply from 196.210.146.1: bytes=32 time=113ms TTL=254
Reply from 196.210.146.1: bytes=32 time=76ms TTL=254
Reply from 196.210.146.1: bytes=32 time=165ms TTL=254
Reply from 196.210.146.1: bytes=32 time=151ms TTL=254
Reply from 196.210.146.1: bytes=32 time=61ms TTL=254
Reply from 196.210.146.1: bytes=32 time=152ms TTL=254
Reply from 196.210.146.1: bytes=32 time=138ms TTL=254
Reply from 196.210.146.1: bytes=32 time=133ms TTL=254
Reply from 196.210.146.1: bytes=32 time=139ms TTL=254
Reply from 196.210.146.1: bytes=32 time=83ms TTL=254
Reply from 196.210.146.1: bytes=32 time=110ms TTL=254

Ping statistics for 196.210.146.1:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 165ms, Average = 112ms


A speedtest result:
http://www.speedtest.net/result/777857040.png
 
Last edited:
Kaas internet!

OK so dagse Mr JAX . hoe gaan dit my PVR buddy :P is jou internet ook dood vandag, ek download iets teen 4 kBps cheer!
 
Looks like your dslam / exchange is overpopulated or just really has a crappy upstream link to the ESR... full stop! your stats are fine, it's definitely a problem on Telkom's side - looks like they havent handled contention ratios properly for your dslam. Where abouts you stay?
 
sigh...
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=221ms TTL=254
Reply from 41.240.128.1: bytes=32 time=177ms TTL=254
Reply from 41.240.128.1: bytes=32 time=136ms TTL=254
Reply from 41.240.128.1: bytes=32 time=171ms TTL=254
Reply from 41.240.128.1: bytes=32 time=205ms TTL=254
Reply from 41.240.128.1: bytes=32 time=181ms TTL=254
Reply from 41.240.128.1: bytes=32 time=125ms TTL=254
Reply from 41.240.128.1: bytes=32 time=184ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 221ms, Average = 171ms
 
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=223ms TTL=254
Reply from 41.240.128.1: bytes=32 time=183ms TTL=254
Reply from 41.240.128.1: bytes=32 time=179ms TTL=254
Reply from 41.240.128.1: bytes=32 time=237ms TTL=254
Reply from 41.240.128.1: bytes=32 time=248ms TTL=254
Reply from 41.240.128.1: bytes=32 time=98ms TTL=254
Reply from 41.240.128.1: bytes=32 time=130ms TTL=254
Reply from 41.240.128.1: bytes=32 time=149ms TTL=254
Reply from 41.240.128.1: bytes=32 time=163ms TTL=254
Reply from 41.240.128.1: bytes=32 time=144ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 98ms, Maximum = 248ms, Average = 175ms
 
Just for interest sake, this is what it looks like in business hours (or when it's at its best)
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=18ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=18ms TTL=254
Reply from 41.240.128.1: bytes=32 time=18ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms TTL=254
Reply from 41.240.128.1: bytes=32 time=18ms TTL=254
Reply from 41.240.128.1: bytes=32 time=18ms TTL=254
Reply from 41.240.128.1: bytes=32 time=17ms 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 = 17ms, Maximum = 18ms, Average = 17ms
 
Yup, you guessed right...pretty much the same thing every bloody evening.
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=178ms TTL=254
Reply from 41.240.128.1: bytes=32 time=108ms TTL=254
Reply from 41.240.128.1: bytes=32 time=141ms TTL=254
Reply from 41.240.128.1: bytes=32 time=160ms TTL=254
Reply from 41.240.128.1: bytes=32 time=173ms TTL=254
Reply from 41.240.128.1: bytes=32 time=233ms TTL=254
Reply from 41.240.128.1: bytes=32 time=116ms TTL=254
Reply from 41.240.128.1: bytes=32 time=139ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 233ms, Average = 156ms
 
Nice....don't you think ???? sigh...
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=197ms TTL=254
Request timed out.
Reply from 41.240.128.1: bytes=32 time=224ms TTL=254
Reply from 41.240.128.1: bytes=32 time=223ms TTL=254
Reply from 41.240.128.1: bytes=32 time=229ms TTL=254
Reply from 41.240.128.1: bytes=32 time=258ms TTL=254
Reply from 41.240.128.1: bytes=32 time=156ms TTL=254
Reply from 41.240.128.1: bytes=32 time=231ms TTL=254
Reply from 41.240.128.1: bytes=32 time=226ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 9, Received = 8, Lost = 1 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 258ms, Average = 218ms
 
Mr Jax - did you ever get this resolved? How? I am having the same problem (except the other way around - here, I get congestion during the day because of offices coming online) and not getting anywhere with Telkom. One technician after the next finds that there is nothing wrong. Argh!!!!
 
Hey, not getting anywhere with this.
Its been a year of enduring this ****** bulls***t

As I type this rely, this is what my latency looks like:
DISGUSTING!
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=49ms TTL=254
Reply from 41.240.128.1: bytes=32 time=99ms TTL=254
Reply from 41.240.128.1: bytes=32 time=81ms TTL=254
Reply from 41.240.128.1: bytes=32 time=105ms TTL=254
Reply from 41.240.128.1: bytes=32 time=163ms TTL=254
Reply from 41.240.128.1: bytes=32 time=87ms TTL=254
Reply from 41.240.128.1: bytes=32 time=167ms TTL=254
Reply from 41.240.128.1: bytes=32 time=99ms TTL=254
Reply from 41.240.128.1: bytes=32 time=155ms TTL=254
Reply from 41.240.128.1: bytes=32 time=105ms TTL=254
Reply from 41.240.128.1: bytes=32 time=182ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 182ms, Average = 117ms
 
I've just about had it, time to kiss my online gaming adventures bye bye and cancel everything with Telkom. so so ***** fed up with this, I just can't express it in words. Totally and utterly pathetic that telkom can't help me with this. Its a **** joke...

Ja...I'm seriously p**ssed off right now.
 
@Mr.Jax
Who is your ISP? If you have the MWeb All Inclusive package, you could try reporting the problem to MWeb, who will then contact Telkom for you.
 
Definitely a congestion problem, everyone getting home and murdering your DSLAM. Only Telkom can fix it.
 
Ugh....really bad again tonight...last night it was perfect!
Pinging 41.240.128.1 (<< the wan gateway telkom assigns to my dsl connection...the first hop) with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=153ms TTL=254
Reply from 41.240.128.1: bytes=32 time=215ms TTL=254
Reply from 41.240.128.1: bytes=32 time=361ms TTL=254
Reply from 41.240.128.1: bytes=32 time=101ms TTL=254
Reply from 41.240.128.1: bytes=32 time=170ms TTL=254
Reply from 41.240.128.1: bytes=32 time=233ms TTL=254
Reply from 41.240.128.1: bytes=32 time=221ms TTL=254
Reply from 41.240.128.1: bytes=32 time=192ms TTL=254
Reply from 41.240.128.1: bytes=32 time=216ms TTL=254
Reply from 41.240.128.1: bytes=32 time=184ms TTL=254
Reply from 41.240.128.1: bytes=32 time=118ms TTL=254
Reply from 41.240.128.1: bytes=32 time=202ms 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 = 101ms, Maximum = 361ms, Average = 197ms

^^ Telkom's next generation network is good hey!
 
Looks like same issue as mine, except im looking at larger pings, 25-50% packet loss, hair being ripped out etc.
But telkom investigated and let us know the DSLAM is rap0xed.
 
Dear Telkom,

Well done, your technical ability to correct problems and customer care is just dandy /sarcasm.

C:\Users\****>ping -t 41.240.128.1

Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=66ms TTL=254
Reply from 41.240.128.1: bytes=32 time=130ms TTL=254
Reply from 41.240.128.1: bytes=32 time=127ms TTL=254
Reply from 41.240.128.1: bytes=32 time=138ms TTL=254
Reply from 41.240.128.1: bytes=32 time=206ms TTL=254
Reply from 41.240.128.1: bytes=32 time=154ms TTL=254
Reply from 41.240.128.1: bytes=32 time=97ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 7, Received = 7, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 206ms, Average = 131ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X