Telkom Internet Capped/Uncapped User Feedback (Pt2)

Things are up to schite again tonight, crap speed & high latency.

Been shocking for me for most of the day (cant even stream youtube 360p on 4MB), this morning was ok. Change over to Afrihost capped and things are at full speed.
 
Is it Thursday yet? Didn't think so ...

That's what I told the call centre guy that called earlier sking if my issue is resolved :D He then wanted to do the normal ticksheet test with me over the phone for the umpteenth time and I said 'no'.

Just keeping log of things.
 
TI Tracker

When did you download that extra 10GB, I seem to recall, that it was mentioned the usage bar does not update in real time.

Sorry I meant to say when I got to about 10 gig last month, the bar was at 10% and green. Up until yesterday, I've done around 30 gig outside NightSurfer so far this month, and my TI Tracker still has no bar. Very strange :confused:
 
Dum dum dummmm....

Here's hoping by the time I wake up the fix has been applied and is working #FINGERSCROSSED
 
Been having this problem for a couple of months now... its not the end of the world, but does get irritating when I'm busy with something. Every couple of days, around this time, mid-day'ish, the browsing dies completely. Emails, ftp etc all continue to work fine, but can't browse anything. It lasts 10-15min or so, by the time I log it, its 'fixed'.

Anyone else having random internet browsing drops every couple of days?

Edit: like this... started typing post on mobile after it went down, hit post, switched back to dsl to test and its already working again:wtf:
 
Last edited:
Meh, so it keeps dropping my browsing more today than ever before... just getting here took a few attempts

traceroute to www.mybroadband.co.za (197.242.89.170), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.839 ms 0.395 ms 0.307 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 9.728 ms 9.574 ms 10.180 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 67.156 ms 68.313 ms 67.449 ms
4 ti-224-0-13.telkomadsl.co.za (105.224.0.13) 758.281 ms 767.896 ms *
5 rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.39.37) 75.428 ms 75.375 ms 74.646 ms
6 rrba-ip-lir-1-gig-7-0-0.telkom-ipnet.co.za (196.43.11.202) 119.375 ms 115.905 ms 117.032 ms
7 rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za (196.43.25.138) 110.561 ms 107.025 ms 111.736 ms
8 internet-solutions-gw.telkom-ipnet.co.za (196.25.46.90) 113.281 ms 113.971 ms 141.172 ms
9 ar2-rba-gi0-1.ip.isnet.net (168.209.1.172) 118.902 ms 114.104 ms 115.735 ms
10 mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net (168.209.86.250) 114.326 ms 113.379 ms 117.639 ms
11 * * *
12 core.gp-cn-het-mee-1.to.gp-mr-vod-mee-1.dfa.p2p.10g.za.africainx.net (41.84.12.151) 119.206 ms 120.857 ms 114.070 ms
13 41-66-132-246-f6.het001-cpe-1-to-gp-cn-het-mee-1.africainx.net (41.66.132.246) 114.262 ms 112.984 ms 110.829 ms
14 core-access-switch1.jnb1.host-h.net (197.189.193.1) 112.482 ms 112.645 ms 111.525 ms
15 row-access-switch1-row3-4.jnb1.host-h.net (197.189.193.36) 118.713 ms 118.521 ms 123.225 ms
16 197.242.89.170 (197.242.89.170) 116.711 ms 108.193 ms 107.919 ms


And this is pretty much for anything other than .co.za

Traceroute has started…

traceroute: Warning: www.youtube.com has multiple addresses; using 74.125.233.71
traceroute to youtube-ui.l.google.com (74.125.233.71), 64 hops max, 72 byte packets
1 10.0.0.2 (10.0.0.2) 0.655 ms 0.336 ms 0.280 ms
2 ti-224-208-01.telkomadsl.co.za (105.224.208.1) 10.085 ms 10.649 ms 10.167 ms
3 ti-224-0-06.telkomadsl.co.za (105.224.0.6) 62.562 ms 61.949 ms 61.856 ms
4 * ti-224-0-13.telkomadsl.co.za (105.224.0.13) 755.847 ms 738.590 ms
5 * ti-228-0-17.telkomadsl.co.za (105.228.0.17) 702.948 ms 693.543 ms
6 * * *
7 * ti-228-0-17.telkomadsl.co.za (105.228.0.17) 706.543 ms *
8 * * ti-228-0-18.telkomadsl.co.za (105.228.0.18) 746.028 ms
9 ti-228-0-17.telkomadsl.co.za (105.228.0.17) 702.122 ms 706.892 ms *
10 * * *
11 * * ti-228-0-17.telkomadsl.co.za (105.228.0.17) 710.909 ms
12 * * *
13 ti-228-0-17.telkomadsl.co.za (105.228.0.17) 713.553 ms 717.299 ms 699.654 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 ti-228-0-17.telkomadsl.co.za (105.228.0.17) 712.058 ms * *
20 * * *
21 * ti-228-0-17.telkomadsl.co.za (105.228.0.17) 718.753 ms *
22 * * *
23 ti-228-0-17.telkomadsl.co.za (105.228.0.17) 703.751 ms * 711.692 ms
24 * * *
 
Last edited:
Given how performance was last night and today from 11:00, I am going back to capped. Time to try Axxess :)
 
Cant access anything Google related today(gmail ,search ,youtube) , anyone else ?
Same here, started at around 10:40. Wonder if it has anything to do with the 140-pair fiber cut in Midrand yesterday afternoon.
Traceroutes to Google sites get stuck hopping between 105.228.0.17 and 105.228.0.18
 
Same here, started at around 10:40. Wonder if it has anything to do with the 140-pair fiber cut in Midrand yesterday afternoon.
Traceroutes to Google sites get stuck hopping between 105.228.0.17 and 105.228.0.18
Problem sorted.
 
Question:
Now that Telkom Simple Uncapped Plus has gone from R644 to R770 p/m overnight, is Do Uncapped Advance a cheaper option giving the same? Cannot see from their website whether it is R705 p/m all in month-to-month, or R 585 (package) + R 166.50 (rental).
http://www.telkom.co.za/sites/athom...&productname=do Uncapped Advance#.U-ypsfmSzXg

I don't have a Telkom phone for the 'free' after hours calls and never bothered to collect 3G modem with negligible data allocation p/m from Telkom shop which one apparently receives with Simple package, so not phased with that. Am using the free ADSL router though.

All I want is 4mb, uncapped on month-to-month. Wondering whether I am paying more than I should... in context, that is :)
Tried the call centre once asking about this - was basically threatened with world wars, never ending contracts and armageddon should I dare change anything.
 
There was a trasmission failure in Gauteng affecting half of our IPC capacity, as well as one of two peering links to Google.

For some reason, while the traffic is usually load-balanced across the links, when one links failed, not all traffic failed over to the other link, , affecting any Google services available in Johannesburg. Since bgp to Google was up they didn't automatically reroute.

We took some diagnostics and will compare to the status now that the links have recovered.

Traffic will not be managed correctly for a few more minutes while traffic normalises.
 
So regarding Durban, the stats show that one issue has been resolved, in that the experience is more uniform (no more 25% consumer uncapped being worse affected). However, it looks like on average the experience isn't that much better yet.

We are awaiting proposals from wholesale for IPC upgrades for all 3 sites, with Durban getting the biggest proportional upgrade, to address the average experience. Unfortunately since we haven't received a proposal yet it is unlikely we will be able to get the upgrade before Monday afternoon, even Tuesday is optimistic if we receive a proposal tomorrow.
 
Top
Sign up to the MyBroadband newsletter
X