Telkom Internet Capped/Uncapped User Feedback (Pt2)

@ Ranger

Does the bandwidth on Telkom's new fiber launched on Dec 1 go through the same IPC as normal ADSL?
 
MickeyD said:
It's time that the TI execs get some balls and explain to your group CEO how Wholesale are destroying TI's value.
Click to expand...

You missed competition law compliance training ...

It also exposes the CTO as he made it very clear in September that they had no outstanding IPC orders on hand.
Click to expand...

I think technically there weren't at the time because we were waiting for proposals, or otherwise they weren't counting our orders :-(
 
ellyally said:
A little better but still buggered here

http://speedtest.ookla.com/result/2785091099.png
http://www.speedtest.net/my-result/3994590125
http://testmy.net/2K0zpZW.ZUasQXy.png
Click to expand...

We have noticed an issue that is resulting in under-utilisation of SAIX capacity (affecting traffic from international and any local providers who don't peer with us). It seems some on-network or peering traffic may be tagged incorrectly resulting in qos policies shaping more than necessary. We are investigating (as of about 16h00), but haven't found a cause yet.
 
ellyally said:
@ranger

Just a quick question, any idea on when I should be getting better results in JHB? i.e., is JHB dependent on CTN upgrade (not sure how it works)?

Still not looking too good
http://speedtest.ookla.com/result/2784849551.png
Click to expand...

Jhb hasn't been having problems in general. However, different ip ranges may be routed differently over intl links. I can get *very* good speeds to that speedtest server on uncapped.

Have you ruled out dslam congestion?
 
Grouter said:
Well it's already destroyed for me (TI's value, that is). Cancellation effective 10 January.

It's been very interesting swapping between my TI accounts (capped and uncapped) and Afrihost capped. Afrihost just works. Page loads, lookups, downloads, nntp - hell, even torrents in the middle of the day @ 1 MBps.
Click to expand...

Well, we've bern waiting 4 months longer ghan anticipated to be able increase IPC capacity in Cape Town. Afrihost was in a similar position 3 months before us and people were crying in the Afrihost thread.

Perhaps it's because (I'm guessing) I break out straight on to MTN Business fibre at my exchange?
Click to expand...

No, it is because we had 15% too little IPC. Which we now have (but it might take another few hours to find some mis-tagged traffic to fix intl).

There are limits to the number of breakouts from IPC per ISP, and it is very unlikely you have a BPE at your exchange, and the latency from ESR to ISP is usually quite low (all on Telkom wholesale fibre anyway).
 
ranger said:
Jhb hasn't been having problems in general. However, different ip ranges may be routed differently over intl links. I can get *very* good speeds to that speedtest server on uncapped.

Have you ruled out dslam congestion?
Click to expand...

Never had congestion, and support keeps telling me no, so I'm guessing no.

Anyway, I disconnecting/reconnecting until I got a new ip address gives me http://speedtest.ookla.com/result/2785218694.png now? who would have thunk it. Thats the highest I have ever seen on my line, EVER

Problem now is speeds back, but pings gone to hell

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.20
traceroute to bbc.co.uk (212.58.244.20), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 2.794 ms 1.411 ms 1.796 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 11.145 ms 11.289 ms 10.119 ms
3 ipc-up-2.north.telkomsa.net (105.228.0.6) 136.233 ms 134.621 ms 132.568 ms
4 ipc-aggr-2.north.telkomsa.net (105.228.0.13) 145.168 ms 146.882 ms 148.174 ms
5 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 13.450 ms 12.904 ms 13.146 ms
6 rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.37) 148.358 ms 147.162 ms 148.239 ms
7 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 438.322 ms 408.624 ms 408.922 ms
8 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 408.943 ms 408.575 ms 409.267 ms
9 ae-7.r23.londen03.uk.bb.gin.ntt.net (129.250.6.54) 406.340 ms 411.382 ms 408.965 ms
10 bbc-linx.pr01.rbsov.bbc.co.uk (195.66.236.103) 409.036 ms 408.621 ms 406.632 ms
11 * * *
12 * * *
13 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 371.972 ms 409.018 ms 409.639 ms
14 132.185.255.149 (132.185.255.149) 407.632 ms 407.836 ms 409.746 ms
15 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 409.091 ms 408.639 ms 409.147 ms


Yesterday was fine, just no speed:

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.18
traceroute to bbc.co.uk (212.58.244.18), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 3.598 ms 0.895 ms 0.708 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 10.460 ms 9.835 ms 10.870 ms
3 ipc-1-up.north.dsl.telkomsa.net (105.224.0.6) 13.141 ms 14.221 ms 11.877 ms
4 ipc-aggr-1.north.telkomsa.net (105.224.0.13) 13.300 ms 12.829 ms 13.237 ms
5 165.165.216.221 (165.165.216.221) 12.959 ms 12.919 ms 13.405 ms
6 lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.58) 189.911 ms 188.853 ms 189.761 ms
7 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 189.935 ms 187.676 ms 188.213 ms
8 ae-7.r23.londen03.uk.bb.gin.ntt.net (129.250.6.54) 195.517 ms 194.641 ms 187.807 ms
9 bbc-linx.pr01.rbsov.bbc.co.uk (195.66.236.103) 189.491 ms 189.575 ms 189.493 ms
10 * * *
11 * * *
12 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 193.222 ms 191.398 ms 190.542 ms
13 132.185.255.149 (132.185.255.149) 197.681 ms 197.577 ms 199.209 ms
14 fmt-vip72.telhc.bbc.co.uk (212.58.244.18) 188.769 ms 188.447 ms 188.313 ms
 
wingnut771 said:
Please post your line stats (snr & atten)
Click to expand...

Its not my line, congestion, shaping, throttling etc etc etc... been on this problem for a while now and have ruled out all that sort of stuffs... also, kinda fishy that as soon as ip changed and speed is back the ping died

ADSL Link - Downstream - Upstream
Connection Speed - 2048 kbps - 511 kbps
Line Attenuation - 2.5 db - 3.8 db
Noise Margin - 10.3 db - 22.5 db
 
Last edited:
I've noticed Youtube streaming has been really patchy this last week or so.
 
Seems something was fixed, all back to 'normal', hopefully it holds:)

http://testmy.net/OhrAl0P.pjwzOLF.png
http://www.speedtest.net/my-result/3995318655
http://speedtest.ookla.com/result/2785298921.png

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.18
traceroute to bbc.co.uk (212.58.244.18), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 2.216 ms 1.803 ms 1.490 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 10.137 ms 10.484 ms 12.379 ms
3 ipc-up-2.north.telkomsa.net (105.228.0.6) 13.186 ms 13.107 ms 13.086 ms
4 ipc-aggr-2.north.telkomsa.net (105.228.0.13) 14.303 ms 13.417 ms 15.547 ms
5 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 13.125 ms 12.721 ms 13.422 ms
6 196.25.166.217 (196.25.166.217) 13.895 ms 15.143 ms 13.900 ms
7 lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za (196.43.9.58) 180.429 ms 180.547 ms 181.094 ms
8 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 192.019 ms 192.509 ms 191.385 ms
9 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) 193.874 ms 192.037 ms 191.742 ms
10 bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103) 181.491 ms 180.765 ms 182.810 ms
11 * * *
12 * * *
13 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 195.694 ms 191.644 ms 194.185 ms
14 132.185.255.149 (132.185.255.149) 192.690 ms 191.672 ms 192.188 ms
15 fmt-vip72.telhc.bbc.co.uk (212.58.244.18) 191.733 ms 191.490 ms 192.825 ms
 
ellyally said:
Its not my line, congestion, shaping, throttling etc etc etc... been on this problem for a while now and have ruled out all that sort of stuffs... also, kinda fishy that as soon as ip changed and speed is back the ping died

ADSL Link - Downstream - Upstream
Connection Speed - 2048 kbps - 511 kbps
Line Attenuation - 2.5 db - 3.8 db
Noise Margin - 10.3 db - 22.5 db
Click to expand...

Those are awesome atten stats, but download snr seems dodge, here are mine:

t1.jpg

As you can see, my max attainable sync according to noise/distance is roughly 12mb on G.dmt.

I once had an issue with my upload snr was low, had telkom come check it out, they put their router on and the problem went away.

Try another router if the problem comes back.
 
Had a normal couple of minutes earlier tonight...

But afraid now back to this:

3995397993.png
 
wingnut771 said:
Those are awesome atten stats, but download snr seems dodge, here are mine:

View attachment 176317

As you can see, my max attainable sync according to noise/distance is roughly 12mb on G.dmt.

I once had an issue with my upload snr was low, had telkom come check it out, they put their router on and the problem went away.

Try another router if the problem comes back.
Click to expand...

I've never had issues with it before... I can honestly say in the last 6-8 years I've never had any line issues. I think I maybe opened a ticket 2-3 times for something... nothing in the last 4-5 years that I can recall, until a few months ago when the google problem started(I think june/july'ish). As far as I remember its always been around 10-15, but I'm positive thats not the problem here. I'll give em a call and get it sorted anyhow. Thanks
 
Last edited:
Everything looks like its back to normal:)

http://speedtest.ookla.com/result/2785523173.png

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.20
traceroute to bbc.co.uk (212.58.244.20), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 3.060 ms 0.931 ms 0.796 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 9.866 ms 10.578 ms 10.120 ms
3 ipc-up-2.north.telkomsa.net (105.228.0.6) 14.530 ms 12.754 ms 12.291 ms
4 ipc-aggr-2.north.telkomsa.net (105.228.0.13) 13.950 ms 12.905 ms 12.188 ms
5 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 12.728 ms 13.007 ms 12.164 ms
6 165.165.216.221 (165.165.216.221) 13.168 ms 13.424 ms 13.266 ms
7 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 180.755 ms 179.737 ms 180.395 ms
8 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 181.784 ms 180.543 ms 181.325 ms
9 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) 180.628 ms 181.452 ms 189.384 ms
10 bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103) 181.562 ms 179.950 ms 180.217 ms
11 * * *
12 * * *
13 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 193.320 ms 191.082 ms 191.573 ms
14 132.185.255.149 (132.185.255.149) 181.821 ms 181.782 ms 183.472 ms
15 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 191.667 ms 190.802 ms 190.973 ms

Edit: never mind, must have been another intermittent 'all is well' few minutes, back to

Traceroute has started…

traceroute: Warning: bbc.co.uk has multiple addresses; using 212.58.244.20
traceroute to bbc.co.uk (212.58.244.20), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 3.610 ms 0.767 ms 0.744 ms
2 rrba-ip-bng-1.north.dsl.telkomsa.net (105.224.208.1) 10.254 ms 10.081 ms 10.177 ms
3 ipc-up-2.north.telkomsa.net (105.228.0.6) 269.410 ms 271.437 ms 409.527 ms
4 ipc-aggr-2.north.telkomsa.net (105.228.0.13) 409.633 ms 408.983 ms 409.318 ms
5 cen-pr-01-be200-vl1.net.telkomsa.net (105.228.0.18) 409.870 ms 409.131 ms 409.461 ms
6 165.165.216.221 (165.165.216.221) 409.908 ms 409.042 ms 409.702 ms
7 lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za (196.43.9.46) 616.514 ms 611.925 ms 614.441 ms
8 xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net (83.231.146.245) 409.632 ms 613.821 ms 614.163 ms
9 ae-6.r22.londen03.uk.bb.gin.ntt.net (129.250.4.20) 614.436 ms 613.822 ms 613.977 ms
10 bbc-linx.pr01.thdow.bbc.co.uk (195.66.224.103) 614.493 ms 614.358 ms 614.065 ms
11 * * *
12 * * *
13 ae0.er01.telhc.bbc.co.uk (132.185.254.109) 509.770 ms 614.072 ms 445.114 ms
14 132.185.255.149 (132.185.255.149) 578.964 ms 428.796 ms 422.295 ms
15 fmt-vip71.telhc.bbc.co.uk (212.58.244.20) 438.011 ms 452.268 ms 469.423 ms
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X