Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
ponder said:
I use Transmission bittorrent client and it's set to use TCP Port 51413 which I've configured under my routers virtual server settings to be allowed.
Not familiar with netgear, have one lying here but the pos overheats within 10mins of powering on and dies.
Click to expand...

I figured out how to enable port forward on my router will give it a bash when I get home to see if does make any difference to my D/L Speeds.
 
If you intend on playing multiplayer games like League of Legends on international servers, you had better be able to predict the future by at least a second and your actions per minute less than 30! Otherwise, it might be an UNPLEASANT EXPERIENCE.

PLEASE.FIX.THE.LAG

It has been 2 weeks. Many people have complained.
 
After a response from the Telkom rep here via PM, in which he told me that the next step was to send an email to support:

eB1a3NR.png


Wow.

Literally sub-200ms most of the time!

No idea what they did (if anything, as this was about an hour after said response), but what wonderful performance!

Going to check it now!
 
Is Telkom down or just me?

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

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 12 ms 12 ms 11 ms dsl-165-145-76-01.telkomadsl.co.za [165.145.76.1
]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

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

1 2 ms <1 ms 1 ms login.router [10.0.0.2]
2 156 ms 157 ms * ti-224-144-01.telkomadsl.co.za [105.224.144.1]
3 305 ms * 68 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 18 ms 16 ms 18 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 * 23 ms 47 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 171 ms * 208 ms 196.43.39.162
7 63 ms 56 ms 68 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 100 ms 111 ms 111 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 116 ms 120 ms 118 ms telkom.co.za [196.43.22.222]

Trace complete.
 
Hmm. That first hop may indicate some form of exchange congestion on my line. :(
 
Looks like an error on the modem, it had reset itself. :(


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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 11 ms 11 ms 11 ms ti-224-156-01.telkomadsl.co.za [105.224.156.1]
3 18 ms 17 ms 17 ms ti-228-0-06.telkomadsl.co.za [105.228.0.6]
4 18 ms 17 ms 18 ms ti-228-0-13.telkomadsl.co.za [105.228.0.13]
5 18 ms 18 ms 18 ms 165.165.216.217
6 17 ms 18 ms 18 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.
43.11.134]
7 18 ms 18 ms 17 ms 196.43.25.138
8 19 ms 19 ms 18 ms internet-solutions-gw.telkom-ipnet.co.za [196.25
.127.182]
9 18 ms 18 ms 18 ms ar2-rba-gi0-1.ip.isnet.net [168.209.1.172]
10 19 ms 19 ms 19 ms mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net [168.209.8
6.250]
11 * * * Request timed out.
12 43 ms 43 ms 44 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
13 63 ms 120 ms 46 ms 41-66-132-242-f2.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.242]
14 63 ms 117 ms 58 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
15 45 ms 45 ms 45 ms row-access-switch1-row7-8.jnb1.host-h.net [197.1
89.193.39]
16 43 ms 43 ms 43 ms 41.203.24.42
17 43 ms 42 ms 42 ms 197.242.89.170

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

1 2 ms <1 ms 1 ms login.router [10.0.0.2]
2 156 ms 157 ms * ti-224-144-01.telkomadsl.co.za [105.224.144.1]
3 305 ms * 68 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 18 ms 16 ms 18 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 * 23 ms 47 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 171 ms * 208 ms 196.43.39.162
7 63 ms 56 ms 68 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 100 ms 111 ms 111 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 116 ms 120 ms 118 ms telkom.co.za [196.43.22.222]

Trace complete.
Click to expand...

You have congestion on the exchange, unless there is more users on the line!
 
elriconess said:
You have congestion on the exchange, unless there is more users on the line!
Click to expand...

Just me on this line.

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

1 1 ms <1 ms <1 ms login.router [10.0.0.2]
2 9 ms 9 ms 9 ms ti-224-144-01.telkomadsl.co.za [105.224.144.1]
3 11 ms 10 ms 10 ms ti-226-0-06.telkomadsl.co.za [105.226.0.6]
4 10 ms 10 ms 11 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 11 ms 10 ms 11 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 33 ms 32 ms 32 ms 196.43.39.162
7 35 ms 47 ms 34 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 38 ms 37 ms 37 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
9 37 ms 37 ms 37 ms telkom.co.za [196.43.22.222]

Trace complete.

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=44ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Request timed out.
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=62ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Request timed out.
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=38ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Request timed out.
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
Reply from 196.43.22.222: bytes=32 time=37ms TTL=245
 
Took me around 5 minutes to get onto this thread. Seems Telkom is taking the weekend off, again.

Honestly so sick of this intermittent service that I can puke. Not sure what the hell has been going on but these past three months has been bad. ADSL will run like the clappers for 3 or 4 days a week and come 17H00 in the afternoon or weekend and it is all the way back to the Beltel days, see images below.

I just mailed through my cancellation for my telephone and ADSL line. I know its going to cost me around double or three times on mobile but I've had it with this company. Made a commitment to myself that I will never again support Telkom in any way or form, no matter whether they turn into world leaders [talk about wishful thinking] or not. I'm done.

mybb.png news24.png
 
Ye something just happend. NNTP went from 300 kb/s to ZERO. dead. 0 kb/s.
Websites and streaming netflix seems to work though. :confused:
 
Telkom performing very poorly tonight. Only got myself sorted out yesterday. Browsing and YT are shapshap, but downloading? Nottachance.:mad:

This is a 4mbps line with uncapped service, for interest's sake.

DLSpeed.jpg
SAIX Spdtst 4.jpg
SAIX Tracert 2.jpg
 
Whilst torrents have taken a bit of knock during the evenings in the last two months overall performance is still great.

TelkomZA has managed to up my line to 8Mbps from 6Mbps and it's still rock solid (thanks Charl) so I'm probably going to be moving to TI 10Mb Uncapped in December when the new pricing kicks in.
 
Has anyone else been experienced bad http eg. browsing.

My downloading speed is fine, and even YouTube is fine, but loading webpages is terrible
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X