Official Vox DSL feedback thread

ok so update on my DSL in sandton , the line basically died last night during peak , then worked again but just barely. with going up to 200ms and then just dropping, my average ping loss for the last 24hours - 2-3% lost, 35ms ave.(17ms low and 3928ms high) ( a whole week like this) is just totally unacceptable ...not for R999 p/m...any good suggestions (im on 10mb dsl and 1tb fat pipe) - we have fibre in area
 
ok so update on my DSL in sandton , the line basically died last night during peak , then worked again but just barely. with going up to 200ms and then just dropping, my average ping loss for the last 24hours - 2-3% lost, 35ms ave.(17ms low and 3928ms high) ( a whole week like this) is just totally unacceptable ...not for R999 p/m...any good suggestions (im on 10mb dsl and 1tb fat pipe) - we have fibre in area

Switch to fiber? for R999/month you could basically get 100/10 uncapped
 
wan port unplugged according to router , but everything same as always. Faulty ONT? Down the road everything working on Afrihost Openserve...
Openserve , Durban , Westville
 
wan port unplugged according to router , but everything same as always. Faulty ONT? Down the road everything working on Afrihost Openserve...
Openserve , Durban , Westville

Check if Lan 1 is flashing on ONT. If not check if ONT is on with yellow power and pon light. If it's on check the cable between the ONT and router. If it's fine connect a pc or laptop with ethernet directly to the ONT on Lan 1 and check if it works.
 
Vox starting crap again.
Anyone else?

Pinging bras.afrihost.com shows 16 ms.
This apparently helps pinpoint congestion at exchange. So that seems fine.

Speedtests have 90+ ms ping.
 
Vox starting crap again.
Anyone else?

Pinging bras.afrihost.com shows 16 ms.
This apparently helps pinpoint congestion at exchange. So that seems fine.

Speedtests have 90+ ms ping.
16ms is very high, should be under 8ms on ADSL, under 3ms on fiber.
Think cap is about 12ms if interleaved, past that usually points to an issue in regards to the copper.

EDIT:
On WiFi, so that's probably why the 25ms outlier:
C:\WINDOWS\system32>ping bras.afrihost.com -t

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=5ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63
Reply from 155.239.255.250: bytes=32 time=2ms TTL=63
Reply from 155.239.255.250: bytes=32 time=1ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=4ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63
Reply from 155.239.255.250: bytes=32 time=3ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 25ms, Average = 4ms
 
16ms is very high, should be under 8ms on ADSL, under 3ms on fiber.
Think cap is about 12ms if interleaved, past that usually points to an issue in regards to the copper.

EDIT:
On WiFi, so that's probably why the 25ms outlier:
Oh ok. Was under impression that under 20ms is good.

On 10mbps adsl (interleaved).

The the ping to bras.afrihost.com is around 16 ms all the time. Been like that the past couple of years since my exchange was upgraded (was congested before).

E.g. Earlier today when all was hunky dory, it also showed 16 ms to bras.afrihost.com. Speedtests showed 23 ms.
At the moment, bras.afrihost.com still shows 16 ms but speedtests are getting progressively worse - currently at 130+ ms again.

Previously when the exchange was congested, bras.afrihost.com was at 100+ ms.

Noticed this for the first time on Thursday night. Is it possible that the Sandton issue could be affecting us in JHB South?
 
Oh ok. Was under impression that under 20ms is good.

On 10mbps adsl (interleaved).

The the ping to bras.afrihost.com is around 16 ms all the time. Been like that the past couple of years since my exchange was upgraded (was congested before).

E.g. Earlier today when all was hunky dory, it also showed 16 ms to bras.afrihost.com. Speedtests showed 23 ms.
At the moment, bras.afrihost.com still shows 16 ms but speedtests are getting progressively worse - currently at 130+ ms again.

Previously when the exchange was congested, bras.afrihost.com was at 100+ ms.

Noticed this for the first time on Thursday night. Is it possible that the Sandton issue could be affecting us in JHB South?
Could be because you are on interleaved if stable 16ms, a couple of ms could maybe be added if they are using a DSLAM in-between due to distance.
Not saying that it couldn't be the network that is messing up for you btw, I am in a completely different region than you, so could be Vox playing up again.

Within CT, no issue:
8027346421.png
 
Could be because you are on interleaved if stable 16ms, a couple of ms could maybe be added if they are using a DSLAM in-between due to distance.
Not saying that it couldn't be the network that is messing up for you btw, I am in a completely different region than you, so could be Vox playing up again.

Within CT, no issue:
8027346421.png
From Zertop's line tool.

Don't know if still reliable as was updated last in 2015...
c61ddcd17ae34bbe7c398e7351e747b3.jpg
 
From Zertop's line tool.

Don't know if still reliable as was updated last in 2015...
c61ddcd17ae34bbe7c398e7351e747b3.jpg
Nah, it's reliable, nothing has changed since then, it just pings a set of IP on the network.
Same thing as running it yourself, just easier for non tech-savvy people as it doesn't involve using command prompt/it's easier as one click.

It's most likely a Vox issue, as you've stated, just want to check if line just in case. Easiest ISP test is still go and use a capped account of a friend and see how it performs after about 45 minutes of being switched to.
 
Well it did look like Vox JHB ipc might be congested at peak times. Yester day saw me getting 130ms to their own jhb test server and struggled to get to 45Mbps on a 200Mbps Openserve line

Using a Infogro account and pings are soooooo good
 
Also having issues with Vox
Since Friday.
This morning ping to local server 540ms. No other devices running.
Eastern Cape area.
 
Well I have just gone down again Vox. Anyone else? Having a second backup account is becoming mandatory with Vox.
 
Also down.. 2nd time this week. Had to sign up with another ISP so I could get my work done.
 
Top
Sign up to the MyBroadband newsletter
X