Official Vox DSL feedback thread

Same problems - browsing dog slow, high latency to EU servers in Rocket League last night, twitch barely working at all.

Think this might be my last month with VOX
 
This is from Cape Town. Looks like the local routing tables are messed up "again"

Tracing route to www.goggle.com [45.33.35.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 * * * Request timed out.
3 20 ms 20 ms 20 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 19 ms 19 ms 20 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 20 ms 19 ms 19 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 20 ms 19 ms 19 ms 41.193.120.37
7 160 ms 159 ms 161 ms vox-ldn-telecity-wacs.vox.co.za [196.41.24.174]
8 160 ms 159 ms 161 ms 40ge1-3.core1.lon2.he.net [195.66.224.21]
9 225 ms 225 ms 225 ms 100ge1-1.core1.nyc4.he.net [72.52.92.166]
10 288 ms 298 ms 288 ms 100ge15-2.core1.sjc2.he.net [184.105.81.213]
11 287 ms 297 ms 299 ms 10ge3-2.core3.fmt2.he.net [184.105.222.13]
12 * * * Request timed out.
13 287 ms 288 ms 287 ms li985-30.members.linode.com [45.33.35.30]

Trace complete.

Now look when WWW is not inserted.

Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 * * * Request timed out.
3 20 ms 19 ms 19 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 27 ms 19 ms 26 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 20 ms 19 ms 19 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 20 ms 19 ms 19 ms 41.193.120.45
7 32 ms 31 ms 31 ms 41.193.106.105
8 31 ms 30 ms 30 ms 41.193.106.97
9 36 ms 37 ms 35 ms 41.193.106.101
10 36 ms 36 ms 36 ms 41.193.32.198
11 35 ms 35 ms 36 ms 41.193.119.86
12 36 ms 36 ms 35 ms google.jb1.napafrica.net [196.46.25.166]
13 36 ms 35 ms 36 ms 72.14.237.239
14 35 ms 35 ms 35 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.

Whats goggle.com?
 
This is from Cape Town. Looks like the local routing tables are messed up "again"

Tracing route to www.goggle.com [45.33.35.30]
over a maximum of 30 hops:


Now look when WWW is not inserted.

Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:
.

Those are not the same website.
 
Whats goggle.com?

:D the monster hiding under your bed. :D

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 * * * Request timed out.
3 28 ms 26 ms 27 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 36 ms 39 ms 38 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 23 ms 24 ms 21 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 23 ms 20 ms 25 ms 41.193.120.45
7 50 ms 51 ms 50 ms 41.193.106.105
8 41 ms 36 ms 32 ms 41.193.106.97
9 47 ms 54 ms 49 ms 41.193.106.101
10 54 ms 56 ms 56 ms 41.193.32.198
11 49 ms 52 ms 52 ms 41.193.119.86
12 48 ms 49 ms 48 ms google.jb1.napafrica.net [196.46.25.166]
13 41 ms 40 ms 39 ms 72.14.237.239
14 49 ms 51 ms 52 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.


Tracing route to google.com [216.58.223.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.home [192.168.1.1]
2 * * * Request timed out.
3 34 ms 35 ms 35 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 38 ms 37 ms 39 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 26 ms 26 ms 26 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 20 ms 23 ms 25 ms 41.193.120.45
7 45 ms 50 ms 51 ms 41.193.106.105
8 38 ms 36 ms 40 ms 41.193.106.97
9 43 ms 44 ms 47 ms 41.193.106.101
10 55 ms 52 ms 53 ms 41.193.32.198
11 42 ms 44 ms 45 ms 41.193.119.86
12 42 ms 38 ms 40 ms google.jb1.napafrica.net [196.46.25.166]
13 52 ms 54 ms 52 ms 72.14.237.239
14 39 ms 40 ms 39 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.
 
Last edited:
I am seriously disappointed with the service that I am receiving. Have been going back and forth now for weeks trying to sort out the issues on the line. Telkom moved me to another port and now are unable to connect.

I phoned and spoke to a support person informing me that the reason that I am unable to connect is that there are too much noise on the line, even though the line is syncing at 20Mbps!

I've had it now!

VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Enable
Traffic Type: PTM Mode
Link Uptime: 0 day: 0 hour: 1 minute
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 2.068 Mbps 20.536 Mbps
Actual Net Data Rate: 2.048 Mbps 20.479 Mbps
Trellis Coding: ON ON
SNR Margin: 6.2 dB 6.8 dB
Actual Delay: 0 ms 5 ms
Transmit Power: 5.5 dBm 14.5 dBm
Receive Power: -11.7 dBm -12.3 dBm
Actual INP: 0.0 symbols 1.0 symbols
Total Attenuation: 17.2 dB 26.8 dB
Attainable Net Data Rate: 2.509 Mbps 24.094 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 12.4 63.4 N/A N/A 26.8 78.1 102.3
Signal Attenuation(dB): 12.4 61.9 N/A N/A 26.8 N/A N/A
SNR Margin(dB): 6.3 6.2 N/A N/A 6.8 N/A N/A
Transmit Power(dBm): 0.6 3.8 N/A N/A 14.5 N/A N/A
 
Opening MYBB with vox is like swimming through treacle.

What the hell vox - fix your ****ing service.
 
SNR Margin: 6.2 dB 6.8 dB
Total Attenuation: 17.2 dB 26.8 dB

That is hardly a VOX issue. You can go to another ISP, but the results will be the same. See below.

Heres is my table of comparisons
SNR:

6dB or below is very bad and will experience no synch or intermittent synch problems
7dB-10dB is fair but does not leave much room for variances in conditions
11dB-20dB is good with little or no sync problems
20dB-28dB is excellent
29dB or above is outstanding
 
That sounds like a easy cop out instead of fixing your issues, my downstream SNR is 6.1dB and I have zero issues.

Telkom requires a minimum of 6.0dB, if you go below that their system will lower your line sync to achieve 6.0dB, so in theory you should be fine. Your issue seems to be elsewhere.
 
That sounds like a easy cop out instead of fixing your issues, my downstream SNR is 6.1dB and I have zero issues.

Telkom requires a minimum of 6.0dB, if you go below that their system will lower your line sync to achieve 6.0dB, so in theory you should be fine. Your issue seems to be elsewhere.

That is exactly what my frustration is. If the line is unstable (as it has been), I can understand, but not being able to connect at all does not compute and seems like a cop out.
 
SNR Margin: 6.2 dB 6.8 dB
Total Attenuation: 17.2 dB 26.8 dB

That is hardly a VOX issue. You can go to another ISP, but the results will be the same. See below.

Heres is my table of comparisons
SNR:

6dB or below is very bad and will experience no synch or intermittent synch problems
7dB-10dB is fair but does not leave much room for variances in conditions
11dB-20dB is good with little or no sync problems
20dB-28dB is excellent
29dB or above is outstanding

At the moment it is 9.7 db, which is considered fair according to the table, and still not able to connect.


============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
G.Vector: Enable
Traffic Type: PTM Mode
Link Uptime: 0 day: 0 hour: 1 minute
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 2.068 Mbps 20.546 Mbps
Actual Net Data Rate: 2.048 Mbps 20.476 Mbps
Trellis Coding: ON ON
SNR Margin: 9.7 dB 9.1 dB
Actual Delay: 0 ms 5 ms
Transmit Power: 6.3 dBm 14.0 dBm
Receive Power: -10.6 dBm -11.2 dBm
Actual INP: 0.0 symbols 2.0 symbols
Total Attenuation: 16.9 dB 25.3 dB
Attainable Net Data Rate: 3.636 Mbps 29.705 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 11.1 59.8 62.1 N/A 25.1 73.8 102.3
Signal Attenuation(dB): 11.1 58.7 N/A N/A 25.1 74.4 N/A
SNR Margin(dB): 9.6 9.7 N/A N/A 9.1 9.2 N/A
Transmit Power(dBm): 0.4 4.9 -128.0 N/A 13.8 1.7 N/A
 
You mentioned Telkom moved you to another port at which point you couldn't connect anymore, you sure they didn't mess something up somewhere?

I suggest you turn off your modem, call Telkom and ask them to recreate/reset the port and after 30 minutes turn the modem back on.
 
You mentioned Telkom moved you to another port at which point you couldn't connect anymore, you sure they didn't mess something up somewhere?

I suggest you turn off your modem, call Telkom and ask them to recreate/reset the port and after 30 minutes turn the modem back on.

Been there, done that.
 
I don't have an account with another ISP.

That means you can't really blame Vox now can you. You did zero troubleshooting and decided to just cancel.

Go to the Afrihost site and signup for the free 1GB, it takes 2 minutes, if that account connects and works you can blame Vox, if it doesn't work you blame Telkom.
 
That means you can't really blame Vox now can you. You did zero troubleshooting and decided to just cancel.

Go to the Afrihost site and signup for the free 1GB, it takes 2 minutes, if that account connects and works you can blame Vox, if it doesn't work you blame Telkom.

Why the hell should I be running around doing troubleshooting getting other accounts to verify if the problem is with Vox. If I am not mistaken, that is exactly why I am paying Vox. I am the customer, and they are the supplier rendering the service.

Telkom was here tested the line and everything was ok. The technician, 10 times more helpful than the Vox consultant phoned Vox. There was an authentication issue, not picked up by Vox when I phoned them.

Next point, I have been battling for weeks getting Vox to understand that 20Mbs ADSL and 20Mbs VDSL is not the same thing and that in order to get proper VDSL it has to be moved to an appropriate port at the exchange. The Telkom technician verified that this was now doen for the first time, hence the following information on the router: "Mode: VDSL2 Annex B", which I queried numerous Vox consultants on, and they could not resolve the issue.

let me guess, you work for Vox!?
 
Why the hell should I be running around doing troubleshooting getting other accounts to verify if the problem is with Vox. If I am not mistaken, that is exactly why I am paying Vox. I am the customer, and they are the supplier rendering the service.

Telkom was here tested the line and everything was ok. The technician, 10 times more helpful than the Vox consultant phoned Vox. There was an authentication issue, not picked up by Vox when I phoned them.

Next point, I have been battling for weeks getting Vox to understand that 20Mbs ADSL and 20Mbs VDSL is not the same thing and that in order to get proper VDSL it has to be moved to an appropriate port at the exchange. The Telkom technician verified that this was now doen for the first time, hence the following information on the router: "Mode: VDSL2 Annex B", which I queried numerous Vox consultants on, and they could not resolve the issue.

let me guess, you work for Vox!?

tl;dr

I don't work for Vox.

If you can't be bothered to just do the most basic troubleshooting on your own just to confirm the issue, which will take you less than 5 minutes, have fun at your new ISP.

If I ever move from Vox, Afrihost are doing good things lately.
 
tl;dr

I don't work for Vox.

If you can't be bothered to just do the most basic troubleshooting on your own just to confirm the issue, which will take you less than 5 minutes, have fun at your new ISP.

If I ever move from Vox, Afrihost are doing good things lately.

So humour me, and tell me what exactly is your definition from basic troubleshooting?

Let's start with where I have been for the last 4 weeks, not just now, unable to connect to VDSL and only ADSL. Let me guess, you are going to tell me it is the same thing.
 
Top
Sign up to the MyBroadband newsletter
X