South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
that akward moment when you get an abandoned because you cant reconnect to a CSGO MM game cause your ping is through the roof
last night pings just went belly up was forced to switch to a 1gb free account with another ISP in order to turn my frown upside down
Dear Telkom Internet User
In keeping with our continuous transformation towards improved services and customer experience, Telkom Internet will be conducting system maintenance. While it is possible that you may experience intermittent service interruption during the maintenance period, rest assured that your ISP will be taking every measure possible to prevent the same.
The maintenance period is Wednesday, 7th October 2015 from 22:00 to Thursday, 8th October 2015, 01:00.
Affected Services:
· Unix Webhosting
· Tracker Tool
· SMT Tool
Please feel free to contact our Technical Support call Centre on 10210 should you have any queries in this regard.
])ragon_\/oid;16226266 said:And there goes my TI account again. Pings are ok, but no normal web browsing data works at all.
Hi ranger, it seems my TITracker problem is linked to the activation of TIAllAccess on my 10MB uncapped account (thread here http://mybroadband.co.za/vb/showthread.php/764856-Always-on-internet).
Still getting the same error - View attachment 302408
... not a major hassle as userstats is working ok but you might want to investigate.
don't worry same boat here. Insanely high ping as of late. But no one seems to care :/ Gaming isn't a priority for Telkom, funny this is... I play Counter Strike as DGC which is hosted by TELKOM! lol
here is a new one did it like two seconds ago
not sure if tracert from JHB to CPT is same, nan0s0ldier where you based?
have to switch to free accounts to play CS and its getting rather annoying
Tracing route to cptts.gameservers.com [152.111.192.232]
over a maximum of 30 hops:
1 <1 ms 1 ms 1 ms 192.168.0.1
2 24 ms 27 ms 25 ms nngy-ip-bb-1.east.dsl.telkomsa.net [105.224.124.1]
3 27 ms 26 ms 28 ms 105.229.0.170
4 27 ms 27 ms 26 ms ipc-aggr-1.east.dsl.telkomsa.net [105.229.0.29]
5 27 ms 26 ms 27 ms dbn-pr-02-be200-vl1.net.telkosma.net [105.229.0.33]
6 519 ms 540 ms 556 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 561 ms 544 ms 823 ms ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
8 500 ms 581 ms 562 ms optinet.ct1.napafrica.net [196.10.140.15]
9 498 ms 438 ms 506 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
10 505 ms 574 ms 469 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 434 ms 419 ms 417 ms 196.28.178.66
12 459 ms 457 ms 471 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 394 ms 395 ms 403 ms 152.111.192.232
Trace complete.
Thu Oct 8 21:42:44 SAST 2015
traceroute to 152.111.192.232 (152.111.192.232), 30 hops max, 60 byte packets
1 dbn-pr-01-be301-vl3800.net.telkomsa.net (105.229.0.116) 0.829 ms 0.747 ms 0.820 ms
2 ipc-aggr-1.east.dsl.telkomsa.net (105.229.0.29) 1.224 ms 1.453 ms 1.506 ms
3 dbn-pr-02-be200-vl1.net.telkosma.net (105.229.0.33) 1.490 ms 1.678 ms 1.876 ms
4 ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) 23.056 ms 23.052 ms 22.682 ms
5 ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) 22.647 ms 22.630 ms 22.610 ms
6 optinet.ct1.napafrica.net (196.10.140.15) 23.566 ms 22.798 ms 23.758 ms
7 bu-ether1.cpt-p-1.optinet.net (197.84.7.33) 26.927 ms 26.861 ms te0-0-0-1.cpt-p-2.optinet.net (197.84.7.34) 28.917 ms
8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 24.729 ms vl12.cpt-hscore-2.optinet.net (197.84.5.254) 24.744 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238) 25.750 ms
9 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 27.667 ms 196.28.178.66 (196.28.178.66) 25.639 ms vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 26.801 ms
10 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.615 ms 196.41.144.34 (196.41.144.34) 26.591 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.597 ms
11 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.563 ms 152.111.192.232 (152.111.192.232) 27.523 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.495 ms
Code:Thu Oct 8 21:42:44 SAST 2015 traceroute to 152.111.192.232 (152.111.192.232), 30 hops max, 60 byte packets 1 dbn-pr-01-be301-vl3800.net.telkomsa.net (105.229.0.116) 0.829 ms 0.747 ms 0.820 ms 2 ipc-aggr-1.east.dsl.telkomsa.net (105.229.0.29) 1.224 ms 1.453 ms 1.506 ms 3 dbn-pr-02-be200-vl1.net.telkosma.net (105.229.0.33) 1.490 ms 1.678 ms 1.876 ms 4 ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) 23.056 ms 23.052 ms 22.682 ms 5 ct1-pr-01-te0-0-0.net.telkomsa.net (105.187.249.138) 22.647 ms 22.630 ms 22.610 ms 6 optinet.ct1.napafrica.net (196.10.140.15) 23.566 ms 22.798 ms 23.758 ms 7 bu-ether1.cpt-p-1.optinet.net (197.84.7.33) 26.927 ms 26.861 ms te0-0-0-1.cpt-p-2.optinet.net (197.84.7.34) 28.917 ms 8 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 24.729 ms vl12.cpt-hscore-2.optinet.net (197.84.5.254) 24.744 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238) 25.750 ms 9 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 27.667 ms 196.28.178.66 (196.28.178.66) 25.639 ms vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 26.801 ms 10 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.615 ms 196.41.144.34 (196.41.144.34) 26.591 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.597 ms 11 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.563 ms 152.111.192.232 (152.111.192.232) 27.523 ms gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 27.495 ms
My hop 2 is your hop 4, and from there on they follow the same path ...
so where do you think problem is coming from or what could it be?
im scratching my head here, afraid i might go bald soon
- Do you mean mean downloaded 200gb of data on an uncapped 2mb line during peak time being 7am - 12am period?
I noticed that previousy when I was on 2mb uncapped once I hit 100GB+ during peak time 7am - 12am I then got thrrottled?
I am now on a 4mb uncapped Telkom line and was wanting to know what their " soft cap " threshold is for peak time downloads?
any idea?
Tracing route to http://cpt.valve.net [152.111.192.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 31 ms 30 ms 30 ms http://ipc-1-up.east.dsl.telkomsa.net [105.229.0.21]
4 31 ms 30 ms 31 ms http://ipc-1-up.east.dsl.telkomsa.net [105.229.0.22]
5 31 ms 29 ms 29 ms http://ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]
[B] 6 124 ms 129 ms 132 ms http://ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 114 ms 112 ms 110 ms http://ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138][/B]
8 87 ms 84 ms 84 ms http://optinet.ct1.napafrica.net [196.10.140.15]
9 97 ms 96 ms 92 ms http://te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
10 129 ms 130 ms 132 ms http://vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 153 ms 148 ms 146 ms 196.28.178.66
12 115 ms 113 ms 112 ms http://gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 95 ms 93 ms 91 ms 152.111.192.244
Tracing route to http://cptts.gameservers.com [152.111.192.232]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 32 ms 30 ms 30 ms http://ipc-1-up.east.dsl.telkomsa.net [105.229.0.21]
4 31 ms 30 ms 30 ms http://ipc-1-up.east.dsl.telkomsa.net [105.229.0.22]
5 30 ms 30 ms 30 ms http://ipc-aggr-2.east.dsl.telkomsa.net [105.229.0.13]
[B] 6 117 ms 116 ms 118 ms http://ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138]
7 129 ms 134 ms 129 ms http://ct1-pr-01-te0-0-0.net.telkomsa.net [105.187.249.138][/B]
8 124 ms 120 ms 116 ms http://optinet.ct1.napafrica.net [196.10.140.15]
9 136 ms 127 ms 124 ms http://te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
10 132 ms 132 ms 143 ms http://vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 135 ms 132 ms 141 ms 196.28.178.66
12 114 ms 111 ms 110 ms http://gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 152 ms 152 ms 149 ms 152.111.192.232