Telkom Internet Capped/Uncapped User Feedback (Pt2)

streaker said:
Big Bean,

I have requested our upstream provider to make changes. My responses looking a lot better now. Please monitor and verify if your responses improved
Click to expand...

Appears to be fixed my end.

I just want to raise another issue that has been present since last year that I have not been able to resolve myself (Mweb support is useless). Ping from TI Cape Town -> Mweb Cape Town seems to route via JHB or dodgy router causing slightly higher than expected ping:
Is it possible to log an issue with Mweb to get this fixed?

TI:
Tracing route to cpt.valve.net [152.111.192.244]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 9 ms 8 ms 9 ms wblv-ip-esr-3.south.dsl.telkomsa.net [105.224.80
.1]
3 10 ms 10 ms 10 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 10 ms 9 ms 10 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

5 9 ms 10 ms 9 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.
54]
6 11 ms 10 ms 10 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.
138]
7 11 ms 10 ms 10 ms mweb.ct1.napafrica.net [196.10.140.15]
8 33 ms 34 ms 34 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
9 32 ms 31 ms 31 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
10 32 ms 31 ms 31 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
11 61 ms 32 ms 29 ms 196.41.144.34
12 34 ms 33 ms 32 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

13 33 ms 33 ms 33 ms 152.111.192.244

Trace complete.
Click to expand...

A backup account:
Tracing route to cpt.valve.net [152.111.192.244]
over a maximum of 30 hops:

1 8 ms 9 ms 7 ms 105-236-4-193-esr-lo.mtnbusiness.co.za [105.236.
4.193]
2 13 ms 14 ms 13 ms 41.181.222.101
3 13 ms 13 ms 13 ms 41.181.222.102
4 12 ms 12 ms 11 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 14 ms 14 ms 13 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 13 ms 12 ms 14 ms db-nt-1.jev.co.za [196.44.31.5]
7 14 ms 12 ms 13 ms 196.44.31.106
8 51 ms 34 ms 15 ms ct-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.10
8]
9 13 ms 13 ms 12 ms 196.44.0.74
10 14 ms 14 ms 13 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.14
1]
11 18 ms 19 ms 15 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
12 14 ms 15 ms 14 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
13 23 ms 14 ms 15 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
14 16 ms 15 ms 15 ms 196.41.144.34
15 16 ms 14 ms 14 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

16 13 ms 14 ms 15 ms 152.111.192.244

Trace complete.
Click to expand...
 
Big Bean said:
Appears to be fixed my end.

I just want to raise another issue that has been present since last year that I have not been able to resolve myself (Mweb support is useless). Ping from TI Cape Town -> Mweb Cape Town seems to route via JHB or dodgy router causing slightly higher than expected ping:
Is it possible to log an issue with Mweb to get this fixed?

TI:


A backup account:
Click to expand...

I have asked MWeb before to identify their Southern routes. This would eliminate issues like yours. Made a change now, please check again.
 
streaker said:
I have asked MWeb before to identify their Southern routes. This would eliminate issues like yours. Made a change now, please check again.
Click to expand...

No change as of yet:
Tracing route to cpt.valve.net [152.111.192.244]
over a maximum of 30 hops:

1 7 ms 9 ms 8 ms wblv-ip-esr-3.south.dsl.telkomsa.net [105.224.80
.1]
2 10 ms 10 ms 10 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
3 9 ms 9 ms 10 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]

4 9 ms 9 ms 9 ms blv-pr-02-be200-vl1.net.telkomsa.net [105.226.0.
54]
5 9 ms 9 ms 9 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.
138]
6 10 ms 10 ms 9 ms mweb.ct1.napafrica.net [196.10.140.15]
7 35 ms 34 ms 35 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 32 ms 31 ms 32 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 32 ms 35 ms 30 ms 196.28.178.66
10 34 ms 31 ms 30 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

11 30 ms 30 ms 29 ms 152.111.192.244

Trace complete.
Click to expand...
 
So what do you do if a specific application in this case a game, Diablo 3, suddenly starts experiencing MASSIVE connection issues. The connection has been perfectly adequate since i started using ti uncapped this month, but since last night it has been unplayable. 700ms+ game nearly freezes up, struggles to login even , the connection is so ****ed up.

Funny thing is everything else is running smoothly. Counterstrike (local) pings well, streaming, downloading, torrenting there is literally nothing else wrong just Diablo 3 suddenly went down the tubes. Speedtests locally, internationally are also fine. With <200ms ping internationally and practically instant ping locally.

Is it perhaps a routing issue? Should I try and test late past 00:00 to rule out congestion or shaping?
 
LBXAC20 said:
So what do you do if a specific application in this case a game, Diablo 3, suddenly starts experiencing MASSIVE connection issues. The connection has been perfectly adequate since i started using ti uncapped this month, but since last night it has been unplayable. 700ms+ game nearly freezes up, struggles to login even , the connection is so ****ed up.

Funny thing is everything else is running smoothly. Counterstrike (local) pings well, streaming, downloading, torrenting there is literally nothing else wrong just Diablo 3 suddenly went down the tubes. Speedtests locally, internationally are also fine. With <200ms ping internationally and practically instant ping locally.

Is it perhaps a routing issue? Should I try and test late past 00:00 to rule out congestion or shaping?
Click to expand...

Same thing is happening with blizzards other game, Heroes of the Storm. 500ms with characters jumping and the game freezing only catch up a few seconds later...

None of my other games have this issue even the ones using European servers like LOL and Trove. Telkom, please fix this.
 
supervegeta41 said:
Same thing is happening with blizzards other game, Heroes of the Storm. 500ms with characters jumping and the game freezing only catch up a few seconds later...

None of my other games have this issue even the ones using European servers like LOL and Trove. Telkom, please fix this.
Click to expand...

So it's not just me... this issue needs to gain some traction if all Blizz games are unplayable on Telkom that is a serious problem. We all need a little Blizz in our life !

Here is some blizzard server/port info:
https://eu.battle.net/support/en/article/running-a-pathping-test
https://us.battle.net/support/en/article/configuring-router-and-firewall-ports (doubt if this is relevant but hey)
 
Have WoW issues since last night

path ping below, don't know if telkom or blizzard

ingame is around 500ms constant, but spikes every few minutes into 1k+

Tracing route to 185.60.114.159 over a maximum of 30 hops

0 Me-PC [192.168.1.2]
1 router.asus.com [192.168.1.1]
2 rrba-ip-bng-1.north.dsl.telkomsa.net [105.224.208.1]
3 ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
4 ipc-aggr-1.north.telkomsa.net [105.224.0.13]
5 196.25.166.217
6 ams-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.82]
7 80.249.208.73
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Me-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% rrba-ip-bng-1.north.dsl.telkomsa.net [105.224.208.1]
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ipc-1-up.north.dsl.telkomsa.net [105.224.0.6]
0/ 100 = 0% |
4 9ms 0/ 100 = 0% 0/ 100 = 0% ipc-aggr-1.north.telkomsa.net [105.224.0.13]
0/ 100 = 0% |
5 10ms 0/ 100 = 0% 0/ 100 = 0% 196.25.166.217
6/ 100 = 6% |
6 296ms 8/ 100 = 8% 2/ 100 = 2% ams-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.82]
0/ 100 = 0% |
7 300ms 6/ 100 = 6% 0/ 100 = 0% 80.249.208.73

Trace complete.
 
Last edited:
Not sure if this is the right place but I've been having on and off latency issues for months now, and it's currently the worst it's ever been, because I'm also getting terrible speeds. I've just done a speed test and a trace route:

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

1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]
2 560 ms 581 ms 635 ms wtvw-ip-bb-1.south.dsl.telkomsa.net [105.224.136.1]
3 604 ms 522 ms 467 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 594 ms 618 ms 635 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 583 ms 570 ms 580 ms blv-pr-01-be200-vl1.net.telkomsa.net [105.226.0.53]
6 * * * Request timed out.
7 665 ms 661 ms 553 ms jb1-pr-01-te1-0.net.telkomsa.net [105.187.249.6]
8 583 ms 664 ms 774 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]
9 777 ms 781 ms 697 ms 72.14.239.129
10 558 ms 659 ms 733 ms jnb01s08-in-f35.1e100.net [216.58.223.35]

Trace complete.
Click to expand...

I've logged faults, and been DMing the @TelkomZA Twitter account since as far back as April but nothing's come of it yet. Playing games online has been all but impossible with my ping jumping between 700ms and 4000ms to international games like Guild Wars 2 and League of Legends. Is there anything that can be done about this?
 
sH3LLsH0K said:
Not sure if this is the right place but I've been having on and off latency issues for months now, and it's currently the worst it's ever been, because I'm also getting terrible speeds. I've just done a speed test and a trace route:



I've logged faults, and been DMing the @TelkomZA Twitter account since as far back as April but nothing's come of it yet. Playing games online has been all but impossible with my ping jumping between 700ms and 4000ms to international games like Guild Wars 2 and League of Legends. Is there anything that can be done about this?
Click to expand...

Hop 2 is the BRSS/ESR, the first IP hop after your modem, with the copper and the dslam in between, and before it gets to the ISP. So, if you aren't seeing errors on the DSL interface on the modem and your sync is stable, this is dslam congestion, nothing that an ISP can do (except log a fault, which you can do online, be very clear that it is dslam congestion and not a line fault, a technician can not do anything about this. ).
 
My ADSL was quite erratic tonight. I checked the modem and the SNR etc. looks fine. Hell, the model states that my highest possible speed is 22Mb, but running a 4Mb line. Did a trace route and got this:


traceroute to slashdot.org (216.34.181.45), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 2.282 ms 0.926 ms 0.763 ms
2 * * *
3 ipc-up-2.north.telkomsa.net (105.228.0.5) 17.891 ms 23.076 ms 14.328 ms
4 * ipc-up-2.north.telkomsa.net (105.228.0.6) 16.168 ms 13.846 ms
5 ipc-aggr-2.north.telkomsa.net (105.228.0.13) 14.794 ms 15.797 ms 14.176 ms
6 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 14.088 ms 13.861 ms 14.183 ms
7 165.165.216.221 (165.165.216.221) 14.362 ms 15.550 ms 16.013 ms
8 fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.110) 202.277 ms 202.639 ms 202.769 ms
9 te0-7-0-11.rcr21.fra06.atlas.cogentco.com (149.11.20.65) 201.185 ms * 202.942 ms
10 be2305.ccr42.fra03.atlas.cogentco.com (154.54.74.77) 203.809 ms 203.424 ms 203.734 ms
11 be2534.agr22.fra03.atlas.cogentco.com (130.117.48.209) 274.744 ms 206.308 ms 270.039 ms
12 te0-0-0-0.nr11.b015923-1.fra03.atlas.cogentco.com (154.25.5.141) 204.322 ms 272.985 ms 205.678 ms
13 savvis.fra09.atlas.cogentco.com (130.117.15.254) 218.375 ms 217.960 ms 219.031 ms
14 cr1-te-0-1-1-0.ft3.savvis.net (206.28.100.81) 220.084 ms 226.347 ms 226.027 ms
15 206.28.96.218 (206.28.96.218) 326.709 ms 316.485 ms 307.923 ms
16 hr3-xe-8-0-0.elkgrovech3.savvis.net (204.70.198.73) 312.717 ms 385.823 ms 314.469 ms
17 64.37.207.146 (64.37.207.146) 332.900 ms 314.040 ms 402.345 ms
18 64.27.160.194 (64.27.160.194) 316.388 ms 339.397 ms 409.471 ms
19 slashdot.org (216.34.181.45) 409.599 ms 409.443 ms 407.648 ms

Look at hop 2. Really weird that the 2nd hop should time out.
 
Having issues since Sunday, League of Legends doesnt work at all on Telkom (EU West) previously had ping between 190 - 200 now its fixed at 305 but definately doesnt play like 305. Game freezes and has ton of spikes.

Tried other capped accounts Afrihost (works perfect) Webafrica ( works perfect) and Axxess (works perfect)

Here is tracert on Telkom

1 <1 ms <1 ms <1 ms RT-AC68U-37A0 [192.168.2.1]
2 * * * Request timed out.
3 14 ms 13 ms 13 ms ipc-up-2.north.telkomsa.net [105.228.0.5]
4 14 ms 13 ms 14 ms ipc-up-2.north.telkomsa.net [105.228.0.6]
5 14 ms 29 ms 14 ms ipc-aggr-2.north.telkomsa.net [105.228.0.13]
6 14 ms 14 ms 14 ms cen-pr-01-be200-vl1.net.telkomsa.net [105.228.0.18]
7 15 ms 15 ms 14 ms 196.25.166.217
8 298 ms 297 ms 327 ms ams-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.43.9.82]
9 * * * Request timed out.
10 201 ms 199 ms 200 ms 186-16-200-109.rackcentre.redstation.net.uk [109.200.16.186]
11 200 ms 200 ms 199 ms h31-3-246-202.host.redstation.co.uk [31.3.246.202]
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X