VDSL issues

[Soul Assassin]

If you can, rather use the online support chat, for me personally the online support is much better than calling.

They switched me over from 20Mbps ADSL2+ to VDSL.

 

[Glimo1]

Okay I've phoned again yesterday they created a new networking system for me. They said if my line speed isn't bumped up by today I must report a fault. And speed never got right . So I'll be logging a fault .

 

[Soul Assassin]

If you used the online support you would've been switched over to VDSL thirty minutes later.

 

[Glimo1]

Hey guys I still have a problem with line . Still not getting speeds what they said it should be . Have been busy lately . So I phoned them yesterday again. After they told me I should log a fault in the line. I logged the fault and they sms me now saying

"Dear Valued Telkom Customer, your service on has been re-tested and found to be free of defects. To confirm that your service is working, please reply to this SMS with your Telkom number followed by @W. If your service is still faulty then reply with your Telkom number followed by @F. No reply will indicate to us that the service is still faulty and we will attend to your fault as soon as possible. Sms rates apply."

So I did a speed test now from my pc got 13mb download speed and from my phone using wifi got 14.07mb download speed and 1.04mb upload speed. So is this what am I suppose to get ? Because like I mentioned they told me that numbers is not correct I should get between 16 to 19mb download speed evens on the 14mb download speed is really bad.

 

[Glimo1]

Zertop's LineTool Results
Date/Time: Tue Jul 11 16:13:25 GMT+02:00 2017

Basic Report:

Your packet loss was 0%.
Your average ping was 38ms.
Your maximum ping was 45ms.

Looking at your average ping, your line seems to be a bit dodgy. This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (eg... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice!

Detailed Report:

PING 155.239.255.250 (155.239.255.250) 56(84) bytes of data.
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=34.4 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=29.1 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=29.5 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=28.6 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=35.3 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=34.6 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=34.8 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=34.3 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=28.7 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=29.2 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=34.8 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=37.7 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=43.0 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=39.0 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=44.5 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=42.1 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=37.4 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=29.0 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=40.3 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=43.0 ms
64 bytes from 155.239.255.250: icmp_seq=21 ttl=63 time=41.7 ms
64 bytes from 155.239.255.250: icmp_seq=22 ttl=63 time=43.5 ms
64 bytes from 155.239.255.250: icmp_seq=23 ttl=63 time=44.8 ms
64 bytes from 155.239.255.250: icmp_seq=24 ttl=63 time=41.3 ms
64 bytes from 155.239.255.250: icmp_seq=25 ttl=63 time=40.2 ms
64 bytes from 155.239.255.250: icmp_seq=26 ttl=63 time=44.7 ms
64 bytes from 155.239.255.250: icmp_seq=27 ttl=63 time=44.7 ms
64 bytes from 155.239.255.250: icmp_seq=28 ttl=63 time=45.8 ms
64 bytes from 155.239.255.250: icmp_seq=29 ttl=63 time=40.6 ms
64 bytes from 155.239.255.250: icmp_seq=30 ttl=63 time=44.1 ms

--- 155.239.255.250 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29144ms
rtt min/avg/max/mdev = 28.618/38.068/45.856/5.682 ms

 

[Lishen23]

Zertop's LineTool Results
Date/Time: Tue Jul 11 16:13:25 GMT+02:00 2017

Basic Report:

[/CODE]

You really should post your line stats from your router, SNR's, Attenuations, etc. Without that it's tough for anyone here to give you accurate advice

 

[Geoff.D]

You really should post your line stats from your router, SNR's, Attenuations, etc. Without that it's tough for anyone here to give you accurate advice

Absolutely! I cannot understand why it seems so difficult for persons having line issues, to access and post their router stats.

On the surface, the latency is only just a bit worse than normal. The fault could very well be with the router itself.

 

[Glimo1]

Hey haven't checked in a while . After having a back and forth with telkom and them sending a technician. Countless tests later and some phone calls . It came to , that I can't have vdsl service because it's not available in my area. So after all that drama . I had to phone telkom for a downgrade , they asked me why i wanted to downgrade and after explaining to them , guess what apparently now they checked and told me no 10mb will be most suitable for my area .. asked them if I can't do the 12mb they told me no they recommend the 10mb line . So yes there was no fault on my router.