Telkom Internet Uncapped User Feedback.

Status
Not open for further replies.
Morning guys.

AS I mentioned a bit earlier in the week, I moved to uncapped on Monday.
This morning I realized that my IP has changed to the 105 range.
Speeds are looking good and my Ping has dropped, but is still dismally high.(from 413 ms to 375 ms)

My question though, when I try to stream Supersport I get a message



I've never seen this.
Is this normal?

Same here, looks like the same IP range (105) that was causing problems when Afrihost moved to the MTN backbone.

I've been confirming details on various gmail accounts this morning because of the new IPs.

Speedtest.net is also borked in respect of location.
 
Thx Mick.
I also had to confirm various Gmail accounts. Forgot to mention that part.
That is actually when I came aware of the 105 IP range. Got the warning of a possible hack attempt and then saw that it it was my current IP address.

The speeds and ping are very up and down atm, but in general my speeds and ping are better than before.

Did receive a telephone from Telkom network guy yesterday. Told me that he rerouted stuff on my line and that he will contact me again today for feedback.

Not sure if the improvement came from his intervention or the move to new IP, but I'm just glad it did improve. I just hope something can be done to drop my international ping to 250ms or less.
As the system letter warned though, maintenance still till the 4th.
 
My question though, when I try to stream Supersport I get a message

I've never seen this.
Is this normal?

I have sent a message on their support form, does anyone know the best way to contact their technical staff?
 
Morning guys.
This morning I realized that my IP has changed to the 105 range.
Speeds are looking good and my Ping has dropped, but is still dismally high.(from 413 ms to 375 ms)

Please post a new trace, any previous trace is invalid.
 
Please post a new trace, any previous trace is invalid.
Morning Ranger.
I'm a much happier person this morning than the last 4 months, but here goes.

For International:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Ronald>cd\

C:\>tracert google.com

Tracing route to google.com [173.194.41.132]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 151 ms 152 ms 151 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 170 ms 168 ms 174 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 175 ms 175 ms 175 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 176 ms 176 ms 177 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 321 ms 320 ms 325 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.58]
7 313 ms 325 ms 315 ms 196.25.191.146
8 320 ms 320 ms 320 ms 209.85.240.61
9 313 ms 312 ms 314 ms 72.14.238.55
10 321 ms 314 ms 312 ms lhr08s03-in-f4.1e100.net [173.194.41.132]

Trace complete.


Local:

C:\>tracert consoleracing.co.za

Tracing route to consoleracing.co.za [196.38.40.232]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 151 ms 152 ms 153 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 169 ms 167 ms 168 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 178 ms 175 ms 175 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 176 ms 176 ms 175 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 197 ms 196 ms 196 ms 196.43.52.42
7 199 ms 197 ms 199 ms 196.43.25.138
8 191 ms 191 ms 191 ms internet-solutions-gw.telkom-ipnet.co.za [196.25
.46.90]
9 189 ms 189 ms 191 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
10 193 ms 192 ms 192 ms core1a-pkl-te1-2.isnet.net [168.209.100.238]
11 197 ms 197 ms 198 ms csw1-b-jup-bry-gi3-2.ip.isnet.net [168.209.218.2
1]
12 198 ms 198 ms 197 ms 196.34.134.105
13 * 320 ms * gw.aserv.co.za [196.33.227.1]
14 199 ms 199 ms 200 ms randomtask.aserv.co.za [196.38.40.232]

Trace complete.

C:\>
 
Last edited:
My international seems to be crawling at the moment...anyone experiencing the same?
 
Out of curiosity, what happens today to the people previously on one of their uncapped options? Do they just get a cheaper bill each month and have their day time restrictions removed?

I am signing up today for the 2mb uncapped, I hope there are no issues with the service.
 
International is absolutely crawling. I'm going to assume something is wrong with the new IP range. Did a new cable go live or something?
 
Out of curiosity, what happens today to the people previously on one of their uncapped options? Do they just get a cheaper bill each month and have their day time restrictions removed?

Correct except I've never experienced any day time restrictions prior to the new AUP.
 
I see RoMark clearly has a congested exchange, can someone who is not on a congested exchange please paste me a traceroute to mail.google.com, myadsl.co.za and www.speedtest.net?

Thank :D
 
I see RoMark clearly has a congested exchange, can someone who is not on a congested exchange please paste me a traceroute to mail.google.com, myadsl.co.za and www.speedtest.net?

Thank :D

Here yer go:

Code:
[mick@mick1 ~]$ traceroute mail.google.com
traceroute to mail.google.com (173.194.32.54), 30 hops max, 60 byte packets
 1  newcop (192.168.11.254)  0.133 ms  0.090 ms  0.082 ms
 2  224-140-1.dsl.subscriber.telkomsa.net (105.224.140.1)  19.274 ms  29.404 ms  29.411 ms
 3  226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6)  39.417 ms  39.411 ms  39.391 ms
 4  226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13)  39.372 ms  49.232 ms  49.242 ms
 5  wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45)  59.214 ms  59.223 ms  59.203 ms
 6  lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46)  208.976 ms  208.745 ms  208.724 ms
 7  196.25.191.146 (196.25.191.146)  208.635 ms  189.382 ms  179.694 ms
 8  209.85.240.61 (209.85.240.61)  179.656 ms  178.564 ms 209.85.240.63 (209.85.240.63)  178.548 ms
 9  209.85.253.90 (209.85.253.90)  178.525 ms  178.611 ms  169.975 ms
10  209.85.240.28 (209.85.240.28)  189.693 ms  189.098 ms  189.091 ms
11  66.249.95.133 (66.249.95.133)  199.077 ms  199.685 ms  199.665 ms
12  209.85.241.193 (209.85.241.193)  319.587 ms  319.599 ms  249.596 ms
13  216.239.43.255 (216.239.43.255)  229.467 ms  229.460 ms  208.191 ms
14  arn06s02-in-f22.1e100.net (173.194.32.54)  208.093 ms  208.102 ms  208.081 ms

[mick@mick1 ~]$ traceroute myadsl.co.za
traceroute to myadsl.co.za (41.203.21.137), 30 hops max, 60 byte packets
 1  newcop (192.168.11.254)  0.129 ms  0.087 ms  0.083 ms
 2  224-140-1.dsl.subscriber.telkomsa.net (105.224.140.1)  29.506 ms  29.485 ms  29.462 ms
 3  226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6)  39.581 ms  39.593 ms  39.572 ms
 4  226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13)  49.497 ms  49.507 ms  49.486 ms
 5  wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45)  59.408 ms  59.420 ms  59.397 ms
 6  196.43.52.38 (196.43.52.38)  79.150 ms  78.900 ms  78.874 ms
 7  196.43.25.138 (196.43.25.138)  89.012 ms  69.337 ms  69.308 ms
 8  mtn-gw.telkom-ipnet.co.za (196.25.58.18)  59.405 ms  59.132 ms  59.159 ms
 9  41.181.139.108 (41.181.139.108)  69.116 ms  59.216 ms  59.180 ms
10  196.44.31.97 (196.44.31.97)  59.159 ms  59.220 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221)  59.181 ms
11  ge4-0-0.gw17.jnb6.za.mtnbusiness.net (196.30.1.37)  59.121 ms  58.923 ms  58.898 ms
12  vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136)  68.813 ms  59.916 ms  59.883 ms
13  core-router1.jnb2.host-h.net (196.30.213.108)  69.662 ms  69.650 ms  69.626 ms
14  core-access-switch1-vlan1001.jnb.host-h.net (41.72.136.53)  69.609 ms  79.542 ms  79.547 ms
15  mybroadband.co.za (41.203.21.137)  79.510 ms  79.488 ms  79.486 ms

[mick@mick1 ~]$ traceroute www.speedtest.net
traceroute to www.speedtest.net (74.209.160.12), 30 hops max, 60 byte packets
 1  newcop (192.168.11.254)  0.129 ms  0.091 ms  0.094 ms
 2  224-140-1.dsl.subscriber.telkomsa.net (105.224.140.1)  19.436 ms  19.441 ms  29.561 ms
 3  226-0-6.dsl.subscriber.telkomsa.net (105.226.0.6)  49.359 ms  49.368 ms  49.348 ms
 4  226-0-13.dsl.subscriber.telkomsa.net (105.226.0.13)  49.325 ms  49.301 ms  59.400 ms
 5  wblv-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.45)  69.414 ms  69.427 ms  69.407 ms
 6  lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.58)  209.109 ms  208.886 ms  208.861 ms
 7  tenge7-2.var01.ldn04.pccwbtn.net (63.218.243.17)  219.106 ms  199.635 ms  199.599 ms
 8  netriver.ge2-16.br01.sea01.pccwbtn.net (63.216.14.162)  349.605 ms  338.501 ms  338.487 ms
 9  static-74-209-160-12.lynnwood.netriver.net (74.209.160.12)  428.412 ms  438.387 ms  428.830 ms
[mick@mick1 ~]$
 
Thanks Mick,

Better than my capped WA account @ the office but my Vanilla OW Uncapped @ home has lower pings
 
Wow - look at my traceroute to www.speedtest.net

Code:
Tracing route to www.speedtest.net [74.209.160.12]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    11 ms    11 ms    10 ms  224-12-1.dsl.subscriber.telkomsa.net [105.224.12.1]
  3    22 ms    22 ms    22 ms  105.228.0.6
  4    23 ms    23 ms    23 ms  105.228.0.13
  5    29 ms    22 ms    25 ms  rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.41]
  6   292 ms   230 ms   229 ms  ams-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.90]
  7   291 ms   343 ms     *     213.19.192.1
  8   437 ms   443 ms   438 ms  ae-52-52.csw2.Amsterdam1.Level3.net [4.69.139.18
5]
  9   440 ms   438 ms     *     ae-59-224.ebr2.Amsterdam1.Level3.net [4.69.153.213]
 10     *        *        *     Request timed out.
 11   439 ms   445 ms   437 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

 12   440 ms   443 ms   451 ms  ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
 13   437 ms     *      437 ms  ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254]

 14   440 ms   436 ms   439 ms  ae-2-2.ebr1.Chicago1.Level3.net [4.69.132.65]
 15   448 ms   448 ms     *     ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
 16   436 ms   438 ms   435 ms  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
 17   440 ms   449 ms   436 ms  ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
 18   358 ms   372 ms   356 ms  ae-24-52.car4.Seattle1.Level3.net [4.69.147.166]

 19   351 ms   351 ms   351 ms  NETRIVER-IN.car4.Seattle1.Level3.net [4.71.156.162]
 20   400 ms   398 ms   397 ms  speedtest.net [74.209.160.12]

Trace complete.

What the hell telkom :mad:

EDIT: Just seen the other thread and the explanation from ranger...hopefully this can get sorted asap!
 
Last edited:
International is absolutely crawling. I'm going to assume something is wrong with the new IP range. Did a new cable go live or something?

The change has resulting in some redistribution of traffic over international links, resulting in congestion on some links. IPNet staff are currently implementing changes to rebalance the traffic on these links.
 
Thanks Mick,

Better than my capped WA account @ the office but my Vanilla OW Uncapped @ home has lower pings

From Cape Town, you should get about 40ms lower latency than MickZA. MickZA takes 60ms to get to a router in Cape Town, it should take you less than 20 to get there.
 
As far as I can tell, this seems fixed (probably as of 15h15 or so).

Nothing is fixed. Int is crawling and my pings are higher on telkom than with WA.

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 * 10 ms 10 ms 224-144-1.dsl.subscriber.telkomsa.net [105.224.1
44.1]
3 11 ms 11 ms 10 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 11 ms 10 ms 11 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 10 ms 10 ms 10 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 33 ms 33 ms 33 ms 196.43.39.162
7 31 ms 31 ms 32 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
8 36 ms 36 ms 36 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
9 * 35 ms 36 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X