TelkomZA

TelkomZA , have you received my PM? I haven't gotten a reply from you yet. We have very bad congestion problem at our exchange in Elarduspark, the line is very unstable in the evening during weekdays and in the late afternoon ( about 5-6 ) during weekends.
 
Cape Town southern suburbs. Line just stopped syncing - this is happening way to often now.
 
Stellenbosch central - 1000+ ms latency to cape town servers. Several people had this same issue a while back, but it was fixed about a month or so ago. It seems to be back.
 
TelkomZA, I am having the exact same problem as StevenC as per the PM I sent you.

I am in Centurion,Clubview-East, why is it that so many of us are having this problem that points to overcrowded exchanges. Surely Telkom must know if they have a problem on the exchange?

It becomes a very painful experience to go through the whole process of reporting the fualt- Telkom says line test fine and sends SMS "problem Resolved" When clearly the problem is far from resolved and we are stuck with an unusable internet connection and still paying for it as well??:mad:

StevenC said:
Welcome to the forum Telkom rep - I hope you can keep pace with the amount of very unhappy ADSL clients you have!

I have had an issue with my exchange for the last couple of weeks resulting in almost unusable internet. As an online gamer, Telkom is costing me money in subscription fees and still making me pay them for the privelage too!

I have reported this already last week using 10210 but as usual, everything but the exchange is the issue. Fault Number: 212CWK130713 was closed on 18th July as being "restored". This was after a promise from a technician who asked me to remind him on the 17th that he must come to my location on the 18th to test the line and then does not have his phone on for the entire day! Very disappointing service. The 10210 technician conducted the port reset and then was fairly useless after that.

Just to add, this very high latency only occurs in the evenings and over weekends (spikes up and down throughout the day). I work most days but I occasionally have a day off during the week at which point I see 12ms ping on the second hop of the exchange which is further evidence that there is nothing wrong with my line, router, ISP(s), computer or DSL filter. What makes this even worse is one of my friends living just around the corner from me is connected to a different exchange and he experiences none of these problems! Client's should be able to request an exchange move without having to move house.

Here are some complimentary traceroutes from 2 ISPs conducted now (9:05PM - 21/07/2013).

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 732 ms 772 ms 770 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 863 ms 968 ms 1056 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 845 ms 895 ms 931 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 714 ms 652 ms 704 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 858 ms 993 ms 940 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 646 ms 608 ms 645 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 790 ms 839 ms 879 ms 196.43.25.205
9 962 ms 832 ms 705 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.

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 644 ms 684 ms 755 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 951 ms 980 ms 906 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 1000 ms 1006 ms 751 ms 41.181.198.188
5 804 ms 631 ms 605 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 967 ms 961 ms 830 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.143]
7 770 ms 801 ms 890 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.197]
8 855 ms 731 ms 645 ms 196.43.25.205
9 929 ms 955 ms 792 ms 196.43.51.78
10 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

The exchange is: WWG+

Telkom needs to really step their game up. Deny ADSL applications until there is room at the exchange for them. Create a congested exchange report option on the 10210 phone number. It takes about 3 to 5 minutes to even get through to someone who then just ignores the overwhelming evidence pointing to exactly what the issue at hand is. I know they have a checklist to run through and not everybody is technically minded but this is as clear as day!

Apologies for the long post - I just had to get that all off my chest to someone who is quite possibly in a position to get things resolved!
Click to expand...
 
sakkiemotto said:
TelkomZA, I am having the exact same problem as StevenC as per the PM I sent you.

I am in Centurion,Clubview-East, why is it that so many of us are having this problem that points to overcrowded exchanges. Surely Telkom must know if they have a problem on the exchange?

It becomes a very painful experience to go through the whole process of reporting the fualt- Telkom says line test fine and sends SMS "problem Resolved" When clearly the problem is far from resolved and we are stuck with an unusable internet connection and still paying for it as well??:mad:
Click to expand...

Hi Sakkiemotto

Whats your area code think we on same exchange also been getting problems as of late

I have sent a PM to TelkomZA
 
Please help TelkomZA - Going on day 3 without Internet since my port was moved - The line syncs perfectly, but the Internet isn't connecting - Apparently they still need to run the jumpers, but I can't see why this is taking so long.
 
sakkiemotto said:
My area code is 0157, from what I can see my Exchange Name/Code is Eldoraigne TEDO03
Click to expand...


We on the same exchange, there was congestion there last year took three months of fighting to get it resolved now its back

@TelkomZA please help us, this only further proves that exchange is congested at peak times
 
Last edited:
Im also part of that area having the same problem... starts around 4PM to get bad - and is totally unusable all times of the weekend.
 
MickeyD said:
Ensure that you send ALL your details to TelkomZA via a PM. If there are multiple complaints on the same DSLAM it will get fixed faster...
Click to expand...
I don't think that is necessarily true.

The type of issue is not always the same for a congested exchange.

1. Exchange is on ATM backhaul, to fix congestion it needs to be upgrade to Metro Ethernet.
- This type of congestion, will need many complaints, but will regardless take long to fix because lots of manual labor is involved in upgrading the backhaul

2. Exchange is on ME backhaul, but running at the capacity of a policy rate limit placed on the port to the DSLAM
- This type of congestion takes seconds to upgrade the policy if there is enough spare capacity on the link. You just need to get through to the right person to help you. I tried the callcenter, another contact who escalated it...nothing happened for months. Finally contacted TelkomZA on here, and while the rep said it would take 2 weeks, I noticed an immediate change that very same evening, which was last week Tuesday I think, and over the week and weekend it kept staying great.

Also, for my DSLAM, I didn't see any complains about it anywhere else, even people I found online who are on the same DSLAM didn't even notice!! Since they don't play games ect, and the DSLAM only shown high latency so far, but mostly downloads were still fine. So I guess I was the only one (that I know about at least) that complained.
 
In Centurion / The reeds section - I think its 0157 area? but yeah, everything fine until 6:10pm, now sitting with 1200 ping to local servers.

This has been going on for almost two weeks to no avail :(

Exchange congested?
 
Big thank you to TelkomZa and his guys/gals....After nearly two years of having inconsistent connection and moaning and complaining and Telkom just checking at exchange level...when it was hot it was steaming, when cold, bloody frustrating...Telkom techie came out this morning, did a full analysis of the line...I have now have a stable 4Mbs line...Thanks guys!! Much appreciated!!
 
Darkon Iramus said:
In Centurion / The reeds section - I think its 0157 area? but yeah, everything fine until 6:10pm, now sitting with 1200 ping to local servers.

This has been going on for almost two weeks to no avail :(

Exchange congested?
Click to expand...

Whats you first 6 numbers of your phone line ?
 
Darkon Iramus said:
012661
Click to expand...

Your on ROOIHUISKRAAL (TRHK02) Exchange.

Is it still bad ?

I am noticing tonight my latency is back to normal wonder if TelkomZa managed to do something

Another forum user on same exchange as me got message from TelkomZA that it might be congestion on the Exchange uplink

BTW I see on broadbandstats.co.za TRHK02 is connected to TRHK and TRHK is connected to EDO (my exchange) wonder if there is a relation to the problem
 
Another fantastic evening of completely unusable internet!

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 992 ms 924 ms 872 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 828 ms 944 ms 950 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 752 ms 816 ms 853 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 829 ms 892 ms 1002 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 797 ms 713 ms 646 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 796 ms 1008 ms 1096 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 902 ms 942 ms 1008 ms 196.43.25.205
9 966 ms 928 ms 657 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

TelkomZA - I shall post a traceroute tomorrow during the day as I will be at home and you shall see the difference it makes.

And then I shall post one every evening until something gets fixed :)
 
StevenC said:
Another fantastic evening of completely unusable internet!

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 992 ms 924 ms 872 ms 41-135-70-1.dsl.mweb.co.za [41.135.70.1]
3 828 ms 944 ms 950 ms 196-28-178-222.adsl.mweb.co.za [196.28.178.222]
4 752 ms 816 ms 853 ms 197-84-2-2.cpt.mweb.co.za [197.84.2.2]
5 829 ms 892 ms 1002 ms TenGigE0-0-0-2.11.cpt-p-2.mweb.co.za [196.28.178.98]
6 797 ms 713 ms 646 ms tengig0-0-0.cpt-pr-2.mweb.co.za [197.84.4.165]
7 796 ms 1008 ms 1096 ms cpt.telkom-ipnet.co.za [197.84.4.21]
8 902 ms 942 ms 1008 ms 196.43.25.205
9 966 ms 928 ms 657 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.43.25.146]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

TelkomZA - I shall post a traceroute tomorrow during the day as I will be at home and you shall see the difference it makes.

And then I shall post one every evening until something gets fixed :)
Click to expand...

The congestion on your line is the worst I have seen :p.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X