TelkomZA

Same here :(

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 7 ms 7 ms 6 ms . [192.168.2.1]
2 145 ms 142 ms 119 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 149 ms 156 ms 160 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 167 ms 164 ms 187 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 166 ms 165 ms 147 ms 165.165.216.221
6 144 ms 153 ms 166 ms 196.43.39.166
7 123 ms 126 ms 130 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 157 ms 150 ms 161 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 135 ms 122 ms 112 ms telkom.co.za [196.43.22.222]

Trace complete.
 
I see yours and raise you by 1000ms :<.... PLEASE FIX THIS....

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 1306 ms 1205 ms 1131 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 1180 ms 1328 ms 1304 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 1411 ms 1343 ms 1382 ms 197-80-2-1.jhb.mweb.co.za [197.80.2.1]
5 1302 ms 1305 ms 1285 ms 197-80-5-225.jhb.mweb.co.za [197.80.5.225]
6 1317 ms 1114 ms 940 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 945 ms 1032 ms 1027 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 1276 ms 1286 ms 1287 ms 196.43.25.137
9 1468 ms 1477 ms 1321 ms 196.43.39.166
10 887 ms 1008 ms 1052 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 1130 ms 1137 ms 1172 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 1188 ms 1343 ms 1454 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Some fresh latency :S

Tracing route to www.telkom.co.za [165.143.158.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 962 ms 984 ms 982 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 1103 ms 986 ms 842 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 846 ms 929 ms 967 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 1020 ms 1022 ms 931 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 1091 ms 1078 ms 1166 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 905 ms 952 ms 1026 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 1061 ms 1104 ms 1169 ms 196.43.25.205
9 972 ms 946 ms 994 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.

TelkomZA has gone completely silent in this thread / PMs. Don't know if thats a "we admit defeat, but never publicly" or a "we are attending to the problem and will get back to you when we know more" kind of silence =(
 
Well my problem was sorted this afternoon and if TelkomZA had anything to do with it, I thank you and hope it does not return.
I may be wrong but maybe you guys that are not having much joy should add your Location below your avatar so they can see where the problems are coming from, just a thought.
 
Well - I figure I may as well give this a shot, because I'm not getting much accomplished going through the usual channels.

Brief description of my issue - I've been getting constant line drops for about a month now, and it all started the exact day our exchange was upgraded (Bothasig 021 558). A line on which I once ran a 10Mbps connection now barely manages 4Mbps. My SNR sits below 6dB most of the time, and my Line Attenuation is atrocious - 45dB+.

These are my current stats (I have just restarted my router):

Upstream 385 kbps
Downstream 3019 kbps
SNR Margin (Upstream) 7.1 db
SNR Margin (Downstream) 6.0 db
Line Attenuation (Upstream) 51.4 db
Line Attenuation (Downstream) 48.0 db
 
Just wanting to extend a tentative thank you to TelkomZA, problems with the exchange in Stellenbosch appear to be resolved following their input :)
 
Still bad here... Promises of it being fixed last week already, and 4 faults that have been escalated later... :/
 
Darkon Iramus said:
Still bad tonight... Sigh :(

Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 308 ms 321 ms 375 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 490 ms 441 ms 449 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 447 ms 414 ms 428 ms 197-80-2-1.jhb.mweb.co.za [197.80.2.1]
5 466 ms 446 ms 470 ms 197-80-5-225.jhb.mweb.co.za [197.80.5.225]
6 554 ms 611 ms 661 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 769 ms 789 ms 765 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 764 ms 741 ms 689 ms 196.43.25.137
9 624 ms 740 ms 841 ms 196.43.39.166
10 781 ms 826 ms 731 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 663 ms 610 ms 608 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 350 ms 369 ms 399 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
Click to expand...

sakkiemotto said:
Same here :(

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 7 ms 7 ms 6 ms . [192.168.2.1]
2 145 ms 142 ms 119 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 149 ms 156 ms 160 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 167 ms 164 ms 187 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 166 ms 165 ms 147 ms 165.165.216.221
6 144 ms 153 ms 166 ms 196.43.39.166
7 123 ms 126 ms 130 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 157 ms 150 ms 161 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 135 ms 122 ms 112 ms telkom.co.za [196.43.22.222]

Trace complete.
Click to expand...

Darkon Iramus said:
I see yours and raise you by 1000ms :<.... PLEASE FIX THIS....

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 1306 ms 1205 ms 1131 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 1180 ms 1328 ms 1304 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 1411 ms 1343 ms 1382 ms 197-80-2-1.jhb.mweb.co.za [197.80.2.1]
5 1302 ms 1305 ms 1285 ms 197-80-5-225.jhb.mweb.co.za [197.80.5.225]
6 1317 ms 1114 ms 940 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 945 ms 1032 ms 1027 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 1276 ms 1286 ms 1287 ms 196.43.25.137
9 1468 ms 1477 ms 1321 ms 196.43.39.166
10 887 ms 1008 ms 1052 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 1130 ms 1137 ms 1172 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 1188 ms 1343 ms 1454 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
Click to expand...

StevenC said:
Some fresh latency :S

Tracing route to www.telkom.co.za [165.143.158.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 962 ms 984 ms 982 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 1103 ms 986 ms 842 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 846 ms 929 ms 967 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 1020 ms 1022 ms 931 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 1091 ms 1078 ms 1166 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 905 ms 952 ms 1026 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 1061 ms 1104 ms 1169 ms 196.43.25.205
9 972 ms 946 ms 994 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination
net unreachable.

Trace complete.
/QUOTE]

Damn, you guys have some terribly congested exchanges there! @StevenC almost a full second on your 2nd hop is baaaaaaddd!
Eish, I dunno if TelkomZA has the power to fix that
Click to expand...
 
Woohoo same every night, four faults made to no avail, 2+ weeks with the problem (Had no problem at all for a year).

Current fault has been opened for a week now...

Why has nothing been done?

Tracing route to Telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 682 ms 671 ms 677 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 688 ms 760 ms 817 ms 197-80-132-118.jhb.mweb.co.za [197.80.132.118]
4 957 ms 1028 ms 1042 ms 197-80-2-2.jhb.mweb.co.za [197.80.2.2]
5 797 ms 672 ms 651 ms 197-80-5-241.jhb.mweb.co.za [197.80.5.241]
6 580 ms 616 ms 605 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 488 ms 511 ms 516 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 658 ms 597 ms 560 ms 196.43.25.137
9 1080 ms 1140 ms 1078 ms 196.43.39.166
10 381 ms 400 ms 447 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 464 ms 526 ms 547 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
12 619 ms 659 ms 673 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Same old story again tonight :wtf:

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 81 ms 8 ms 7 ms . [192.168.2.1]
2 167 ms 144 ms 151 ms ti-224-76-01.telkomadsl.co.za [105.224.76.1]
3 137 ms 113 ms 118 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
4 107 ms 99 ms 102 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
5 199 ms 216 ms 198 ms 165.165.216.221
6 143 ms 157 ms 156 ms 196.43.39.166
7 144 ms 129 ms 111 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 77 ms 79 ms 88 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 71 ms 67 ms 72 ms telkom.co.za [196.43.22.222]

Trace complete.
 
Daily Traceroute for the record:

Tracing route to www.telkom.co.za [165.143.158.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.0.1
2 703 ms 729 ms 707 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 765 ms 730 ms 808 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 762 ms 738 ms 797 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 712 ms 818 ms 876 ms 197-84-5-226.cpt.mweb.co.za [197.84.5.226]
6 865 ms 876 ms 921 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 1011 ms 945 ms 803 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 555 ms 537 ms 529 ms 196.43.25.205
9 725 ms 629 ms 562 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

It did start a little later this evening and it has been gradual but eventually unplayable.

A glimmer of hope, I at least got GH (TelkomZA) rep to PM me back after a second request, hopefully this means I am in some sort of queue of getting stuff sorted :)
 
Oh well, looks like the wheels fell of here also.
Maybe they working on something.

Tracing route to www.telkom.co.za [165.143.158.8]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.254
2 319 ms 306 ms 306 ms 41-133-48-1.dsl.mweb.co.za [41.133.48.1]
3 397 ms 419 ms 397 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 329 ms 345 ms 365 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 376 ms 386 ms 373 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
6 390 ms 398 ms 413 ms jhb.telkom-ipnet.co.za [197.80.4.117]
7 323 ms 338 ms 372 ms 196.43.25.137
8 353 ms 374 ms 365 ms 196.43.51.78
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports:
Destination net unreachable.

Trace complete.
C:\>
 
Would love to hear how I have a 2 month fault that eventually gets fixed - laying of new cable - and 4 days later I have no internet or (more importantly) phone again?
 
6th technician AND a specialist (apparently), yet my problem is STILL not fixed. Same ****, during busy times connection is unstable and drops all the time... Seriously, how hard can it be to fix this?!
 
hereticangel said:
have a look at parow dslam having congestion issues.

ranges are 021 939 xxxx and 021 930 xxxx , 2 different exchanges but same dslam , it is 10mbs enabled.
Click to expand...

Yes please help with this.. i am on the 021 930 xxx and i just can't do fokkol in the evenings neither over weekends no point even trying to be on the internet over weekends at all.

I have allso send you a PM if you can assist it would be appreciated.

How are we suppose to work on the internet with the following results:

Ping statistics for 196.2.63.110:
Packets: Sent = 613, Received = 423, Lost = 190 (30% loss)
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 872ms, Average = 48ms
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X