TelkomZA

Look at this... a little better but just as bad.

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.1
2 348 ms 268 ms 280 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 164 ms 200 ms 199 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 192 ms 207 ms 186 ms 197-80-2-1.jhb.mweb.co.za [197.80.2.1]
5 112 ms 112 ms 105 ms 197-80-5-225.jhb.mweb.co.za [197.80.5.225]
6 100 ms 110 ms 129 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 158 ms 127 ms 125 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 112 ms 112 ms 51 ms 196.43.25.137
9 26 ms 22 ms 24 ms 196.43.51.78
10 * * * Request timed out.
11 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: De
stination net unreachable.


EDIT: IT just got way worse.....

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.1
2 307 ms 266 ms 307 ms 41-133-100-1.dsl.mweb.co.za [41.133.100.1]
3 333 ms 394 ms 446 ms 197-80-4-106.jhb.mweb.co.za [197.80.4.106]
4 546 ms 524 ms 455 ms 197-80-2-1.jhb.mweb.co.za [197.80.2.1]
5 529 ms 585 ms 659 ms 197-80-5-225.jhb.mweb.co.za [197.80.5.225]
6 712 ms 695 ms 706 ms tengig0-0-0.vic-pr-1.mweb.co.za [197.80.4.141]
7 632 ms 652 ms 664 ms jhb.telkom-ipnet.co.za [197.80.4.117]
8 783 ms 814 ms 696 ms 196.43.25.137
9 448 ms 484 ms 442 ms 196.43.51.78
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] re
ports: Destination net unreachable.
 
Last edited:
This is my last cry of desperation!

It's been 3 months since the upgrade, or should I say "upgrade" to our local exchange. For 3 months the line is TOTALLY unstable, drops every 10-30 mins during peak hours, 1-2 hours during off-peak, weekend 1-2 minutes (if I'm lucky). I've had 5 technicians look at the problem, all to find nothing at my size, and apparently nothing at your end.

Now, this isn't rocket science, we all know where the problem is, the exchange got upgraded to speed up line speeds, and now all of a sudden the connections are unstable. The exchange is congested, and no one seems to want to do anything about it. For the amount I am paying, this is completely unacceptable to have this problem going on for 3 months.

PLEASE do something about it, I am at the end of my sanity. I really wish there was another provider, but the sad truth to Telkom not allowing other infrastructure will never see anything happen.

It's a joke.

558 Area Code (Bothasig CT exchange) You'll see how many times the line drops and how many people have "tried" to fix it and did nothing!
 
Last edited:
nerf said:
Technician came to my house I explained the problem and he said there are too many customers on the Card at the DSLAM im connected to, he said he was going to move me to another card. Will see tonight how it goes
Click to expand...

Exact same problem, but 3 months of waiting and no fix for me (558 area code in CT)
 
All this nonsense started when the rolled out the 20 & 40 mbit ADSL.
 
The silence of TelkomZA are deafening. I hope it's because he is busy resolving these issues.

Are you still there?.
 
After moving me to a new card on the DSLAM with fewer users the latency is now acceptable but not as good as it was, used to get 9 ms to google

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 10 ms 7 ms 6 ms 105.236.4.129
3 11 ms 9 ms 9 ms 41.181.178.89
4 27 ms 22 ms 29 ms 196.44.0.146
5 10 ms 11 ms 11 ms 196.44.31.95
6 35 ms 10 ms 11 ms 41.181.165.115
7 40 ms 41 ms 39 ms 72.14.194.74
8 45 ms 37 ms 34 ms 64.233.174.57
9 12 ms 13 ms 14 ms 74.125.233.87

Trace complete.
 
nerf said:
After moving me to a new card on the DSLAM with fewer users the latency is now acceptable but not as good as it was, used to get 9 ms to google

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 10 ms 7 ms 6 ms 105.236.4.129
3 11 ms 9 ms 9 ms 41.181.178.89
4 27 ms 22 ms 29 ms 196.44.0.146
5 10 ms 11 ms 11 ms 196.44.31.95
6 35 ms 10 ms 11 ms 41.181.165.115
7 40 ms 41 ms 39 ms 72.14.194.74
8 45 ms 37 ms 34 ms 64.233.174.57
9 12 ms 13 ms 14 ms 74.125.233.87

Trace complete.
Click to expand...

I would rather take that than the 700 ping im getting... What should i tell them to do? i was getting the same problem as you i think? Please i cant take this anymore
 
I wouldn't complain about 3 ms as there is bound to be a small amount of variance...

Anyways, here is my evening traceroute for the third day in a row:

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 957 ms 846 ms 714 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 755 ms 572 ms 713 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 907 ms 833 ms 863 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 932 ms 899 ms 957 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 896 ms 1011 ms 753 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 635 ms 932 ms 854 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 651 ms 808 ms 828 ms 196.43.25.205
9 693 ms 842 ms 805 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.

This is with no internet traffic running. It has been bad since 5pm this evening!
 
Darkon Iramus said:
I would rather take that than the 700 ping im getting... What should i tell them to do? i was getting the same problem as you i think? Please i cant take this anymore
Click to expand...

The solution was the Technician who knew what congestion is and how to try and fix it
 
Please fix your SSL cert for online bill payment, it expired yesterday

ebpp.telkom.co.za
 
So are problems being sorted here by the Telkom rep or has he realised that it doesnt matter and his salary remains the same either way? :D
 
Are you kidding me......TelkomZA (GH ) is flippen awesome. Lotsa <3 to him for all the hard work so far.

Our line was noisy so we have so many ways to log a fault.

in no particular order

1. Social media (Twitter, Facebook and here)
2. SMS
3. Phoning

So PM'd and within an hour our noisy line is super clear. Dad can talk to mum tonight without repeating each other :D

Thanks very much.
 
sakkiemotto said:
I will definitely give TelkomZA the thumbs up if he gets my problem sorted, only time will tell.
Click to expand...

Yup...

Sorry @Yuu guess they trying their best... but I'm so upset right now that Telkom and TelkomZA promised me a date and never delivered, costing me a lot of revenue.. i.e. one month of 3g data, data from afrihost which i could not use due to no adsl etc. all adds up...
 
Last edited:
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.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X