LATENCY!!!

I've been informed that the backhaul capacity on Clareinch 9 was upgraded and the connectivity fault in the area was cleared at around 16h30. I'm not convinced that this is the full extent of the cause of the latency in the area,but let's see if there is any improvement.
 
I'm still on Clareinche 6 at the moment but last night was a very good night. Telkom teccie phoned me this morning about my request to be switched back to my old dslam - asked me to unplug everything in the house, and he apparently still sees a fault on the line so he's coming out today. I'm curious to see what this is because everything seems to be fine that I can see, except for the latency issues which have been affecting everyone on Clareinche. Maybe he's noticed the lack of fibre in my 3.5km of copper and is going to suggest putting a mini-dslam on my pavement (I live in hope).
 
Turns out my line was just coming into contact with another line which explains why it deteriorated a bit after heavy rains. Same latency problem again last - it went all pear shaped at about 6:15pm and only recovered just before 11pm. Usual story.
 
Same again tonight. I noticed this on the MWeb Status Notices:

Outage Num:8746
Telkom ADSL outage affecting Clareinch ( 021 - 671, 674 & 683 )
Telkom ADSL services in the following area may be Inaccessible : Clareinch ( 021 - 671, 674 & 683 )
Start Date:2010-10-04 09:59:03
End Date:2010-10-04 16:28:16
Status:Closed

Whatever this was for, it hasn't improved anything for me tonight. In fact my latency has been bad since 9am - never returned to normal once today. I wonder if they are now only focusing on specific dslams at Clareinche.
 
@teRRRier I'm still chasing this.

We were flooded with calls from Clareinch on Friday covering at least 4 DSLAMS, only a fault on DSLAM 9 was confirmed. As you can see from todays notice there are now other confirmed faults in the exchange. I manage the team that oversees this process and we put a lot of focus on detecting fault trends and reporting these issues to Telkom.

I was also assured that the previous fault I raised was due to utilization on the Clareinch 9 backhaul link which was upgraded on Thursday, or Friday.

I will speak to my contacts tomorrow and ensure that some attention gets focused on your DSLAM - if I have to get them to fix it one DSLAM at a time, then so be it :D
 
Thanks WATCHDOG@MWEB. I always thought these status notices were just reports of notifications received from Telkom. So these are rather cases where MWEB is picking up potential faults itself and then reporting them to Telkom. Excellent.

Release the hounds!
 
That's one of my favorite sayings :)

The notices are actually a combination of confirmed Telkom faults and those detected and reported to them using our own trends.
 
A little late joining this thread - has anything been mentioned about the same symptoms in the CBD area? For quite a while now (at least a week?) I've also been experiencing >100 pings.
 
This is super annoying. It must be a Telkom fault. I am a WebAfrica subscriber and have been experiencing the same problem.

Traceroute through webafrica account:
1 <1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms dsl-185-88-1.dynamic.wa.co.za [41.185.88.1]
3 8 ms 7 ms 8 ms vl108.cr.gw.cpt.za.wa.co.za [196.220.59.238]
4 8 ms 8 ms 8 ms vl34.er.gw.cpt.za.wa.co.za [41.185.0.34]
5 154 ms 150 ms 148 ms upstream.vl101.gw.cpt.za.wa.co.za [196.220.59.226]
6 168 ms 161 ms 164 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
7 177 ms 171 ms 165 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 179 ms 178 ms 174 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
9 157 ms 153 ms 154 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

And then a traceroute through an Axxess prepaid account:

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

1 1 ms <1 ms <1 ms 192.168.66.1
2 6 ms 6 ms 6 ms 196-210-152-1.dynamic.isadsl.co.za [196.210.152.1]
3 143 ms 141 ms 136 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 158 ms 161 ms 164 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 176 ms 162 ms 155 ms 168.209.1.140
6 125 ms 128 ms 128 ms 168.209.1.170
7 178 ms 181 ms 177 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181]
8 156 ms 156 ms 156 ms 196.43.25.137
9 171 ms 163 ms 158 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
10 155 ms 161 ms 167 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
11 176 ms 165 ms 158 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
12 165 ms 164 ms 172 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

It is also very time-dependent. Late at night it is fine - have not been able to test it throughout the day.
 
Yep, it used to be from about 6:30pm until about 11pm, but for the last few days it has worsened and now I'm seeing 5x normal latency from around 9am to 11pm.
@Johand - which area of Cape Town are you in?
 
Last edited:
teRRRier said:
Yep, it used to be from about 6:30pm until about 11pm, but for the last few days it has worsened and now I'm seeing 5x normal latency from around 9am to 11pm.
@Johand - which area in Cape Town are you in?
Click to expand...

Rondebosch, Belmont Rd Exchange (021686xxxx).
 
+1

I've just sent comparative ping and tracert results to my Telkom escalation point. On Clareinch 9 I get an average latency to a popular local site of 198ms, from our test bench the reading is 47ms.
 
This is getting ridiculous

1.5 MONTHS and nothing has been done about it. I have 20 Reference numbers, every morning they are cleared. WTF is wrong with these people.

Im in Sybrand Park and connected to the Crawford Exchange. This is really iritating.

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

1 <1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 8 ms 7 ms 7 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 176 ms 180 ms 179 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 200 ms 157 ms 158 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 178 ms 180 ms 182 ms 168.209.1.140
6 175 ms 171 ms 169 ms 168.209.1.170
7 151 ms 144 ms 142 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127
.181]
8 153 ms 156 ms 163 ms 196.43.25.137
9 181 ms 181 ms 184 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.
43.8.146]
10 139 ms 138 ms 139 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 182 ms 180 ms 175 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 175 ms 166 ms 167 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
@jpmonster Could I get the 1st 6 digits of your number? - in private if you'd prefer. I'm trying to build a better understanding of how widespread the problem is and I'd like to add your tracert to what I have so far for the evening in relation to the dslam you're connected to.
 
and Yep. 11:15, pings are bag to normal

Trace complete.

tracert telkom.co.za

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 8 ms 7 ms 8 ms dsl-242-172-01.telkomadsl.co.za [41.242.172.1]
3 30 ms 29 ms 29 ms cdsl2-rba-vl2663.ip.isnet.net [196.38.73.25]
4 30 ms 30 ms 28 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 29 ms 29 ms 29 ms 168.209.1.140
6 29 ms 31 ms 48 ms 168.209.1.170
7 29 ms 30 ms 30 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127
.181]
8 29 ms 30 ms 30 ms 196.43.25.137
9 30 ms 29 ms 30 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.
43.8.146]
10 30 ms 30 ms 31 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 55 ms 33 ms 33 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 34 ms 33 ms 33 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

sigh
 
Exactly - every day the same. From about 9am to 11:30 it's as fast as a snail through honey. I'm thinking of investing in some carrier pigeons (TIP - don't get homing pigeons, they just keep bringing all your sent packets right back to you). hehehe
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X