PostmanPot
Honorary Master
No issues here, TI Capped. First trace route had a similar result to yours (180ms), fine now.
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: How impressed have you been with the 2026 Amazon Prime Day deals?
Telkom Internet Capped/Uncapped User Feedback (Pt2)
- Thread starter bwana
- Start date
No issues here, TI Capped. First trace route had a similar result to yours (180ms), fine now.
MickeyD
RIP
PS. don't do trace routes to mybroadband!
])ragon_\/oid
Expert Member
- Joined
- Jun 10, 2011
- Messages
- 3,959
- Reaction score
- 0
Cloud flare has local servers, so shouldn't be a problem.
defcomk
Senior Member
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\GeorgeKiarie>tracert www.google.com
Tracing route to www.google.com [105.187.241.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 2232 ms 2280 ms 2312 ms esdw-ip-esr-3.south.dsl.telkomsa.net [105.224.4.1]
3 2228 ms 2242 ms 2236 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 2197 ms 2224 ms 2221 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 2252 ms 2277 ms 2301 ms cache.google.com [105.187.241.49]
Trace complete.
C:\Users\GeorgeKiarie>tracert www.google.com
Tracing route to www.google.com [105.187.241.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 2236 ms 2215 ms 2190 ms esdw-ip-esr-3.south.dsl.telkomsa.net [105.224.4.1]
3 2236 ms 2220 ms 2206 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 2239 ms 2238 ms 2220 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 2252 ms 2249 ms 2271 ms cache.google.com [105.187.241.49]
Trace complete.
C:\Users\GeorgeKiarie>tracert telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 2191 ms 2170 ms 2163 ms esdw-ip-esr-3.south.dsl.telkomsa.net [105.224.4.1]
3 2183 ms 2186 ms 2203 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
4 2206 ms 2223 ms 2213 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 2188 ms 2225 ms 2227 ms 165.165.214.213
6 2217 ms 2216 ms 2247 ms 196.43.39.166
7 2272 ms 2235 ms 2234 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 2203 ms 2213 ms 2208 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.34]
9 2240 ms 2259 ms 2261 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
C:\Users\GeorgeKiarie>
since 9pm yesterdayMickZA
Executive Member
TI mail servers are on a "go slow" again TI to TI included, up to an hour delay.
elf_lord_ZC5
Honorary Master
Don't use TI form email - Google just works better ...
Badprop_za
Expert Member
Is anyone else experiencing crappy speeds? For the last 2 days my 4meg line have been looking more like a 1meg line......
elf_lord_ZC5
Honorary Master
Have not been online so far this week - work. But my Son is complaining of bad lag spikes ... , in game playing Dota2 or LoL.
Last edited:
Spamhater
Senior Member
- Joined
- Aug 6, 2006
- Messages
- 617
- Reaction score
- 5
Having high ping`s in Cape Town something is wrong
C:\Users\>ping telkom.co.za
Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=214ms TTL=245
Reply from 196.43.22.222: bytes=32 time=215ms TTL=245
Reply from 196.43.22.222: bytes=32 time=217ms TTL=245
Reply from 196.43.22.222: bytes=32 time=202ms TTL=245
Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 202ms, Maximum = 217ms, Average = 212ms
C:\Users\>tracert www.telkom.co.za
Tracing route to www.telkom.co.za [165.143.158.60]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 7 ms 8 ms 7 ms wtvw-ip-bng-1.south.dsl.telkomsa.net [105.224.24
8.1]
3 160 ms 161 ms 153 ms ipc-1-up.south.dsl.telkomsa.net [105.226.0.6]
4 218 ms 215 ms 206 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 141 ms 136 ms 141 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.
153]
6 228 ms 221 ms 214 ms 196.43.51.74
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.
C:\Users\>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.246.95]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home.gateway [192.168.1.254]
2 8 ms 7 ms 8 ms wtvw-ip-bng-1.south.dsl.telkomsa.net [105.224.24
8.1]
3 136 ms 140 ms 140 ms ipc-3-up.south.dsl.telkomsa.net [105.226.0.246]
4 225 ms 215 ms 212 ms ipc-aggr-1.south.dsl.telkomsa.net [105.226.0.13]
5 108 ms 104 ms 102 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 284 ms 287 ms 278 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 357 ms 357 ms 370 ms ldn-b5-link.telia.net [62.115.35.89]
8 398 ms 413 ms 429 ms atos-ic-151907-ldn-b5.c.telia.net [80.239.132.14
2]
9 * * * Request timed out.
10 * * * Request timed out.
11 402 ms 410 ms 421 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 347 ms 305 ms 307 ms 132.185.255.165
13 407 ms 404 ms 374 ms bbc-vip016.cwwtf.bbc.co.uk [212.58.246.95]
Trace complete.
Here is mine at the moment:
Code:
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. home.gateway 0.0% 73 0.3 0.4 0.3 0.4 0.0
2. wblv-ip-esr-3.south.dsl.telkomsa 0.0% 73 8.6 8.9 7.4 10.2 0.4
3. ipc-3-up.south.dsl.telkomsa.net 0.0% 73 24.6 34.0 11.2 57.8 10.1
4. ipc-aggr-1.south.dsl.telkomsa.ne 0.0% 73 19.7 11.3 9.2 40.0 3.8
5. 196.25.103.93 0.0% 73 15.9 10.9 8.3 80.4 8.3
6. 196.43.39.166 0.0% 72 153.8 168.2 118.1 212.3 22.8
7. 196.43.23.6 0.0% 72 159.1 169.5 122.0 213.8 22.0
8. nbsc-ip-bssr-2-atm-5-0-0-1.telko 0.0% 72 161.3 150.7 107.6 187.5 16.3
9. nbsc-ip-rcache-1-vif0.telkom-ipn 0.0% 72 163.0 171.4 133.9 215.0 20.1Spamhater
Senior Member
- Joined
- Aug 6, 2006
- Messages
- 617
- Reaction score
- 5
Called telkom and they done a port reset and problem was resolved
elf_lord_ZC5
Honorary Master
Damn and all Tarnation - I am DC'ing like it is going out of fashion ... in GW2 ...
Telkom Internet Uncapped User Feedback (Pt2)
Aaargghh. ADSL line is syncing, but it seems that it isn't authenticating my ISP account. Router status is stuck at connecting. Anyone else experiencing the same problem
Edit. Got through to the call centre. Area wide outage.
Aaargghh. ADSL line is syncing, but it seems that it isn't authenticating my ISP account. Router status is stuck at connecting. Anyone else experiencing the same problem
Edit. Got through to the call centre. Area wide outage.
Last edited:
Stickfigure
Honorary Master
tracert www.google.co.za
Tracing route to www.google.co.za [105.187.241.42]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 443 ms 2171 ms 663 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 1321 ms 587 ms 425 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 652 ms 923 ms 1541 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 1229 ms 2636 ms * cache.google.com [105.187.241.42]
7 2056 ms 259 ms 144 ms cache.google.com [105.187.241.42]
Trace complete.
tracert capetown.spdtst.saix.net
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 276 ms 442 ms 175 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 134 ms 64 ms 559 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 368 ms 778 ms 172 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 252 ms 604 ms 177 ms 165.165.214.213
7 671 ms 752 ms 930 ms 196.43.51.26
8 2254 ms 242 ms 273 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 316 ms 150 ms 586 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
Tracing route to www.google.co.za [105.187.241.42]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 443 ms 2171 ms 663 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 1321 ms 587 ms 425 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 652 ms 923 ms 1541 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 1229 ms 2636 ms * cache.google.com [105.187.241.42]
7 2056 ms 259 ms 144 ms cache.google.com [105.187.241.42]
Trace complete.
tracert capetown.spdtst.saix.net
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 276 ms 442 ms 175 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 134 ms 64 ms 559 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 368 ms 778 ms 172 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 252 ms 604 ms 177 ms 165.165.214.213
7 671 ms 752 ms 930 ms 196.43.51.26
8 2254 ms 242 ms 273 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 316 ms 150 ms 586 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
Stickfigure
Honorary Master
Crawling tonight
tracert capetown.spdtst.saix.net
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 1354 ms 111 ms 178 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 1079 ms 732 ms 69 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 2207 ms 27 ms 45 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 81 ms 26 ms 95 ms 165.165.214.213
7 1574 ms 31 ms 28 ms 196.43.51.26
8 1092 ms 626 ms 71 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 475 ms 1222 ms 169 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
tracert capetown.spdtst.saix.net
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 1354 ms 111 ms 178 ms wbs-ip-hsll-2-gi3-1-0-vl102.telkom-ipnet.co.za [105.226.0.29]
4 1079 ms 732 ms 69 ms ipc-4-up.south.dsl.telkomsa.net [105.226.0.30]
5 2207 ms 27 ms 45 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
6 81 ms 26 ms 95 ms 165.165.214.213
7 1574 ms 31 ms 28 ms 196.43.51.26
8 1092 ms 626 ms 71 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [196.25.37.2]
9 475 ms 1222 ms 169 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
Charl101
Well-Known Member
The_Imp_ZA
Well-Known Member
- Joined
- Feb 4, 2013
- Messages
- 424
- Reaction score
- 53
Is it just me or is the TiTracker broken?
I noticed a week ago that the usage bar stopped going up, and for the past two days I've been deliberately downloading some things in the day to make it move, but it still stays at the same spot. I'm not sure if I'm lucky or if all of a sudden it's going to bounce to where I think it should be, which is about 3 quarters of the way into the orange section instead only half way in the green where it is now.
EDIT: I tried checking userstats.adsl.saix.net but that doesn't seem to be working at all any more. Maybe I've gotten lucky and my account has disappeared into the limbo.
I noticed a week ago that the usage bar stopped going up, and for the past two days I've been deliberately downloading some things in the day to make it move, but it still stays at the same spot. I'm not sure if I'm lucky or if all of a sudden it's going to bounce to where I think it should be, which is about 3 quarters of the way into the orange section instead only half way in the green where it is now.
EDIT: I tried checking userstats.adsl.saix.net but that doesn't seem to be working at all any more. Maybe I've gotten lucky and my account has disappeared into the limbo.
Last edited:
elf_lord_ZC5
Honorary Master
Mine is spiking like it is noboy's bussiness - been playing Guildwars 2, and I have "almost" DC'ed so many times it is not funny. You are running with the guild, and suddenly you are stuck and then the rest of the guild is 3/4 of the map away from you.