Official Vox DSL feedback thread

sssutututu · Nov 14, 2018

WE Want SACS access on VOX!!! Tired of gaming 200ms+ on MMOs

sssutututu · Nov 14, 2018

catman37 said:
Hi All. The Fibre Packages that Vox offer are they on a contract or month to month?

DeathStrike · Nov 14, 2018

ILoveGames said:
View attachment 578630

catman37 said:
Hi All. The Fibre Packages that Vox offer are they on a contract or month to month?

yes month to month if you pay for line installation yourself otherwise they cover it but if you cancel before 12 months then they will charge you for the installation etc.

just got mine done with them. fibre is amazing.

d.casper.b · Nov 15, 2018

Is there an issue with Vox?
Since yesterday I'm only getting 4-5Mbps download on a 20Mbps VDSL line.

From my router:

Johnatan56 · Nov 15, 2018

d.casper.b said:
Is there an issue with Vox?
Since yesterday I'm only getting 4-5Mbps download on a 20Mbps VDSL line.

From my router:
View attachment 579470

Yesterday was high latency for me in the evening, haven't tried today.

CuriouS · Nov 15, 2018

I have been having issues since last night. Downlink crawls, but uplink is fine... Where are you located? I'm in Southern Suburbs in CT.

Johnatan56 · Nov 15, 2018

CuriouS said:
I have been having issues since last night. Downlink crawls, but uplink is fine... Where are you located? I'm in Southern Suburbs in CT.

Atlantic seaboard, CT.

nerevar · Nov 15, 2018

same here since yesterday international is about 50-100 ms hight than normal

Macabre25 · Nov 18, 2018

Anyone else having high latency and packet loss around 9-10 at nights, I've been experiencing it for the past almost week or so. Changed ISP accounts and all is good but back to VOX and issues

Johnatan56 · Nov 18, 2018

Macabre25 said:
Anyone else having high latency and packet loss around 9-10 at nights, I've been experiencing it for the past almost week or so. Changed ISP accounts and all is good but back to VOX and issues

I had some packet loss 20h30-~21h30 as well, 25% says Discord, but asked in group and everyone said sounded fine while no impact in games. The packet loss currently is a bit strange. Haven't had a latency increase.

Dianysis · Nov 28, 2018

Anyone else having issues on Fatpipe over the last half hour or so?

feo · Nov 28, 2018

On fibre yeah, was a bit flaky a few mins ago.

Soul Assassin · Nov 28, 2018

Dianysis said:
Anyone else having issues on Fatpipe over the last half hour or so?

It was wonky for a couple of minutes there but it seems fine now.

Dianysis · Nov 28, 2018

Seems their network had a b**** fit.

klipdrifter · Nov 29, 2018

Anyone having latency issues tonight to Europe servers? I usually play on Battle.net euro servers but tonight its not playable at all...

Johnatan56 · Nov 29, 2018

klipdrifter said:
Anyone having latency issues tonight to Europe servers? I usually play on Battle.net euro servers but tonight its not playable at all...

In Cape Town, not having any problems.

klipdrifter · Nov 29, 2018

Nope my Telkom account doing the same... seems the problem is on my side :-( just not sure what it can be

klipdrifter · Nov 29, 2018

Tracing route to battle.net [24.105.29.30]
over a maximum of 30 hops:

1 14 ms <1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 78 ms 80 ms * telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 80 ms 79 ms * vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 83 ms 80 ms 81 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 81 ms 81 ms 81 ms 41.193.120.5
7 227 ms 220 ms 226 ms vox-ldn-telecity-wacs.vox.co.za [196.41.24.174]
8 222 ms * 224 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.13]
9 * * * Request timed out.
10 * 240 ms * 195.50.122.138
11 355 ms 359 ms * ae1-br01-eqld5.as57976.net [137.221.79.33]
12 390 ms 377 ms * xe-0-0-0-1-br01-eqny8.as57976.net [137.221.65.24]
13 310 ms 312 ms 310 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
14 * 359 ms 367 ms et-0-0-3-br02-eqla1.as57976.net [137.221.65.4]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

Anyone that can tell me if there is something wrong with the tracert info above? It timed out from hop 15 onwards...

I am in George, Western Cape, 400km from CT

Johnatan56 · Nov 29, 2018

ping bras.afrihost.com and 10.0.0.2 using -t and end both after a minute.

klipdrifter · Nov 29, 2018

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=53ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=52ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=31ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=33ms TTL=63
Reply from 155.239.255.250: bytes=32 time=34ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63

Pinging 10.0.0.2 with 32 bytes of data:
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=11ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=3ms TTL=64
Reply from 10.0.0.2: bytes=32 time=3ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=11ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=20ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=5ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64

Join the MyBroadband community

Get started

Official Vox DSL feedback thread

Well-Known Member

Well-Known Member

Expert Member

Well-Known Member

Honorary Master

Well-Known Member

Honorary Master

Well-Known Member

Well-Known Member

Honorary Master

Expert Member

Honorary Master

Honorary Master

Expert Member

Senior Member

Honorary Master

Senior Member

Senior Member

Honorary Master

Senior Member