Telkom Internet Capped/Uncapped User Feedback (Pt2)

How is it that TI doesn't know that 10210 doesn't work? It's looking more like a communication disaster.

We aren't involved in the day-to-day operation of 10210, and we haven't been informed of any issues related to 10210 today.

However, I called 10210 before posting this message:

Doesn't sound like an ISP issue if you can't place a call ...

and got to the IVR.

There may have been a localised call routing issue of course ...
 
We aren't involved in the day-to-day operation of 10210, and we haven't been informed of any issues related to 10210 today.

However, I called 10210 before posting this message:



and got to the IVR.

There may have been a localised call routing issue of course ...

Any idea what broke earlier today for JHB? Everyone I spoke to had no internets and all seem to have come on at 1.20pm'ish. Also no one was able to contact 10210, but normal calls were fine
 
@ranger Everything is working great again, so no issues.

also

49ms on your first hop and 45ms on your second hop looks more like a Telkom Wholesale issue than a TI issue.

I should point out the my line is interleaved mode, and not fast mode which is what could apparently cause the high first hop, is it possible for Telkom to set it back to "fast" mode?
 
Any idea what broke earlier today for JHB? Everyone I spoke to had no internets and all seem to have come on at 1.20pm'ish. Also no one was able to contact 10210, but normal calls were fine

It's not just JHB, other regions were also fooked.
 
How long is it going to take to fix the authentication issues?

Just ran out of axxess bandwidth, tried TI again but no go, switched to fnb account and that works.
 
Just ran out of axxess bandwidth, tried TI again but no go, switched to fnb account and that works.
Took the servers and network down last night before the 20:00 outage to give the UPS batteries a chance to catch up after yesterdays fun & games and everything came up without hassles at 07:00 including TI authentication.

See we're on stage 2 load shedding again today so it'll be interesting to see if my clients still have problems or TI have waved the magic wand.
 
Last edited:
Took the servers and network down last night before the 20:00 outage to give the UPS batteries a chance to catch up after yesterdays fun & games and everything came up without hassles at 07:00 including TI authentication.

See we're on stage 2 load shedding again today so it'll be interesting to see if my clients still have problems or TI have waved the magic wand.

13+ minutes to authenticate today nearly half an hour after power was restored to the the area.
 
13+ minutes to authenticate today nearly half an hour after power was restored to the the area.
Is it something that is happening in a specific area or is it widespread? My router usually boots up in less than a minute and internet connectivity is established.
 
Is it something that is happening in a specific area or is it widespread? My router usually boots up in less than a minute and internet connectivity is established.

No idea - it's 3-4 minutes on a good, non-shedding, day with TI, less than half that using other ISPs.
 
13+ minutes to authenticate today nearly half an hour after power was restored to the the area.

Is it something that is happening in a specific area or is it widespread? My router usually boots up in less than a minute and internet connectivity is established.
I've had a couple of clients complain today but the problem does not seem as severe as yesterday when it could take over hour, no problem with capped accounts on other ISP's though.

Definitely appears that TI's systems (or SAIX from what ranger has said) are overloaded in a given area when power is restored after load shedding.
 
No idea - it's 3-4 minutes on a good, non-shedding, day with TI, less than half that using other ISPs.

I see no problems:

Code:
[root@test ~]# time ifup ppp1
Cannot find device "ppp1"
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
Remote message: Login ok
PAP authentication succeeded
local  IP address 105.227.174.xx
remote IP address 105.184.43.1
primary   DNS address 196.43.46.190
secondary DNS address 196.43.34.190

real    0m2.355s
user    0m0.038s
sys     0m0.159s
[root@test ~]#

We are seeing a lot more authentication requests since yesterday, but we put more resources in yesterday to deal with the additional load.

We have had some information regarding problems on the wholesale side affecting users on specific BNGs/ESRs, but this 3-4 minutes thing isn't due to anything on our side. We started seeing this a few weeks ago, about the time Wholesale AAA software was upgraded (when we had made no changes at all in 2 months).
 
I've had a couple of clients complain today but the problem does not seem as severe as yesterday when it could take over hour, no problem with capped accounts on other ISP's though.

Definitely appears that TI's systems (or SAIX from what ranger has said) are overloaded in a given area when the power is restored after load shedding.

I figured they'd be overloaded initially which is why I waited fifteen minutes before disconnecting the router from the aux power source and trying to reconnect. Surely that should be enough time for the riff-raff to reconnect?
 
I see no problems:

Code:
[root@test ~]# time ifup ppp1
Cannot find device "ppp1"
Using interface ppp1
Connect: ppp1 <--> /dev/pts/1
Remote message: Login ok
PAP authentication succeeded
local  IP address 105.227.174.xx
remote IP address 105.184.43.1
primary   DNS address 196.43.46.190
secondary DNS address 196.43.34.190

real    0m2.355s
user    0m0.038s
sys     0m0.159s
[root@test ~]#


We are seeing a lot more authentication requests since yesterday, but we put more resources in yesterday to deal with the additional load.

We have had some information regarding problems on the wholesale side affecting users on specific BNGs/ESRs, but this 3-4 minutes thing isn't due to anything on our side. We started seeing this a few weeks ago, about the time Wholesale AAA software was upgraded (when we had made no changes at all in 2 months).
Thanks ranger, this is what my router is reporting

Jul 18 00:01:03 daemon err syslog: User name and password authentication failed.
Jul 18 00:01:43 daemon err syslog: User name and password authentication failed.
Jul 18 00:02:06 daemon err syslog: User name and password authentication failed.
Jul 18 00:02:43 daemon err syslog: User name and password authentication failed.
Jul 18 00:03:06 daemon err syslog: User name and password authentication failed.
Jul 18 00:03:43 daemon err syslog: User name and password authentication failed.
Jul 18 00:04:05 daemon err syslog: User name and password authentication failed.
Jul 18 00:04:43 daemon err syslog: User name and password authentication failed.
Jul 18 00:05:06 daemon err syslog: User name and password authentication failed.
Jul 18 00:05:42 daemon err syslog: User name and password authentication failed.

… <This is where I got bored copying and pasting the same thing over and over>

Jul 18 00:12:54 daemon err syslog: User name and password authentication failed. **25th time!**
Jul 18 00:13:05 daemon crit syslog: Clear IP addresses. PPP connection DOWN.
Jul 18 00:13:05 daemon crit syslog: Received valid IP address from server. Connection UP.
 
Hm, what's the easiest way to upgrade from 4 to 10 as 10210 is pretty ridiculous to get through to.
 
Top
Sign up to the MyBroadband newsletter
X