Telkom, please fix this

Question for the gurus

Don't all adsl connections physically terminate with SAIX and from there your traffic is routed to your ISP (if need be) ?

Can't this problem lie within the SAIX realm ?
 
Yes, my neighbour had saix involved and they fixed his issue.

I cant get saix involved - they refuse to help me without a "FQ number". Note, FQ number is not a normal fault number from telkom.

Just to show you what my ping does on a saturday. This is what I have to deal with on a Saturday and Sunday - the entire day.

C:\Users\JP>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 sx762.dummy.porta.siemens.net [10.0.0.2]
2 1622 ms 1548 ms 1537 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 1502 ms 1526 ms 1506 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 1579 ms 1448 ms 1564 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 1427 ms 1337 ms 1286 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 1171 ms 1213 ms 1181 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 1131 ms 1130 ms 1152 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
8 1400 ms 1418 ms 1292 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
9 1429 ms 1444 ms 1397 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
10 1277 ms 1442 ms 1620 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
 
Yeah that sucks on a epic scale...totally unusable.

Well, I emailed [email protected] last night and just got a call from them. Thinking it was TelkomInternet Support...it wasn't.
Log story short, the bloke tells me he can see that the exchange is not running at full capacity (so its not congested) while at the same time my ping hovers at 150 odd. He will now forward the details onto Telkom Internet so that they can take it further.

I'm optimistic; this might just go in the right direction now.

I bet ya its something that went pear shaped on SAIX....

Thanks to the telkom bloke who took the time to read my e-mail and actually understand what I'm on about; he was very helpful and this might just restore my faith in them....Please don't disappoint me again.
 
You have an emai addressl from that guy that seems to understand your issue?
 
Hmm. After quite a few days of not having this issue. It's back once again >_> damn lol
 
ShadowRider said:
Same problem: On JHB Waterford Exchange 011 658.
(I am with webAfrica and I have a 4Mb line. I have tried 2 other accounts from IS to Mweb)

Tracert: to wa.co.za


Routers stats are: Which are good. (I am exactly 1.35KM from my exchange)
Line Attenuation 23.1 db 13.0 db
Noise Margin 26.0 db 18.0 db

I can upload about 50MB in the time it takes me to download about 3-5MB :(

I have had this problem for 4 weeks, since I got my 4Mb line.
And Telkom just does not get it, they have no-clue what ping, latency or contention-ratios are :sick:
I have also had 2 Techs at my house telling me what I already know.:twisted::mad:

Speed test: http://www.speedtest.net/result/921801841.png

Problem is I am sick of 3Gs ridiculous caps and I will never go back to NeoFail. :cry:
So what can I do, I can't pay +R400 p/m for a slow ISDN line :(
Click to expand...

I'm On the exact same exchange as you and am having the same issue, except my line is a 384kb line, this is the thread I opened. http://mybroadband.co.za/vb/showthr...sue-Telkom-doesn-t-know?p=4556161#post4556161
 
UPDATE:

As expected, nothing came of it......I was promised that the details would be sent to Telkom Internet etc, but absolutely nothing happened.
In stead, I got a call from some or other company conducting a customer satisfaction survey wrt dealing with the Telkom escalation centre.
She asked me if I had contact with them and I just started laughing and commented I had nothing to say thanks bye.....

Shortly after I received an SMS of a fault number opened.
Long story short, I had a long civilised discussion with some lady at the escalation centre explaining in detail what the issue is.....
Now SHE promised to forward this on to her manager to take it to the correct department in Telkom.
At the same time, a telkom techie is now assisting the best he can. We met today, discussed the problem a bit etc.

I told him this starts around 6PM, well he called me just after 6PM wanting to know whats going in and as always...bad latency...pretty much started the moment he called LOL.

So tomorrow we meet up again, probably going to test the line or whatever (pointless IMO).

I did gather from him that the exchange backhaul is not served by fibre, but using ATM links I suppose....

So, lets wait and see whats going to happen here. My money is on an oversubscribed exchange with insufficient backhaul; I hope I'm wrong.
 
Sorry to hear Mr Jax.

Also here on my side nothing new. Techies been here digging up all point out the manholes. My cable was literally frot. He cut the bad piece off which caused noise.
My Techie is also certain its a traffic issue. Too many users online at the same time. He has forwarded my issue as many time before to a "spcialist" This was 2 weeks ago. Nothing new.

Im going to dispute each month a certain amount of the adsl line rental. 4-5 hours a day I am not willing to pay - as my Internet is really not usable. Will see how quick they are on the issue then.
 
I dream of a day where we can all get wonderful pings and download/upload speed. What scares me though is I may not live to see it. Cause going by how we're doing. I dont see it happening anytime soon :o That is.. if it will happen :p

Also @Mr.Jax

Sorry to hear about telkom. Not surprised though.
Getting anywhere with telkom is harder than getting a sick dog to eat it's food. They just dont seem to really care. And alot of the staff on the phones, I think judging by how they "try" help. They just are probably people who hardly have been trained if even trained at all. Their support is slow and they certainly dont sound like they care. maybe Im just unlucky when I've had to phone them. But yeah. Going by my experience with them, their "world class service" isn't really so.. world class.

But I guess talking about their service isn't really helpful.

So in regards to you using iburst, would you say their service is any good :o ? I've been wanting to get myself a wireless card for when I leave home for a week or so when I visit my dad in Durban. Cause I really need to be able to do my work as it's a 24/7 job online so yeah.
 
Grimster101,

A lot of forumites complain a lot about iBurst but I've never had any issues with them. What heps is that there's an active iburst representative on these forums and he gets things done!
Now that helps a helluva lot compared to Telkom.
 
Mr.Jax said:
Grimster101,

A lot of forumites complain a lot about iBurst but I've never had any issues with them. What heps is that there's an active iburst representative on these forums and he gets things done!
Now that helps a helluva lot compared to Telkom.
Click to expand...

Hmm interesting. I should check em out again sometime. But yeah. Might just be better leaving it as I dont go to see my dad often. Thanks for the reply though =]
 
Little update from my side.

Received this email from my Telkom techie.
Please check for any difference in latency, GDB 1 & 2 rerouted to a different STM-1 link, should be OK now.

Since Friday my latency seems stable. @ MR Jax - maybe you can ask them to also reroute you as well on ot a diff STM-1 link.
 
Some more stats...still going strong every evening....

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.1.1
2 * * * Request timed out.
3 145 ms 137 ms 128 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
4 145 ms 153 ms 135 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
5 146 ms 145 ms 136 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
6 126 ms 118 ms 117 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]1

Trace complete.

ping -t 41.240.188.1

Pinging 41.240.188.1 with 32 bytes of data:
Reply from 41.240.188.1: bytes=32 time=65ms TTL=254
Reply from 41.240.188.1: bytes=32 time=57ms TTL=254
Reply from 41.240.188.1: bytes=32 time=18ms TTL=254
Reply from 41.240.188.1: bytes=32 time=27ms TTL=254
Reply from 41.240.188.1: bytes=32 time=89ms TTL=254
Reply from 41.240.188.1: bytes=32 time=117ms TTL=254
Reply from 41.240.188.1: bytes=32 time=156ms TTL=254
Reply from 41.240.188.1: bytes=32 time=130ms TTL=254
Reply from 41.240.188.1: bytes=32 time=151ms TTL=254
Reply from 41.240.188.1: bytes=32 time=226ms TTL=254
Reply from 41.240.188.1: bytes=32 time=121ms TTL=254
Reply from 41.240.188.1: bytes=32 time=130ms TTL=254
Reply from 41.240.188.1: bytes=32 time=105ms TTL=254
Reply from 41.240.188.1: bytes=32 time=112ms TTL=254
Reply from 41.240.188.1: bytes=32 time=71ms TTL=254
Reply from 41.240.188.1: bytes=32 time=87ms TTL=254
Reply from 41.240.188.1: bytes=32 time=94ms TTL=254
Reply from 41.240.188.1: bytes=32 time=80ms TTL=254

Ping statistics for 41.240.188.1:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 226ms, Average = 102ms

Tracing route to dsl-240-188-01.telkomadsl.co.za [41.240.188.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 189 ms 162 ms 158 ms dsl-240-188-01.telkomadsl.co.za [41.240.188.1]

Trace complete.
 
Cool, could you provide me the email address for this techie since it sounds like he knows his stuff.

blogbytes said:
Little update from my side.

Received this email from my Telkom techie.
Please check for any difference in latency, GDB 1 & 2 rerouted to a different STM-1 link, should be OK now.

Since Friday my latency seems stable. @ MR Jax - maybe you can ask them to also reroute you as well on ot a diff STM-1 link.
Click to expand...
 
Pinging 41.240.188.1 with 32 bytes of data:
Reply from 41.240.188.1: bytes=32 time=169ms TTL=254
Reply from 41.240.188.1: bytes=32 time=155ms TTL=254
Reply from 41.240.188.1: bytes=32 time=153ms TTL=254
Reply from 41.240.188.1: bytes=32 time=172ms TTL=254
Reply from 41.240.188.1: bytes=32 time=172ms TTL=254
Reply from 41.240.188.1: bytes=32 time=175ms TTL=254
Reply from 41.240.188.1: bytes=32 time=212ms TTL=254
Reply from 41.240.188.1: bytes=32 time=239ms TTL=254
Reply from 41.240.188.1: bytes=32 time=248ms TTL=254
Reply from 41.240.188.1: bytes=32 time=141ms TTL=254
Reply from 41.240.188.1: bytes=32 time=190ms TTL=254
Reply from 41.240.188.1: bytes=32 time=242ms TTL=254

Ping statistics for 41.240.188.1:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 141ms, Maximum = 248ms, Average = 189ms

Tracing route to dsl-240-188-01.telkomadsl.co.za [41.240.188.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 202 ms 185 ms 195 ms dsl-240-188-01.telkomadsl.co.za [41.240.188.1]

Trace complete.

http://www.speedtest.net/result/970462543.png
http://www.pingtest.net/result/24999126.png

pa-the-tic!
 
Last edited:
Ping test as of this moment:
Pinging 41.240.128.1 with 32 bytes of data:
Reply from 41.240.128.1: bytes=32 time=140ms TTL=244
Reply from 41.240.128.1: bytes=32 time=168ms TTL=244
Reply from 41.240.128.1: bytes=32 time=158ms TTL=244
Reply from 41.240.128.1: bytes=32 time=21ms TTL=244
Reply from 41.240.128.1: bytes=32 time=62ms TTL=244
Reply from 41.240.128.1: bytes=32 time=173ms TTL=244
Reply from 41.240.128.1: bytes=32 time=330ms TTL=244
Reply from 41.240.128.1: bytes=32 time=456ms TTL=244
Reply from 41.240.128.1: bytes=32 time=222ms TTL=244
Reply from 41.240.128.1: bytes=32 time=130ms TTL=244
Reply from 41.240.128.1: bytes=32 time=182ms TTL=244
Reply from 41.240.128.1: bytes=32 time=154ms TTL=244
Reply from 41.240.128.1: bytes=32 time=155ms TTL=244
Reply from 41.240.128.1: bytes=32 time=90ms TTL=244
Reply from 41.240.128.1: bytes=32 time=196ms TTL=244
Reply from 41.240.128.1: bytes=32 time=163ms TTL=244
Reply from 41.240.128.1: bytes=32 time=83ms TTL=244

Ping statistics for 41.240.128.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 456ms, Average = 169ms

a speed test:
http://www.speedtest.net/result/980317130.png

a ping test:
http://www.pingtest.net/result/25519639.png (LOL HSDPA is better than this!)
 
Last edited:
tracert as of this moment (running on an unshaped IS based account)
Tracing route to dsl-240-128-01.telkomadsl.co.za [41.240.128.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 264 ms 244 ms 221 ms 196-210-146-1.dynamic.isadsl.co.za [196.210.146.1]
3 105 ms 109 ms 87 ms 196.38.73.113
4 174 ms 130 ms 129 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 76 ms 64 ms 68 ms core6a-rba-gi0-0-0.ip.isnet.net [196.26.0.43]
6 170 ms 175 ms 204 ms 196.26.0.130
7 22 ms 22 ms 22 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.46.89]
8 88 ms 90 ms 84 ms 196.43.25.137
9 81 ms 80 ms 120 ms dsl-240-128-01.telkomadsl.co.za [41.240.128.1]

Trace complete.
 
Today has been particularly bad, started around 8.30AM and hasn't improved since.
A speed test: barely manage 1 Mbps (however, for most of the test it was less than 500Kbps....)
http://www.speedtest.net/result/983926502.png


And a ping test.....
http://www.pingtest.net/result/25711010.png

...and a traceroute
Tracing route to 196-210-146-1.dynamic.isadsl.co.za [196.210.146.1]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 200 ms 163 ms 168 ms 196.38.73.113
4 64 ms 62 ms 64 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 165 ms 191 ms 210 ms cdsl2-rba-vl153.ip.isnet.net [196.38.73.14]
6 238 ms 272 ms 241 ms cdsl2-rba-vl2562-ipc.ip.isnet.net [196.38.73.218]
7 107 ms 111 ms 100 ms 196-210-146-1.dynamic.isadsl.co.za [196.210.146.1]

Trace complete.


Tracing route to mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 255 ms 233 ms 261 ms 196.38.73.113
4 220 ms 208 ms 191 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 135 ms 109 ms 107 ms core6a-rba-gi0-0-0.ip.isnet.net [196.26.0.43]
6 152 ms 200 ms 202 ms 196.26.0.130
7 120 ms 129 ms 145 ms ge0-1.br1.jnb7.za.mtnbusiness.net [196.30.228.241]
8 212 ms 231 ms 213 ms ge0-1.cr1.jnb7.za.mtnbusiness.net [196.30.228.122]
9 223 ms 212 ms 209 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
10 220 ms 261 ms 277 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
11 51 ms 41 ms 26 ms 196.30.213.108
12 222 ms 239 ms 268 ms firewall1.jnb2.host-h.net [196.7.216.173]
13 58 ms 53 ms 59 ms mybroadband.co.za [41.203.21.137]

Trace complete.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X