Clareinch (Claremont Exchange) Congested

zolly said:
The social media team is supposed to have better trained staff than the call center, so they should understand what ping and latency is.

I'll see if I can find the regional manager's contact info.
Click to expand...

I thought so too but it seems they don't get taught it :), I got the number from my friend in the Telkom Direct Store and they emailed him on my behalf.
 
jeanres said:
For reference

View attachment 138670
Click to expand...

Also, tell them it's an ESR port at the exchange, not the exchange itself, and that another member of their team has identified and acknowledged the problem. If you want to tell them anything, tell them you want to know an ETA on the solution since you already know the problem exists.
 
ichigo said:
I thought so too but it seems they don't get taught it :), I got the number from my friend in the Telkom Direct Store and they emailed him on my behalf.
Click to expand...

I don't have any friends at Telkom. I might have to go to a store and throw a hissy fit just to get some results.
 
Anthro said:
I can tell you its oversubscribed
View attachment 138684
Click to expand...

I used to get that as well but it seems like all our complaining is getting somewhere because now all I get is "Your speed cannot be determined at this time"

Also for the record:

AFRIHOST

05 August 2014 9:09PM

C:\Users\Chris>tracert google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 120 ms 118 ms 122 ms 105-236-6-1-esr-lo.mtnbusiness.co.za [105.236.6.1]
3 131 ms 132 ms 130 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 143 ms 143 ms 136 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 140 ms 135 ms 132 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 269 ms 270 ms 273 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 281 ms 275 ms 277 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
8 273 ms 292 ms 283 ms rb-ad-1--msbm-rbg-1-a.mtnns.net [209.212.99.13]
9 270 ms * * 209.85.255.76
10 289 ms 282 ms 288 ms 72.14.238.21
11 279 ms 281 ms 272 ms lhr14s23-in-f24.1e100.net [74.125.230.88]

Trace complete.

06 August 2014 1:29PM

C:\Users\Chris>tracert google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 5 ms 105-236-6-1-esr-lo.mtnbusiness.co.za [105.236.6.1]
3 8 ms 8 ms 8 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 8 ms 8 ms 8 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 9 ms 16 ms 10 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 163 ms 154 ms 152 ms ls-cr-2.uk--tb-cr-1.za.mtnns.net [196.44.31.113]
7 152 ms 151 ms 152 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.187]
8 151 ms 152 ms 151 ms rb-ad-1--msbm-rbg-1-a.mtnns.net [209.212.99.13]
9 156 ms 152 ms 154 ms 209.85.255.78
10 153 ms 153 ms 152 ms 72.14.238.55
11 153 ms 151 ms 151 ms lhr08s03-in-f15.1e100.net [173.194.41.143]

Trace complete.

TELKOM

06 August 2014 12:45PM (the afternoon. Not night :P)


C:\Users\Chris>tracert google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms ti-224-100-01.telkomadsl.co.za [105.224.100.1]
3 8 ms 7 ms 8 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 8 ms 8 ms 8 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 7 ms 7 ms 7 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153]
6 29 ms 29 ms 29 ms rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za [196.43.52.38]
7 30 ms 31 ms 31 ms 72.14.212.1
8 30 ms 30 ms 30 ms 64.233.174.21
9 31 ms 30 ms 30 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.

06 August 2014 9:00PM

C:\Users\Chris>tracert google.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 137 ms 135 ms 135 ms ti-224-100-01.telkomadsl.co.za [105.224.100.1]
3 143 ms 144 ms 141 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 137 ms 136 ms 134 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 201 ms 196 ms 184 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39.45]
6 148 ms 143 ms 144 ms rrba-ip-lir-1-gig-5-0-0.telkom-ipnet.co.za [196.43.52.38]
7 159 ms 159 ms 158 ms 72.14.212.1
8 157 ms 164 ms 156 ms 64.233.174.21
9 149 ms 151 ms 159 ms jnb01s01-in-f23.1e100.net [74.125.233.55]

Trace complete.

Used both telkom and Afrihost accounts, just to prove it's not an isp issue. Took the liberty of pointing out second hop (exchange hop) ping.

P.S I only realised the other day that Afrihost/MTN don't have a locally cached google.co.za what the hell?
 
So I'm moving to Claremont soon. I messaged TelkomZA for ETA of my adsl line -
Good afternoon.

There is no ETA at this time. The network has to be upgraded in your area to accommodate the request.
Feedback states that you will be contacted within the next month to schedule an appointment if there are no unforeseen circumstances.
Click to expand...
At least they realised that clareinch needs to be upgraded.
 
Last edited:
ajan said:
So I'm moving to Claremont soon. I messaged TelkomZA for ETA of my adsl line -

At least they realised that clareinch needs to be upgraded.
Click to expand...

Yeah, but an ETA on an issue that was discovered in April would be nice...
 
Currently have mixed feeling about moving to Claremont all of a sudden. :D:cry:
 
seems ok tonight

│traceroute to github.com (192.30.252.131), 64 hops max, 52 byte packets
│ 1 192.168.1.1 (192.168.1.1) 1.348 ms 0.840 ms 0.678 ms
│ 2 dsl-197-245-24-1.voxdsl.co.za (197.245.24.1) 5.690 ms 6.197 ms 7.275 ms
│ 3 196.41.29.166 (196.41.29.166) 9.285 ms 7.763 ms 7.173 ms
│ 4 196.41.29.233 (196.41.29.233) 7.747 ms 7.448 ms 9.273 ms
│ 5 196.41.24.114 (196.41.24.114) 153.527 ms 154.015 ms 152.485 ms
│ 6 195.50.120.13 (195.50.120.13) 169.524 ms 203.018 ms 164.939 ms
 
jeanres said:
seems ok tonight

│traceroute to github.com (192.30.252.131), 64 hops max, 52 byte packets
│ 1 192.168.1.1 (192.168.1.1) 1.348 ms 0.840 ms 0.678 ms
│ 2 dsl-197-245-24-1.voxdsl.co.za (197.245.24.1) 5.690 ms 6.197 ms 7.275 ms
│ 3 196.41.29.166 (196.41.29.166) 9.285 ms 7.763 ms 7.173 ms
│ 4 196.41.29.233 (196.41.29.233) 7.747 ms 7.448 ms 9.273 ms
│ 5 196.41.24.114 (196.41.24.114) 153.527 ms 154.015 ms 152.485 ms
│ 6 195.50.120.13 (195.50.120.13) 169.524 ms 203.018 ms 164.939 ms
Click to expand...

I know, but this also happened the one Saturday night a couple of weeks back. Fingers crossed they actually fixed it.
 
The problem is when they test it and clear the fault is when it is fine and they never test it at night when the problem arises so you have to get the regional manager to get someone to test at night or you won't ever get anywhere or get it fixed unfortunately :)
 
ichigo said:
The problem is when they test it and clear the fault is when it is fine and they never test it at night when the problem arises so you have to get the regional manager to get someone to test at night or you won't ever get anywhere or get it fixed unfortunately :)
Click to expand...

Well it's been ages since it's been this good (touch wood) so we'll see if they've fixed it or not.
 
Not going to close my fault unless it clears my tracert every night around 9-10pm for a week. Spent this long explaining my problem and I've finally found a telkom rep who agrees with me and knows whats going on. Not going to lose him over 1 good night.
 
Agreed. My suspicion is that all our combined complaining got someone to go have a look at it and they've done some load balancing.

As a temporary measure this is great. If this is their "replacement solution" I'm not so happy. I can see this going back to being congested in a month or two.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X