Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
@ Ranger Streaming even 360p buffers on 4mb uncapped synced @ 6mb. Was fine all weekend. I cant only think its the change you guys implemented today :(

According to subxero's post, it was before my change ...

Is it still bust now?
 
Well the change didn't improve my latency in LOL one bit,still won't go below 600ms.Has it improved for anyone else?
 
Yes... can confirm that all is fine again.

Edit: More or less in that speeds are fluctuating from low to high. My connections bar graph looks like an ECG printout
 
Last edited:
I think your change has broken it for everyone. I am getting pings of 400ms to telkom.co.za here in joburg.

Reply from 196.43.22.222: bytes=32 time=421ms TTL=246
Reply from 196.43.22.222: bytes=32 time=436ms TTL=246
Reply from 196.43.22.222: bytes=32 time=422ms TTL=246
Reply from 196.43.22.222: bytes=32 time=413ms TTL=246
Reply from 196.43.22.222: bytes=32 time=408ms TTL=246
Reply from 196.43.22.222: bytes=32 time=426ms TTL=246
Reply from 196.43.22.222: bytes=32 time=436ms TTL=246
Reply from 196.43.22.222: bytes=32 time=399ms TTL=246
Reply from 196.43.22.222: bytes=32 time=393ms TTL=246
Reply from 196.43.22.222: bytes=32 time=398ms TTL=246
Reply from 196.43.22.222: bytes=32 time=424ms TTL=246
Reply from 196.43.22.222: bytes=32 time=424ms TTL=246
Reply from 196.43.22.222: bytes=32 time=371ms TTL=246
Reply from 196.43.22.222: bytes=32 time=372ms TTL=246
Reply from 196.43.22.222: bytes=32 time=395ms TTL=246
Reply from 196.43.22.222: bytes=32 time=430ms TTL=246
Reply from 196.43.22.222: bytes=32 time=439ms TTL=246

That is an issue your side:
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=36ms TTL=246
Reply from 196.43.22.222: bytes=32 time=41ms TTL=246
Reply from 196.43.22.222: bytes=32 time=35ms TTL=246
Reply from 196.43.22.222: bytes=32 time=65ms TTL=246
 
@Ranger

Tracing route to FRAG1N3SVR103 [95.172.65.123]
over a maximum of 30 hops:

1 * <1 ms <1 ms 10.0.0.2
2 11 ms 10 ms 11 ms 224-72-1.dsl.subscriber.telkomsa.net [105.224.72
.1]
3 108 ms 106 ms 105 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6
]
4 101 ms 101 ms 101 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.
13]
5 16 ms 15 ms 15 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 200 ms 201 ms 199 ms fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.110]
7 221 ms 198 ms 198 ms ffm-b10-link.telia.net [195.12.255.217]
8 201 ms 204 ms 202 ms ffm-bb1-link.telia.net [213.155.134.134]
9 240 ms 219 ms 203 ms ffm-b11-link.telia.net [213.155.134.85]
10 222 ms 219 ms 211 ms internap-ic-138405-ffm-b11.c.telia.net [213.248.
98.22]
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 ^C
C:\Users\SPIRITS>

This is the server I was on a few minutes ago.
 
Last edited:
My experience today was below average. A friend from out of town came to visit today and asked for a a couple of torrent related downloads. Downloads were hovering between 80 and 200kbps. During this time browsing were terrible.

Facebook group pages would take about 30 seconds to load completely and other pages not must faster.

A but earlier had a look at a couple of Youtube repair videos and had no problems with the streaming quality.

I eventualy gave up on the torrents as it took 2:30 minutes to download about 87% of a 310MB file. I changed to my backup Afrihost account and immediately hit 420kB/s.

I'm in Kirkwood in the Eastern Cape on a 4Mbps line and would describe my current experience as far below par ito what I used to experience on TI.
 
@Ranger

Tracing route to FRAG1N3SVR103 [95.172.65.123]
over a maximum of 30 hops:

1 * <1 ms <1 ms 10.0.0.2
2 11 ms 10 ms 11 ms 224-72-1.dsl.subscriber.telkomsa.net [105.224.72
.1]
3 108 ms 106 ms 105 ms 224-0-6.dsl.subscriber.telkomsa.net [105.224.0.6
]
4 101 ms 101 ms 101 ms 224-0-13.dsl.subscriber.telkomsa.net [105.224.0.
13]
5 16 ms 15 ms 15 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
6 200 ms 201 ms 199 ms fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.110]
7 221 ms 198 ms 198 ms ffm-b10-link.telia.net [195.12.255.217]
8 201 ms 204 ms 202 ms ffm-bb1-link.telia.net [213.155.134.134]
9 240 ms 219 ms 203 ms ffm-b11-link.telia.net [213.155.134.85]
10 222 ms 219 ms 211 ms internap-ic-138405-ffm-b11.c.telia.net [213.248.
98.22]
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 ^C
C:\Users\SPIRITS>

This is the server I was on a few minutes ago.


How did you get the ip? I tried with tcp view and it doesn't show.....
 
Go to the logs folder in your league of legends game folder then network logs and pick one of the logs.

Ok cool found it..... The thing is the trace rt looks fine but ingame its like 1800ms latency...

My last server connected to was 31.186.224.237
 
Ok cool found it..... The thing is the trace rt looks fine but ingame its like 1800ms latency...

My last server connected to was 31.186.224.237

Yes I know it does look fine and I also use a program called LOLTool to show my latency without going ingame and it shows 206ms,yet ingame I get 600-1500ms.Weird..
 
Dead in the water here (Durban). Been up and down all day today, but as of 7pm or so, everything has just fallen to s#!t. I honestly wish Telkom could just unf#cK whatever they keep messing with. Called the call centre, and was on hold for almost an hour before I gave up and hung up.
 
Browsing is pathetic tonight. No abnormally high pings what so ever, only slow web browsing. Didn't even try downloads yet.
 
Dead in the water here (Durban). Been up and down all day today, but as of 7pm or so, everything has just fallen to s#!t. I honestly wish Telkom could just unf#cK whatever they keep messing with. Called the call centre, and was on hold for almost an hour before I gave up and hung up.

+1 utter crap at the moment.
 
Yes I know it does look fine and I also use a program called LOLTool to show my latency without going ingame and it shows 206ms,yet ingame I get 600-1500ms.Weird..

That is telling.

I have done a few more tweaks to prevent gaming impacting icmp and dns too much. There may be some impact to P2P, which I will try and reduce.

I think we will have to test LOL at the office tomorrow and do packet captures, debugging etc. to see what is happening with the latency shown in this game, whether it is accurate, if so why it is so high etc.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X