Telkom, please fix this

Do you know how far away you are from your dslam? The actual copper lines may be inferior.

Please do a pingtest and post the results.
 
D34M0n7 said:
Do you know how far away you are from your dslam? The actual copper lines may be inferior.

Please do a pingtest and post the results.
Click to expand...
This is nonsense. DSL won't sync under conditions that would cause high latency, it just doesn't work that way. I'm 3km from my exchange with a low noise margin and yet I ping 7ms to my DSLAM, the same ping I had when I was 200 meters from my previous DSLAM with high noise margins (SNR)... the problem lies at his exchange specifically, and the only things affecting ping AFAIK are congestion on the link, modems used (small factor), and sync rate (faster tends to lower ping)
 
Bad traceroutes on all ISPs during office hours

I've also got major office hours ping and bandwidth issues. Had it since I had my line installed over 6 months ago.

Filed at least 3 faults now. Here is a sample I took when I reported a fault last week:

MWeb Uncapped
→ traceroute saix.nettraceroute to saix.net (196.25.1.200), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 36.573 ms 8.364 ms 1.789 ms
2 41-132-46-1.dsl.mweb.co.za (41.132.46.1) 622.039 ms 831.226 ms 619.305 ms
3 tengig-0-0-0-104.vic-ipc-1.mweb.co.za (196.22.169.146) 705.124 ms 836.211 ms 814.229 ms
4 vl-92.vic-hscore-1.mweb.co.za (196.22.189.2) 874.233 ms 811.716 ms
vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 540.587 ms
5 tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225) 515.599 ms 677.032 ms 714.675 ms
6 rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249) 714.953 ms 830.230 ms 815.812 ms
7 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30) 818.520 ms 786.240 ms 763.376 ms
8 * * *
9 *^C

Web Africa Pre-paid
→ traceroute saix.nettraceroute to saix.net (196.25.1.200), 64 hops max, 52 byte packets
1 * 192.168.0.1 (192.168.0.1) 1.312 ms 1.885 ms
2 dsl-185-87-1.dynamic.wa.co.za (41.185.87.1) 623.015 ms 598.484 ms 620.812 ms
3 vl105.cr.gw.cpt.za.wa.co.za (196.220.59.250) 622.182 ms 653.662 ms 628.862 ms
4 vl35.er.gw.cpt.za.wa.co.za (41.185.0.38) 603.241 ms
vl34.er.gw.cpt.za.wa.co.za (41.185.0.34) 624.287 ms
vl35.er.gw.cpt.za.wa.co.za (41.185.0.38) 651.806 ms
5 upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 695.088 ms
upstream.vl102.gw.cpt.za.wa.co.za (196.220.59.230) 689.013 ms
upstream.vl101.gw.cpt.za.wa.co.za (196.220.59.226) 633.807 ms
6 wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za (196.43.11.30) 633.339 ms 664.447 ms 647.645 ms
^C


Afrihost Capped
→ traceroute saix.nettraceroute to saix.net (196.25.1.200), 64 hops max, 52 byte packets
1 * 192.168.0.1 (192.168.0.1) 1.289 ms 1.318 ms
2 196-210-150-129-wbs-esr-4.dynamic.isadsl.co.za (196.210.150.129) 728.020 ms 748.312 ms 722.830 ms
3 cdsl2-rba-vl2663.ip.isnet.net (196.38.73.25) 716.635 ms 728.025 ms 650.223 ms
4 cdsl2-rba-vl150.ip.isnet.net (196.38.73.9) 615.155 ms 661.566 ms 748.744 ms
5 core6a-rba-gi1-0-0.ip.isnet.net (168.209.1.165) 801.756 ms 818.535 ms 879.575 ms
6 168.209.1.170 (168.209.1.170) 843.406 ms 895.841 ms 738.206 ms
7 rrba-ip-spe-2-wan.telkom-ipnet.co.za (196.25.127.181) 792.994 ms 718.233 ms 754.755 ms
8 196.43.25.137 (196.43.25.137) 719.370 ms 734.572 ms 778.906 ms
^C
 
And so the tale of the big ping continues.
It's not a tale, its a series now, featuring every night of the day.brilliant!
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=122ms TTL=254
Reply from 41.240.128.1: bytes=32 time=69ms TTL=254
Reply from 41.240.128.1: bytes=32 time=106ms TTL=254
Reply from 41.240.128.1: bytes=32 time=125ms TTL=254
Reply from 41.240.128.1: bytes=32 time=95ms TTL=254
Reply from 41.240.128.1: bytes=32 time=85ms TTL=254
Reply from 41.240.128.1: bytes=32 time=86ms TTL=254
Reply from 41.240.128.1: bytes=32 time=88ms TTL=254
Reply from 41.240.128.1: bytes=32 time=32ms TTL=254
Reply from 41.240.128.1: bytes=32 time=131ms TTL=254
Reply from 41.240.128.1: bytes=32 time=123ms TTL=254
Reply from 41.240.128.1: bytes=32 time=157ms TTL=254
Reply from 41.240.128.1: bytes=32 time=127ms TTL=254
Reply from 41.240.128.1: bytes=32 time=113ms 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 = 157ms, Average = 104ms
 
Your dslam is oversubscribe & lacking backhaul capacity, bottom line.
 
ponder said:
Your dslam is oversubscribe & lacking backhaul capacity, bottom line.
Click to expand...
So much for all systems go 10mbps... his dslam can't even handle 4? what's up with that Telkom?
Mr.Jax I thought they sorted your exchange out recently?
 
OMG Telkom, it went good for a while and now the total BS is starting again...this whole week has been like this!!!
WTF are you noobs doing!?
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=189ms TTL=254
Reply from 41.240.128.1: bytes=32 time=188ms TTL=254
Request timed out.
Reply from 41.240.128.1: bytes=32 time=106ms TTL=254
Request timed out.
Reply from 41.240.128.1: bytes=32 time=205ms TTL=254
Reply from 41.240.128.1: bytes=32 time=150ms TTL=254
Reply from 41.240.128.1: bytes=32 time=139ms TTL=254
Reply from 41.240.128.1: bytes=32 time=76ms TTL=254
Reply from 41.240.128.1: bytes=32 time=49ms TTL=254
Reply from 41.240.128.1: bytes=32 time=123ms TTL=254
Reply from 41.240.128.1: bytes=32 time=88ms TTL=254
Reply from 41.240.128.1: bytes=32 time=146ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 13, Received = 11, Lost = 2 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 205ms, Average = 132ms
 
fragtion_ said:
So much for all systems go 10mbps... his dslam can't even handle 4? what's up with that Telkom?
Mr.Jax I thought they sorted your exchange out recently?
Click to expand...

Yeah, i was moved to a different DSLAM and it went ok for a while, but now its starting again.

10Mbps ?...please dont enable it it will result in a fat joke!
 
In regards to the ping spikes

I've been having them for quite some time too

Although I tend to get 2000+ ms at times x-x And I've had request timeouts plenty....

This is on a good time

-----------------------
Pinging telkomsa.net [196.25.211.40] with 32 bytes of data:
Reply from 196.25.211.40: bytes=32 time=41ms TTL=125
Reply from 196.25.211.40: bytes=32 time=43ms TTL=125
Reply from 196.25.211.40: bytes=32 time=46ms TTL=125
Reply from 196.25.211.40: bytes=32 time=40ms TTL=125
----------------------------------

On a bad time..

Pinging telkomsa.net [196.25.211.40] with 32 bytes of data:
Reply from 196.25.211.40: bytes=32 time=1167ms TTL=125
Reply from 196.25.211.40: bytes=32 time=1183ms TTL=125
Reply from 196.25.211.40: bytes=32 time=1200ms TTL=125
Reply from 196.25.211.40: bytes=32 time=1066ms TTL=125

And no, I was not downloading/uploading/updating. I made sure of that. And it's been worse than that.
 
Yup, every evening now....
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=137ms TTL=254
Reply from 41.240.128.1: bytes=32 time=132ms TTL=254
Reply from 41.240.128.1: bytes=32 time=60ms TTL=254
Reply from 41.240.128.1: bytes=32 time=107ms TTL=254
Reply from 41.240.128.1: bytes=32 time=52ms TTL=254
Reply from 41.240.128.1: bytes=32 time=149ms TTL=254
Reply from 41.240.128.1: bytes=32 time=78ms TTL=254
Reply from 41.240.128.1: bytes=32 time=138ms TTL=254
Reply from 41.240.128.1: bytes=32 time=139ms TTL=254
Reply from 41.240.128.1: bytes=32 time=140ms 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 = 52ms, Maximum = 149ms, Average = 113ms

Telkom! beware.....you will lose customers for life....this BS has been going on since Feb last year...its a total waste of time even trying the support centres...its a total waste of time trying the escalation centre....None of your support channels could solve this little problem, none of your support channels could even provide a explanation as to why it happens.

Gaan aan telkom...gaan aan.
 
Still going strong Telkom....every evening, this is what i get.
Bucket loads of FAIL and aids.

Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=163ms TTL=254
Reply from 41.240.128.1: bytes=32 time=235ms TTL=254
Reply from 41.240.128.1: bytes=32 time=171ms TTL=254
Reply from 41.240.128.1: bytes=32 time=198ms TTL=254
Reply from 41.240.128.1: bytes=32 time=124ms TTL=254
Reply from 41.240.128.1: bytes=32 time=182ms TTL=254
Reply from 41.240.128.1: bytes=32 time=89ms TTL=254
Reply from 41.240.128.1: bytes=32 time=123ms TTL=254
Reply from 41.240.128.1: bytes=32 time=104ms TTL=254
Reply from 41.240.128.1: bytes=32 time=192ms TTL=254
Reply from 41.240.128.1: bytes=32 time=111ms TTL=254
Reply from 41.240.128.1: bytes=32 time=165ms TTL=254
Reply from 41.240.128.1: bytes=32 time=194ms TTL=254

Ping statistics for 41.240.128.1:
Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 235ms, Average = 157ms
 
Mr Jax,

what are you complaining about???? You can atleast browse with that ping. i can do fukkol if it hits 6pm on my side.

I have the same issue - Latency goes up from 6pm. Not like yours, mine is then between 600-1500ms on local servers.

I have tried everything - i log a fault weekly. Techs dotn find the issue. They also refuse to escalate the issue to SAIX.

Funny thing is - Guy who stays 33 meters away from me HAD the same issue - Yes he had. App Telkom forwarded a FQ number to SAIX and they took care of it. For the living of Gawd - I cant get them to do that.

I had 5 diff technicians here - I have been put on different ports - Issue not resloved - I have offered each telkom tec R1000 if they solve my mysterious issue. Nothing gets done - and I am about to burn down the fscking exchange. I have had this issue for more then 6months now. Each nigh my latency rises. Im gatvol - but depended on that fscken telkom line.
 
Last edited:
Will do. Latency only goes up after 6pm.
But, FYI - 1st hop after router has already the high latency - so it not down the line.
Its clearly the bandwith allocation on our exchange or dslam. Too many users online at the same time. My neighbour has mention that he was connected to a faulty card in th dslam or exchange.
 
Yeah, mine not as bad as yours for sure.

I use my line mostly for online gaming...try playing Quake Live with a ping that hops between 50 and 250 all the time with bursts of throughput issues and bursts of packet loss....you cant.

I call it lag with parkinsons ON STEROIDS :)

blogbytes said:
Mr Jax,

what are you complaining about???? You can atleast browse with that ping. i can do fukkol if it hits 6pm on my side.

I have the same issue - Latency goes up from 6pm. Not like yours, mine is then between 600-1500ms on local servers.

I have tried everything - i log a fault weekly. Techs dotn find the issue. They also refuse to escalate the issue to SAIX.

Funny thing is - Guy who stays 33 meters away from me HAD the same issue - Yes he had. App Telkom forwarded a FQ number to SAIX and they took care of it. For the living of Gawd - I cant get them to do that.

I had 5 diff technicians here - I have been put on different ports - Issue not resloved - I have offered each telkom tec R1000 if they solve my mysterious issue. Nothing gets done - and I am about to burn down the fscking exchange. I have had this issue for more then 6months now. Each nigh my latency rises. Im gatvol - but depended on that fscken telkom line.
Click to expand...
 
I have exactly the same problem in langenhovenpark, Bloemfontein on exchange 051 436. Telkom has also sent about 3 technicians to my house and everytime i have to tell them the problem is at my exchange. My bad latency and packet loss between 15-30% starts around 7pm and only calms down at about 12pm. But not always. Ive had this issue for 13months now and telkom doesnt give a ****!!! Ive also had port changes etc. But now im on a port that is giving port errors. I had to give up competitive gaming until our exchange is upgraded one day. here are my atenuation and SNR rates. They are very good but my exchange is overloaded!!!

ADSL Link Downstream Upstream
Line Attenuation 20.0 db 10.0 db
Noise Margin 30.2 db 13.0 db
 
You think thats bad: Waterford Exchange :(

Same problem: On JHB Waterford Exchange 011 658.
(I am with webAfrica and I have a 4Mb line. I have tried 2 other accounts from IS to Mweb)

Tracert: to wa.co.za

Tracing route to wa.co.za [196.220.63.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 453 ms 419 ms 394 ms dsl-185-69-1.dynamic.wa.co.za [41.185.69.1]
3 463 ms 497 ms * vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 399 ms 329 ms 362 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
5 487 ms 478 ms 373 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
6 375 ms 445 ms 489 ms fe0.er1.gw.cpt.za.wadns.net [41.185.0.4]
7 220 ms 286 ms 290 ms wa-acc1.wadns.net [196.220.39.253]
8 460 ms 488 ms 436 ms 196.220.63.42

Trace complete.
Click to expand...
Routers stats are: Which are good. (I am exactly 1.35KM from my exchange)
Line Attenuation 23.1 db 13.0 db
Noise Margin 26.0 db 18.0 db

I can upload about 50MB in the time it takes me to download about 3-5MB :(

I have had this problem for 4 weeks, since I got my 4Mb line.
And Telkom just does not get it, they have no-clue what ping, latency or contention-ratios are :sick:
I have also had 2 Techs at my house telling me what I already know.:twisted::mad:

Speed test: http://www.speedtest.net/result/921801841.png

Problem is I am sick of 3Gs ridiculous caps and I will never go back to NeoFail. :cry:
So what can I do, I can't pay +R400 p/m for a slow ISDN line :(
 
Last edited:
ShadowRider said:
Same problem: On JHB Waterford Exchange 011 658.
(I am with webAfrica and I have a 4Mb line. I have tried 2 other accounts from IS to Mweb)

Tracert: to wa.co.za


Routers stats are: Which are good. (I am exactly 1.35KM from my exchange)
Line Attenuation 23.1 db 13.0 db
Noise Margin 26.0 db 18.0 db

I can upload about 50MB in the time it takes me to download about 3-5MB :(

I have had this problem for 4 weeks, since I got my 4Mb line.
And Telkom just does not get it, they have no-clue what ping, latency or contention-ratios are :sick:
I have also had 2 Techs at my house telling me what I already know.:twisted::mad:

Speed test: http://www.speedtest.net/result/921801841.png

Problem is I am sick of 3Gs ridiculous caps and I will never go back to NeoFail. :cry:
So what can I do, I can't pay +R400 p/m for a slow ISDN line :(
Click to expand...

Strange indeed...... i pinged your exchange I think yourn 1st connection and looks ok.

C:\Users\Jannie>ping -t 41.185.69.1

Pinging 41.185.69.1 with 32 bytes of data:
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=31ms TTL=251
Reply from 41.185.69.1: bytes=32 time=30ms TTL=251
Reply from 41.185.69.1: bytes=32 time=34ms TTL=251
Reply from 41.185.69.1: bytes=32 time=33ms TTL=251
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=31ms TTL=251
Reply from 41.185.69.1: bytes=32 time=30ms TTL=251
Reply from 41.185.69.1: bytes=32 time=34ms TTL=251
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=30ms TTL=251
Reply from 41.185.69.1: bytes=32 time=125ms TTL=251
Reply from 41.185.69.1: bytes=32 time=34ms TTL=251
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=30ms TTL=251
Reply from 41.185.69.1: bytes=32 time=29ms TTL=251
Reply from 41.185.69.1: bytes=32 time=34ms TTL=251
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=30ms TTL=251
Reply from 41.185.69.1: bytes=32 time=33ms TTL=251
Reply from 41.185.69.1: bytes=32 time=32ms TTL=251
Reply from 41.185.69.1: bytes=32 time=31ms TTL=251
Reply from 41.185.69.1: bytes=32 time=29ms TTL=251
Reply from 41.185.69.1: bytes=32 time=33ms TTL=251

Ping statistics for 41.185.69.1:
Packets: Sent = 47, Received = 47, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 125ms, Average = 33ms

Tracing route to dsl-185-69-1.dynamic.wa.co.za [41.185.69.1]
over a maximum of 30 hops:

1 11 ms 10 ms 9 ms dsl-185-84-1.dynamic.wa.co.za [41.185.84.1]
2 13 ms 9 ms 9 ms vl105.cr.gw.cpt.za.wa.co.za [196.220.59.250]
3 14 ms 14 ms 13 ms vl36.er.gw.cpt.za.wa.co.za [41.185.0.66]
4 12 ms 9 ms 10 ms vl38.cr.gw.cpt.za.wa.co.za [41.185.0.73]
5 9 ms 9 ms 9 ms upstream.vl106.gw.cpt.za.wa.co.za [196.220.59.24
5]
6 104 ms 33 ms 34 ms dsl-185-69-1.dynamic.wa.co.za [41.185.69.1]

Trace complete.
 
Last edited:
@ JAnie

I have the exact same scenario. When my latency rises - which is every night from about 6pm till 10-11ish pm, my download speeds are at about 8-16kb/sec. Upload is fine. Full blast
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X