Official Vox DSL feedback thread

I asked the question because it may be affecting my ADSL or be a related symptom. The errors do not occur on WebAfrica, so something is different on the Vox network. I'm pleased you were able to reproduce it.

I'm able to replicate the issue but have no degraded experience whatsoever, suggesting the problem is something on your side.

Have you phoned Telkom to query the issue of possible exchange congestion?

I used to have your exact same problem with another ISP "A" - degraded performance not replicated with ISP "B", leading me to assume (incorrectly) that the problem lay with ISP "A". ISP "A" actually spent a lot of time with me explaining why this disparity may be found, and insisted the problem was exchange congestion based on tracerts, pathpings and so on, and recommended I report the problem to Telkom.

I did, they confirmed exchange congestion, did some magics behind the scenes, and some months later I have a beautiful, butter-smooth internet experience with numerous ISPs.

If I had ignored the advice I was given (as you seem to be), I would probably still be getting agitated and upset, with no resolution to my problem in sight, blaming the ISP for a problem that, ultimately, was not of their doing.
 
I'm able to replicate the issue but have no degraded experience whatsoever, suggesting the problem is something on your side.

Have you phoned Telkom to query the issue of possible exchange congestion?

I used to have your exact same problem with another ISP "A" - degraded performance not replicated with ISP "B", leading me to assume (incorrectly) that the problem lay with ISP "A". ISP "A" actually spent a lot of time with me explaining why this disparity may be found, and insisted the problem was exchange congestion based on tracerts, pathpings and so on, and recommended I report the problem to Telkom.

I did, they confirmed exchange congestion, did some magics behind the scenes, and some months later I have a beautiful, butter-smooth internet experience with numerous ISPs.

If I had ignored the advice I was given (as you seem to be), I would probably still be getting agitated and upset, with no resolution to my problem in sight, blaming the ISP for a problem that, ultimately, was not of their doing.
A lot of customers run speedtest and then pronounce the network fine. We have had instances where an ISP is hampering certain downloads and then saying it's not and then pointing to speed test as evidence. In our case, some people in Cape Town had trouble, whilst others did not, leading to other Cape people to come bounding to rescue Vox's reputation like a devoted puppy (down boy :D).

Things are better on our side. The 3rd hop issue is all but gone. Games still suck late in the evening, which is why I wanted to check for shaping. They still don't explain why WebAfrica shows clear results on the test but Vox doesn't. Telkom has done so many tests you would not believe it. Their exchange here is not congested either. I believe if Vox support treated things a bit more seriously when reported and quit being over defensive, they might learn more. Not one of them opened a support ticket, which leads me to believe they don't encourage fault reporting at all.
 
I checked on IS and it works there.

So something specifically happening on Vox to block it.

Did Chris not say either here or in the Fatpipe thread that they checked and could find nothing on Vox's side to block it, and it was more likely utorrent was blocking Vox?
 
Did Chris not say either here or in the Fatpipe thread that they checked and could find nothing on Vox's side to block it, and it was more likely utorrent was blocking Vox?
Why would utorrent block Vox??

I checked on Axxess and IS (Webafrica) and it worked on both.
 
Why would utorrent block Vox??

I checked on Axxess and IS (Webafrica) and it worked on both.

I doubt they set out to block Vox specifically. More likely they probably liberally banned an IP range due to attacks/abuse which happened to intersect with Vox. I'm just thumb sucking here, but I recall cvanwie saying something to the effect that they'd sent them an enquiry regarding this.
 
I doubt they set out to block Vox specifically. More likely they probably liberally banned an IP range due to attacks/abuse which happened to intersect with Vox. I'm just thumb sucking here, but I recall cvanwie saying something to the effect that they'd sent them an enquiry regarding this.

I sent another mail to uTorrent moments ago, hopefully they reply.

EDIT: also asked for NetOps to assist trouble shooting.
 
Last edited:
Luckily it is not a train smash. Everything else (incl uTorrent itself) work 100% and happy with Vox.

It is just my lazy ass that prefer to use the remote page to make changes instead of walking 5m to the server :o
 
Luckily it is not a train smash. Everything else (incl uTorrent itself) work 100% and happy with Vox.

It is just my lazy ass that prefer to use the remote page to make changes instead of walking 5m to the server :o

Why not just enable the WebUI?
 
I'll have a look at it again.

Can't remember why I couldn't get it to work last time. Think I couldn't get it to work while I was at the office. Only on local LAN.

Oh and there is the Android App that I can use while I'm in bed. Another reason I opted for that one.
 
Some funky business going on this morning...

traceroute to twitter.com (199.16.156.102), 64 hops max, 52 byte packets
1 1.0.0.1 (1.0.0.1) 3.401 ms 1.720 ms 1.713 ms
2 * * *
3 vox-upload-teraco-cpt-barrack-ipc.vox.co.za (41.193.121.10) 3090.686 ms 2288.883 ms 2559.520 ms
4 vox-b2b-pts-barrack-ipc-int.vox.co.za (209.203.1.41) 2326.207 ms 1942.311 ms 2252.840 ms
5 41.193.120.113 (41.193.120.113) 2560.364 ms 3356.151 ms 3465.343 ms
6 vox-ldn-telecity-wacs.vox.co.za (196.41.24.174) 2983.927 ms 2258.719 ms 2357.141 ms
7 ldn-b3-link.telia.net (213.248.100.161) 2661.962 ms 3090.984 ms *
8 twitter-ic-302264-ldn-b3.c.telia.net (62.115.34.10) 2979.013 ms 409.763 ms
twitter-ic-302263-ldn-b3.c.telia.net (62.115.34.6) 657.201 ms
9 ae65.atl1-er2.twttr.com (192.133.76.19) 1199.999 ms 1405.520 ms 1687.024 ms
10 199.16.156.102 (199.16.156.102) 2100.745 ms 3141.721 ms 2817.371 ms
 
Some funky business going on this morning...

That's not funky, that's horrible!

Give Telkom a call and ask them to reset your port ASAP. Once done, run another trace and let's see how it compares.
 
Hi Chris

Any chance that you guys had a look at why https://remote.utorrent.com is not working on the Vox network?

Thanks

Interesting problem!

I've sent an request to uTorrent to assist in trouble shooting this issue. I have a work around for this. Instead of going to https://remote.utorrent.com rather go to https://remote.bittorrent.com

For those geeks who want to understand how we got there:

Code:
[cvanwie@vox- ~]$ nslookup remote.utorrent.com
Server:         196.22.218.248
Address:        196.22.218.248#53

Non-authoritative answer:
remote.utorrent.com     canonical name = com-utorrent-prod-6114614.us-east-1.elb.amazonaws.com.
Name:   com-utorrent-prod-6114614.us-east-1.elb.amazonaws.com
Address: 23.21.233.214
Name:   com-utorrent-prod-6114614.us-east-1.elb.amazonaws.com
Address: 107.22.255.107
Name:   com-utorrent-prod-6114614.us-east-1.elb.amazonaws.com
Address: 107.20.191.188

Then use one of the hosts and if you try to submit the login form, you'll see it's posting to https://remote.bittorrent.com

We aren't doing anything on our side to cause this issue. We suspect that they are blocking our DSL supernet of IP addresses. We've reached out and hope to hear back from them soon.
 
Well this morning at precisely 9 am, Vox disconnected me and regardless of what I do I cannot connect.
I checked all the modem settings, rebooted the modem several times but no go.
I connect to Afrihost no problem at all.
 
My vox connection just died and had to use the Afrihost free 1gb account :confused:
is someone at Vox looking at this?
 
Top
Sign up to the MyBroadband newsletter
X