South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Hi is there someone who can help me to move my line to another place, i`m trying to call telkom but the call centre is so busy, please
Will do.Looks as though TI might have created a retentions department possibly doing exit interviews, let us know how it goes.
Any other place I can retrieve my DSL Username and password? I use to have it on SMS but my phone has lost all data.
Tried to call call center, after about 2 hours still nobody answering. Sent multiple twitter messages with no response, complained on Facebook but no response.
Seriously can a simple task like this be so difficult to accomplish!!!!
Reason I don't have them in my modem? I used another ISP (vox) while telkom had all this connection problems.
Well, the problem on this traceroute is that hops 5,6,7,8 and 9 are all on IPNet. If we had a problem, it would have shown up on hop 3 or hop 5.
So, either there is a problem between nbsc-ip-bssr-2 and nbsc-ip-rcache-1, or there happened to be a latency spike when traceroute was sending packets with a ttl of 9, that coincided.
And this is why mtr or winmtr is better, as it traces the path, and then pings all the hops on the path and provides stats on each hop.
And yes, it is possible for your DSLAM to be horribly congested for 1 minute, and then be fine after that.
We are seeing high utilisation (still within limits, but getting quite close) on one IPC link, in Cape Town, and you didn't go through it.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.2 - 0 | 51 | 51 | 0 | 0 | 0 | 0 |
| ti-224-188-01.telkomadsl.co.za - 67 | 12 | 4 | 8 | 8 | 9 | 8 |
| ti-228-0-06.telkomadsl.co.za - 67 | 12 | 4 | 10 | 10 | 12 | 11 |
| ti-228-0-13.telkomadsl.co.za - 67 | 12 | 4 | 10 | 12 | 17 | 10 |
| rndf-ip-hsll-1-wan.telkom-ipnet.co.za - 75 | 12 | 3 | 13 | 14 | 16 | 13 |
| 196.43.39.166 - 75 | 12 | 3 | 15 | 15 | 16 | 16 |
|rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za - 75 | 12 | 3 | 15 | 15 | 17 | 15 |
|nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za - 75 | 12 | 3 | 15 | 17 | 20 | 15 |
|nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za - 67 | 12 | 4 | 14 | 17 | 21 | 15 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.2 - 0 | 51 | 51 | 0 | 0 | 1 | 0 |
| ti-224-188-01.telkomadsl.co.za - 75 | 12 | 3 | 7 | 8 | 9 | 8 |
| ti-228-0-06.telkomadsl.co.za - 70 | 13 | 4 | 10 | 10 | 12 | 10 |
| ti-228-0-13.telkomadsl.co.za - 75 | 12 | 3 | 11 | 11 | 12 | 11 |
| rndf-ip-hsll-1-wan.telkom-ipnet.co.za - 70 | 13 | 4 | 10 | 11 | 13 | 10 |
|lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za - 75 | 12 | 3 | 181 | 190 | 196 | 181 |
| linx.redstation.net.uk - 75 | 12 | 3 | 183 | 191 | 197 | 183 |
| h185-5-3-242.host.redstation.co.uk - 75 | 12 | 3 | 185 | 194 | 202 | 185 |
|186-16-200-109.rackcentre.redstation.net.uk - 75 | 12 | 3 | 187 | 196 | 203 | 187 |
| h31-3-246-194.host.redstation.co.uk - 75 | 12 | 3 | 189 | 197 | 204 | 189 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Know how you feel, I had the same experience with axxess during the 2012 MNET meltdown. Because of business commitments I was forced to kick their uncapped accounts into touch within 2 weeks (kept the capped a/cs though).Must say I'm actually feeling sad that it came to this. Have been with Telkom forever and was happy with the service.
Know how you feel, I had the same experience with axxess during the 2012 MNET meltdown. Because of business commitments I was forced to kick their uncapped accounts into touch within 2 weeks (kept the capped a/cs though).
They're still a great company to deal with and I believe their uncapped problems are behind them now![]()
Well, the problem on this traceroute is that hops 5,6,7,8 and 9 are all on IPNet. If we had a problem, it would have shown up on hop 3 or hop 5.
So, either there is a problem between nbsc-ip-bssr-2 and nbsc-ip-rcache-1, or there happened to be a latency spike when traceroute was sending packets with a ttl of 9, that coincided.
And this is why mtr or winmtr is better, as it traces the path, and then pings all the hops on the path and provides stats on each hop.
And yes, it is possible for your DSLAM to be horribly congested for 1 minute, and then be fine after that.
We are seeing high utilisation (still within limits, but getting quite close) on one IPC link, in Cape Town, and you didn't go through it.
Will do.
Must say I'm actually feeling sad that it came to this. Have been with Telkom forever and was happy with the service.
Funny enough the one other problem I had was also this time last year, just before I moved to uncapped and that took ICASA intervention to fix.
My 1st post on my broadband. Post virgin I am ;-)
Welcome, if last Febuary/March are anything to go by this too will passMy 1st post on my broadband. Post virgin I am ;-)
... And this may seem crazy, but it is a hassle to cancel TI, so for the moment I keep my TI account going in the belief that perhaps things will improve someday... I will keep tracking the forum from time to time to see if that is the case.
Welcome, if last Febuary/March are anything to go by this too will pass
... although I won't be surprised to see a new type of TI uncapped account specifically for Netflix & VOD released before the end of March.