Vox Telecom Fatpipe

YouTube seems to have slowed down a lot since last month. I was getting buffer free playback at any time of the day, now videos stop half way and buffer for up to 20 seconds before playing 5 seconds and buffering another 20 seconds. Wondering if I am alone here ? Fat pipe unshaped eh ... looks like I might have to cancel 3 newly acquired vox accounts
 
Been with vox for about a year now without issues until recently... Ever since the specials i guess interwebz downloaders have joined :)... streaming etc has been rather ****ty... hope the situation improves.
 
Last edited:
Yeah, 350ms on Smite and 420ms on WoW. Locally it spikes randomly in CSGO(sometimes). I don't get it, were working perfectly fine last week.

My downloading and streaming is fine, but gaming wise I can't say the same.
 
pings down the crapper again, 200+ pings to local

57a56fb5db.png


poor form
 
I only started using my 100GB fatpipe special this month. [I am in cape town]

I created a ticket for Vox to look into my issues this morning (in progress). Thought I'd share my initial findings:

- Mweb had 2x faster ping to a European game server (BSGO).
- Battlefield 4 local game servers: all over 180ms ping...
- I did speed tests tonight - Vox shows 150 to 180ms (local server).
- I get 11ms with Axxess (used them as I had some data left with them).
- Ping to news24.co.za used to be about 11ms with mweb, its 185ms avg with Vox...

I did some speed tests now:

Vox speed tests:
1) http://www.speedtest.net/my-result/4650058686
2) http://www.speedtest.net/my-result/4650063395

Axxess speed tests:
http://www.speedtest.net/my-result/4650082169

Hopefully they can sort out whatever this is, otherwise it's back to trusty old mweb (just wish mweb could get cheaper).

LOL. those dont go in the same sentence. I Was with MWEB from day 1, bit their shaping got so bad, they forced my hand to move.
 
Streaming is fine, it's the high pings that is the bigger issue.
You are actually right. Compared pings to local BF4 servers and say a 120ms difference between VoX and another ISP. Granted it is not like this everyday.

A fix was deployed this morning for CT, so will compare tonight again.
 
You are actually right. Compared pings to local BF4 servers and say a 120ms difference between VoX and another ISP. Granted it is not like this everyday.

A fix was deployed this morning for CT, so will compare tonight again.

The fix was yesterday morning - so issues should already have been sorted last night.

Fatpipe seems a little sluggish for me today - general browsing / streaming.
 
Grab a traceroute or something to help narrow this down, it's not our network capacity ... (sneak peak, don't share... http://i.imgur.com/j2Mw100.png)

Sorry for not reporting back. Actually ran a few tests, then noticed I had a 1200ms (!) ping to Google DNS. Ran a traceroute, saw the latency was on the first hop, gave my router a good kick to the ass and things are perfect again. I'm going to write a cron job script to reboot it automatically every few days, apologies for the false report!
 
Ok So any response to my statement?
I expected the fix to reduce pings but this has not happened at all.
What's the IP of the server you're having trouble with. Maybe cvanwie can advise where/what the bottleneck is, if you can paste a traceroute
 
Grab a traceroute or something to help narrow this down, it's not our network capacity ... (sneak peak, don't share... http://i.imgur.com/j2Mw100.png)

Could you please specify what IPs/hosts we should traceroute? I ask as I seem to have the problem with absolutely everything and I dont want to be told my traceroute tests was for a service that is caused by something outside of Vox.
 
Ok So any response to my statement?
I expected the fix to reduce pings but this has not happened at all.

So did I Electric.

I just walked out of a meeting (because it was over) with the Network team. I showed them the reports/graphs/forum reports for the last few months to validate that there was some misaligned configuration between the way we do things in JHB and the way we handle CPT.

The difference was found, and changes applied to CPT to fall in line with how JHB is handled.

Please run through tests tonight and report back here please.
 
So did I Electric.

I just walked out of a meeting (because it was over) with the Network team. I showed them the reports/graphs/forum reports for the last few months to validate that there was some misaligned configuration between the way we do things in JHB and the way we handle CPT.

The difference was found, and changes applied to CPT to fall in line with how JHB is handled.

Please run through tests tonight and report back here please.

I will do that, No problem.
 
Top
Sign up to the MyBroadband newsletter
X