Telkom Internet Capped/Uncapped User Feedback (Pt2)

Fot the first time since I can remember I can stream twitch.tv on low in the Western Cape! Medium still won't work on 4mb.
I hope this continues for the rest of the day. I will test it again in the afternoon.
 
There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.

Appreciate the feedback "ranger"
 
There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.

Thank you.
Which ADSL ISPs should theoretically be affected by this? All?
 
There's no doubt you've been put on a 10Mb exchange with those speeds.

my speed test is....speed.jpg

The faster speeds are only at the end of last month .usagereport2014-05-04.jpg


Cumulative Totals for April 2014.jpg

Reading Rangers Quote .and we are hoping to not punish people who have the one bad month

Was throttled always about the 20th on the 1meg line SO upgraded to 2 meg Now 4meg and have never been over the green .
Was RED on the 27th but was not throttled .
With School Hols XBOX Live and some Kid got a Brand new laptop (hisfirst )
I can have my PC internet Bandwith Back :)

and I just found out how to do this image thing
 
There is a failure on the IPNet core network, affecting traffic between regions. Thus, Gauteng is worst affected on international traffic. Durban and Cape Town seem to be affected mainly for content in Gauteng, but not international content. There is no SAIX notice yet, and we haven't received any other official communication.

Ok, by 09h27 there was actually a notice, NN0022980.

Apparently the fibre was spliced at 11h02. It may take some time for traffic to normalise, but our traffic volumes in Gauteng have already doubled.
 
Thanks for that ranger. Hopefully will be better.
Pity you aren't the norm for customer service within your company.
 
lol, holding since 11:30 for cancellations....



still holding and its now 12:12. Even the crap music has stopped playing. Now I only get recorded voice every few minutes telling to please hold etc etc.

This really is a genius tactic by Telkom
 
Last edited by a moderator:
lol, holding since 11:30 for cancellations....



still holding and its now 12:12. Even the crap music has stopped playing. Now I only get recorded voice every few minutes telling to please hold etc etc.

This really is a genius tactic by Telkom

I would love Telkom to have a Queueing system That told you what number you were in the Queue and how long your call will take to be answered ?
then you can Hold or hangup.
 
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?
 
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?

Agreed. It BS.
I'm still waiting for my call back. I doubt it will come.
 
We have been working on other approaches to managing abuse on our uncapped accounts, but the development is not complete yet, so it isn't an immediate solution to current problems. However, a lot of people have complained about things like rolling windows (e.g. IS star rating), and we are hoping to not punish people who have the one bad month, but at the same time we know we need to fix the current experience. Unfortunately, the past 3 weeks haven't been very productive (too many key people on leave), so there is still a lot of work to be done.

There are some initiatives that should bear some fruit in the next 2 to 3 weeks (but these are dependent on external parties to get things in place).
Whatever you do to manage bandwidth, it should not be a surprise to the client. That's my beef.
 
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?

Some other ISPs I know have the same system, they originate the call to verify the cancellation. Part of their security.
 
Well update on my post made on the 16th April regarding the terrible performance I have been getting on my Telkom line since early February.

4 mbs residential uncapped user in the Cape Town area. Still can't watch twitch streams in any quality and every night from 19:00 the internet becomes essentially unusable. YouTube videos struggle to load at 144p quality, latency to international game servers jumps around wildly and web pages take ages to load. There have also been random periods of terrible performance during the day as well now.

All faults I have opened are either being ignored or closed without the fault being resolved as has been going on since this problem started. The only thing I have not tried is going to a Telkom store to try and fix this.
 
Call was answered exactly after 1 hour of holding. What I do not however understand is, why must I now wait for another call to verify that I am cancelling? Especially after having to answer security questions?

Is it maybe to do with cooling off? Maybe when they ring back you changed your mind. I know a few companies I have come across that do that.
 
Still getting bad lag from up north... and just a question, why do we go through India?

206-127-159-239.plaync.com.png
 
I'm confused,
Why is my line streaming terribly yet the speedtest looks like this?

2589519162.png

Afrihost capped account streaming just fine in HD.
 
Still getting bad lag from up north... and just a question, why do we go through India?

I get the same thing when I run a traceroot to twitch.tv...

Tracing route to cdn.justin.tv.c.footprint.net [4.26.231.254]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 11 ms 11 ms 11 ms ti-224-100-01.telkomadsl.co.za [105.224.100.1]
3 13 ms 13 ms 12 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 14 ms 12 ms 13 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 12 ms 12 ms 12 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.
153]
6 36 ms 36 ms 36 ms nngy-ip-hsll-1-gig-2-0-0.telkom-ipnet.co.za [196
.43.51.250]
7 124 ms 124 ms 125 ms if-3-0-1.core1.COV-Cochin.as6453.net [116.0.85.1
]
8 257 ms 258 ms 251 ms if-4-0-0.core1.MLV-Mumbai.as6453.net [209.58.105
.37]
9 357 ms 354 ms 375 ms if-11-3-2-0.tcore1.MLV-Mumbai.as6453.net [180.87
.38.93]
10 355 ms 354 ms 360 ms if-9-5.tcore1.WYN-Marseille.as6453.net [80.231.2
17.17]
11 348 ms 349 ms 355 ms if-8-1600.tcore1.PYE-Paris.as6453.net [80.231.21
7.6]
12 356 ms 352 ms 349 ms if-2-2.tcore1.PVU-Paris.as6453.net [80.231.154.1
7]
13 331 ms 231 ms 230 ms 80.231.153.66
14 230 ms 230 ms 229 ms ae-60-60.csw1.Paris1.Level3.net [4.69.168.62]
15 228 ms 228 ms 228 ms ae-61-61.ebr1.Paris1.Level3.net [4.69.161.77]
16 231 ms 230 ms 230 ms ae-47-47.ebr1.London1.Level3.net [4.69.143.109]

17 233 ms 233 ms 233 ms ae-58-113.csw1.London1.Level3.net [4.69.153.122]

18 231 ms 230 ms 231 ms ae-118-3504.edge3.London1.Level3.net [4.69.166.1
42]
19 * * * Request timed out.
20 * * * Request timed out.
 
Last edited:
I get the same thing when I run a traceroot to twitch.tv...
...
If I'm not mistaken, Twitch.tv uses a CDN that disables ping requests as a method of alleviating stress from their servers. This is also a simple way to prevent a mass attack of pings (DDOS).
Code:
Tracing route to twitch.tv [192.16.71.171]
over a maximum of 30 hops:

  1    21 ms    13 ms     9 ms  ti-224-164-01.telkomadsl.co.za [105.224.164.1]
  2    57 ms    55 ms    55 ms  ti-229-0-06.telkomadsl.co.za [105.229.0.6]
  3    56 ms    58 ms    58 ms  ti-229-0-29.telkomadsl.co.za [105.229.0.29]
  4    60 ms    59 ms    62 ms  tbnb-ip-hsll-1-wan.telkom-ipnet.co.za [165.165.2
35.173]
  5   226 ms   227 ms   225 ms  lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9  ^C

You can test the pings of Twitch.tv servers using this http://www.teamliquid.net/forum/tech-support/326034-jtvping-find-your-best-twitchtv-server
Twitch is a child of Justin.tv, so it uses Justin.tv's CDN.

I don't route through India according to tracerts. I can't stream any quality without constant buffering, even though speed tests are fine. Same problems as everyone seems to be having.
 
Top
Sign up to the MyBroadband newsletter
X