Telkom ISP Issues

I'm having the same issue with Telkom ISP, however the speed test on Vumatel site shows full line speed, while saix or any other speed meter shows about 5% of the full line rate. This has been happening since about Friday, the line was fine today until the connection dropped sometime in the afternoon, it's horrific right now, YouTube is showing stuff in 360p. Telkom did send out a scheduled maintenance sms last week for their email system, have no idea why the rest of the service is affected.
 
I'm having the same issue with Telkom ISP, however the speed test on Vumatel site shows full line speed, while saix or any other speed meter shows about 5% of the full line rate. This has been happening since about Friday, the line was fine today until the connection dropped sometime in the afternoon, it's horrific right now, YouTube is showing stuff in 360p. Telkom did send out a scheduled maintenance sms last week for their email system, have no idea why the rest of the service is affected.
Yes, its the same issue and the timing is the same from Friday. try your speedtest after 23h00, that when it returns to full speed. I am in Randburg area, where about are you? I did log a call with Telkom, got a sms stating a possible network fault.
 
And right on time, after 23h00, speed returns. Is it the network? Or TelkomZa Throttling protocols messed up. Or is this because it in night surfing time? @TelkomZA

SpeedTest201906102313.PNG
 
Just some stats I have regarding to problem. If I change over to Afrihost there is no problem but I have a limited cap on Afrihost and I am paying Telkom for a 200mb line so I am not exactly happy with this.

I noticed the problem starts getting bad from about 15:30 and then clears up at about 22:30, below are some relevant pings to a telkom IP address (105.187.235.5) two hops away

Normal ping is sub 5ms
Mon Jun 10 14:13:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.83 ms
Mon Jun 10 14:15:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.55 ms
Mon Jun 10 14:17:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=4.42 ms

Just after 15:00 is starts degrading
Mon Jun 10 15:09:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.76 ms
Mon Jun 10 15:11:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=4.01 ms
Mon Jun 10 15:13:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=4.38 ms
Mon Jun 10 15:15:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=10.0 ms
Mon Jun 10 15:17:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=9.59 ms
Mon Jun 10 15:19:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.54 ms
Mon Jun 10 15:21:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=17.6 ms
Mon Jun 10 15:23:26 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=35.3 ms

By 16:20 is constantly averaging over 50ms
Mon Jun 10 16:21:27 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=51.0 ms
Mon Jun 10 16:23:27 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=54.3 ms
Mon Jun 10 16:25:27 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=54.3 ms
Mon Jun 10 16:27:27 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=42.6 ms

It returns to normal at about 22:35
Mon Jun 10 22:24:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=50.3 ms
Mon Jun 10 22:26:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=53.4 ms
Mon Jun 10 22:28:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=51.4 ms
Mon Jun 10 22:30:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=35.5 ms
Mon Jun 10 22:32:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=25.7 ms
Mon Jun 10 22:34:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=11.2 ms
Mon Jun 10 22:36:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=4.51 ms
Mon Jun 10 22:38:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.16 ms
Mon Jun 10 22:40:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=2.95 ms
Mon Jun 10 22:42:17 SAST 2019 64 bytes from 123.456.789.123: icmp_seq=1 ttl=248 time=3.15 ms

A speedtest done at 21:15 about gives me a speed 14Mb/s

wagner:~$ speedtest
Retrieving speedtest.net configuration...
Testing from Telkom Internet (123.456.789.123)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Bronberg Connect (Pretoria) [10.57 km]: 66.228 ms
Testing download speed................................................................................
Download: 14.52 Mbit/s
Testing upload speed....................................................................................................
Upload: 33.55 Mbit/s
wagner:~$

Speedtest done at 07:50 this morning is what I would expect all the time

wagner:~$ speedtest
Retrieving speedtest.net configuration...
Testing from Telkom Internet (123.456.789.123)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Bronberg Connect (Pretoria) [10.57 km]: 8.102 ms
Testing download speed................................................................................
Download: 156.17 Mbit/s
Testing upload speed....................................................................................................
Upload: 74.20 Mbit/s
 
Update: Today tried a speedtest at 15h00 and then at 18h15. Now the ping and speed are normal. Going to keep monitoring till late.

SpeedTest201906111452.PNG
 
Does anyone know where I can find the FUP limit before throttling for a 20/2 line?

I called Telkom and the assistant told me that he thinks it's 1800 GB but not sure and he doesn't know where to find the information.
 
And reporting a telkom vumatel fiber fault is no joke I have been struggling since Wednesday last week
 
Wow the hostility. Relax.... Realistically what answer did you want? There is zero trace routes to help any way no speedtests no investigation or anything from your side and even if the Rep was still on the forum what would be the difference compared to 10210?

Post a trace route to see where the latency is happing. If it's happening on the 2nd/3rd hop the it's likely IPC capacity related which is it very likely is. Just like other ISP's Telkom need to apply/buy more IPC capacity from Openserve and wait for Openserve to install that capacity. Just because Openserve and Telkom is the same company they have to follow the rules as silly as it sounds but that is just how it is.

So from your side test with another adsl account and see how it performs on the line. If it's fine then you know Telkom ISP and then it's basically just a waiting game and it's a pity that @ranger left Telkom because he could have actually looked into it for you and reported back.

Sad to hear that he left. Always found him very helpful.
 
Does anyone know where I can find the FUP limit before throttling for a 20/2 line?

I called Telkom and the assistant told me that he thinks it's 1800 GB but not sure and he doesn't know where to find the information.
Have you tried logging in to customerportal.telkomsa.net ? It should show you all you need to know about that.

If there is a mismatch between what you expect there (in terms of usage), and what you do see, does the IP under active sessions on the Connectivity page match your IP (e.g. from the Vumatel portal)? If convenient, check the IPs from the connection history too.

When I left, Vumatel still had no way to inform ISPs when a customer's IP changed, and something could have broken in the processes to map IPs to customers for usage management.

Of course, the backhaul link from IS to Telkom Internet could be over-subscribed now (Vumatel only did hand-over at IS, not at Teraco where we had much better presence and capacity, and for many reasons it was difficult and expensive for Telkom retail to get capacity to IS).
 
Top
Sign up to the MyBroadband newsletter
X