Official Vox DSL feedback thread

waylander said:
depth of 1 = fastpath

interleaving is an error correction system for poor signal, your signal must be okay. post line sync stats to confirm
Click to expand...
My stats haven't changed since they installed the MSAN x number of years ago:

Line Attenuation(Up/Down): 5.6/17.0 dB
Noise Margin(Up/Down): 12.2/11.0 dB
 
Weird that you are now on Fastpath with VDSL. Before they forced interleaved for error correction on 20 and 40Mbps VDSL. I'm guessing they are trying out fast path on good VDSL lines now.

Also latency has slightly dropped on Openserve even on fibre. Not exactly sure what has changed on Openserve side but something has.

As for Vox using SACS I will need to do some tests quick but that would be a very interesting development indeed.
 
waylander said:
this was never the case, had 40Mbit VDSL on fastpath many years ago, a large portion of customers on VDSL wanting higher sync rates (and a push to get them on faster line speeds by Openserve) on sub-optimal lines was the reason, and this applied to ADSL too when ASSIA's system was used
Click to expand...
You could have 40/3 on Fastpath and 45/10 on interleaved, I now have best of both.
 
cavedog said:
Weird that you are now on Fastpath with VDSL. Before they forced interleaved for error correction on 20 and 40Mbps VDSL. I'm guessing they are trying out fast path on good VDSL lines now.

Also latency has slightly dropped on Openserve even on fibre. Not exactly sure what has changed on Openserve side but something has.

As for Vox using SACS I will need to do some tests quick but that would be a very interesting development indeed.
Click to expand...

FastPath accounts for everything else but that's not going to make my ping to AWS Sao Paulo 170ms, unless Apex is lying to me that means SACS is the only answer.
 
Code: 
Pinging 177.54.152.31 with 32 bytes of data:
Reply from 177.54.152.31: bytes=32 time=169ms TTL=117
Reply from 177.54.152.31: bytes=32 time=168ms TTL=117
Reply from 177.54.152.31: bytes=32 time=168ms TTL=117
Reply from 177.54.152.31: bytes=32 time=168ms TTL=117

Ping statistics for 177.54.152.31:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 169ms, Average = 168ms

The one Apex Legends server in Sao Paulo but it's not AWS it's Maxihost, if I ping the AWS one the ping is 280ms.
 
Hmm, wonder if I can have my vdsl line changed to fastpath from interleave? Should that be on both up and down as mine is on up only. Not sure what the stats should be. I am about a block away from the exchange.
Would love to get better latency.

​
SNR Margin11.9 dB22.1 dB
Line Attenuation17.8 dB40.0 dB
Path ModeInterleavedFastPath
Interleave Depth8271
Data Rate20479 kbps2048 kbps
Max Rate60012 kbps8997 kbps
Power13.6 dbm0.4 dbm
 
Rohan said:
Hmm, wonder if I can have my vdsl line changed to fastpath from interleave? Should that be on both up and down as mine is on up only. Not sure what the stats should be. I am about a block away from the exchange.
Would love to get better latency.

​
SNR Margin11.9 dB22.1 dB
Line Attenuation17.8 dB40.0 dB
Path ModeInterleavedFastPath
Interleave Depth8271
Data Rate20479 kbps2048 kbps
Max Rate60012 kbps8997 kbps
Power13.6 dbm0.4 dbm
Click to expand...

I'm definitely interleaved on both. Ideally I'd love to have Fast Path Download and Interleaved Upload, since I do enjoy the 5120 kpbs Upload I get on my 20Mb VDSL.
 
I don't want to rub it in but it feels so nice having the faster speeds and FastPath too, I genuinely can feel the difference, that's why I posted originally, I was just minding my own business and I was like why is everything loading so fast. I hopped onto Apex solo the other night and played on the Sao Paulo server at something like 168ms and it felt amazing, this is after playing on Belgium at over 200ms two or so weeks back, London was 220ms.
 
Soul Assassin said:
I don't want to rub it in but it feels so nice having the faster speeds and FastPath too, I genuinely can feel the difference, that's why I posted originally, I was just minding my own business and I was like why is everything loading so fast. I hopped onto Apex solo the other night and played on the Sao Paulo server at something like 168ms and it felt amazing, this is after playing on Belgium at over 200ms two or so weeks back, London was 220ms.
Click to expand...

I don't know how you get that because I tried and I still see pretty high latency.

I still can't get over the horror show that is 230ms in League of Legends EU West.

Vox fatpipe is almost a distant memory for me now even on Openserve fibre it's just not that good.

Unknown ISPs like infogro has better routing and latency than them.
 
cavedog said:
I don't know how you get that because I tried and I still see pretty high latency.

I still can't get over the horror show that is 230ms in League of Legends EU West.

Vox fatpipe is almost a distant memory for me now even on Openserve fibre it's just not that good.

Unknown ISPs like infogro has better routing and latency than them.
Click to expand...
It's just that one server in Sao Paulo that gives me that low ping, I don't know what is up with that.
 
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 35ms, Average = 33ms

Why must you be like this.

Edit: This is better:

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 9ms, Average = 8ms
 
Last edited:
This is the best I've ever seen:

Pinging lon.hosted.co.za [167.99.194.90] with 32 bytes of data:
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53

Ping statistics for 167.99.194.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 166ms, Average = 166ms
 
  • Love
Reactions: Yuu
Soul Assassin said:
This is the best I've ever seen:

Pinging lon.hosted.co.za [167.99.194.90] with 32 bytes of data:
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53
Reply from 167.99.194.90: bytes=32 time=166ms TTL=53

Ping statistics for 167.99.194.90:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 166ms, Maximum = 166ms, Average = 166ms
Click to expand...

Very nice for VDSL. That is how it's actually supposed to be when a line is working well.
 
  • Like
Reactions: Yuu
My downloads left little to desire lately although my line show that is running @12479 but the actual performance don't seem close to that.

Thanks VOX for the 1300gb you loaded for free onto my account. Much appreciated...
 
mika1000 said:
My downloads left little to desire lately although my line show that is running @12479 but the actual performance don't seem close to that.

Thanks VOX for the 1300gb you loaded for free onto my account. Much appreciated...
Click to expand...

Same this side. The 400GB base cap now shows 1300GB base cap and roll over data at 3.7TB :unsure:
 
  • Like
Reactions: Yuu
So I'm on the Vox 1TB Black Friday Promo account right now, and my usage is physically impossible. It claims that a couple of days ago I downloaded 70GBs in the space of about 5 hours. That's excluding upload of about 1GB.

I'm on 20Mb VDSL, so even if I was downloading at full speed (which I wasn't, the variance in the graph proves that.), the max I could possibly have downloaded in that time would have been 45GBs. I've checked my session history, and only my VDSL line number shows up so it's not that someone else is using my account either.

I expect that I must have used about 35GBs in that time, but it's almost like they doubled it to make my data run out faster.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X