Vox Telecom Fatpipe

techead said:
This is another IS based ISP, problem is gone

Rock solid ping during PEAK

View attachment 240724
Click to expand...

Hi Techead -- I've asked our senior core network engineer for some assistance debugging this one, and unfortunately cannot find anything on our network causing you grief.

From one of my servers in JHB:
--- 46.23.67.190 ping statistics ---
round-trip min/avg/max/std-dev = 173.210/177.692/191.790/4.172 ms

From the core router in Cape Town:
PING 46.23.67.190 (46.23.67.190): 56 data bytes
64 bytes from 46.23.67.190: icmp_seq=0 ttl=58 time=174.809 ms
64 bytes from 46.23.67.190: icmp_seq=1 ttl=58 time=199.953 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=58 time=195.875 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=58 time=193.562 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=58 time=192.965 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=58 time=190.899 ms

I noticed you changed your destination, so I ran another test for you from my JHB server:
--- 31.3.246.202 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 176.000/179.263/188.554/4.711 ms

The network is not congested, we have no faults on our network. There's a lot of moving parts between your CPE and the destination. 30ms isn't something to be too concerned about. I was looking for that 100ms+ you complained about previously and I'm not seeing anything on our end (yes I checked the times you sent) which correlates.

There's not another stone that I can turn over.
 
cvanwie said:
The network is not congested, we have no faults on our network.
Click to expand...
Glad to be on VOX :-) Considering the 300GB deal. Just hope we don't see something else next month which will mean going through the cancellation process again - hoping you guys can improve ease of signing up, actual account activation, and the cancellation process, in relatively near future... and for heaven's sake why should I need to type my account ID every time my session expires if I don't need it to log in from the home page anyway? The general ControlPanel/interface experience leaves some to be desired
 
Last edited:
My signup was quick and painless. Created a new account, purchased two specials and everything was done in about ten minutes. The details were mailed to me within five minutes.

I chose a debit order and that was really the only variable in the process so maybe it has to do with credit card signups.
 
cvanwie said:
Hi Techead -- I've asked our senior core network engineer for some assistance debugging this one, and unfortunately cannot find anything on our network causing you grief.

From one of my servers in JHB:
--- 46.23.67.190 ping statistics ---
round-trip min/avg/max/std-dev = 173.210/177.692/191.790/4.172 ms

From the core router in Cape Town:
PING 46.23.67.190 (46.23.67.190): 56 data bytes
64 bytes from 46.23.67.190: icmp_seq=0 ttl=58 time=174.809 ms
64 bytes from 46.23.67.190: icmp_seq=1 ttl=58 time=199.953 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=58 time=195.875 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=58 time=193.562 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=58 time=192.965 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=58 time=190.899 ms

I noticed you changed your destination, so I ran another test for you from my JHB server:
--- 31.3.246.202 ping statistics ---
8 packets transmitted, 8 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 176.000/179.263/188.554/4.711 ms

The network is not congested, we have no faults on our network. There's a lot of moving parts between your CPE and the destination. 30ms isn't something to be too concerned about. I was looking for that 100ms+ you complained about previously and I'm not seeing anything on our end (yes I checked the times you sent) which correlates.

There's not another stone that I can turn over.
Click to expand...

Hi

I appreciate the time and effort taken to respond, but I am not satisfied. The below is not really acceptable in my view. The mere fact that at 18h12 your ping was rock solid stable at 179/180ms seems to indicate some kind of load issue. I'm not an engineer , but I do know enough to tell you that something is wrong, on YOUR network, otherwise why are the other two ISP Ive tested with a non-issue?

I have tested with two other ISP's (one IS based and one non-IS based) and the ping is ROCK stable... just like yours was earlier this evening I assume before the masses queued their downloads?

22h08.jpg

I would like a refund please. Do Vox offer refunds?
 
Suck it :D :p

Code: 
PING www.bbc.co.uk (46.23.67.190) 56(84) bytes of data.
64 bytes from 46.23.67.190: icmp_seq=1 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=6 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=7 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=8 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=9 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=10 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=11 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=12 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=13 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=14 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=15 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=16 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=17 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=18 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=19 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=20 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=21 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=22 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=23 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=24 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=25 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=26 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=27 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=28 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=29 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=30 ttl=53 time=156 ms
^C
--- www.bbc.co.uk ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 34057ms
rtt min/avg/max/mdev = 153.209/155.016/158.284/1.313 ms
 
DrJohnZoidberg said:
Suck it :D :p

Code: 
PING www.bbc.co.uk (46.23.67.190) 56(84) bytes of data.
64 bytes from 46.23.67.190: icmp_seq=1 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=2 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=3 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=4 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=5 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=6 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=7 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=8 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=9 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=10 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=11 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=12 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=13 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=14 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=15 ttl=53 time=155 ms
64 bytes from 46.23.67.190: icmp_seq=16 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=17 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=18 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=19 ttl=53 time=157 ms
64 bytes from 46.23.67.190: icmp_seq=20 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=21 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=22 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=23 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=24 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=25 ttl=53 time=154 ms
64 bytes from 46.23.67.190: icmp_seq=26 ttl=53 time=156 ms
64 bytes from 46.23.67.190: icmp_seq=27 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=28 ttl=53 time=158 ms
64 bytes from 46.23.67.190: icmp_seq=29 ttl=53 time=153 ms
64 bytes from 46.23.67.190: icmp_seq=30 ttl=53 time=156 ms
^C
--- www.bbc.co.uk ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 34057ms
rtt min/avg/max/mdev = 153.209/155.016/158.284/1.313 ms
Click to expand...

Perfect ping, nice

As it stands right now, the pings are looking great. It's a real yo-yo up and down
 
I was trying to game on capped. Capped is definitely not unshaped.

Switched to Webafrica and far better.
 
Once again, absolute **** internet for gaming past 10pm. Horrible ping is back. GG Vox. Pretty sure this **** is supposed to be unshaped? seems not
 
Last edited:
If 99.8% of the users have zero issues and you have issues, where is the logical place for the fault to be?
 
Soul Assassin said:
If 99.8% of the users have zero issues and you have issues, where is the logical place for the fault to be?
Click to expand...
I'd agree with you if not for the fact that i have two other 1gb accounts with other isps and they were fine last night.
 
Pansyfaust said:
I'd agree with you if not for the fact that i have two other 1gb accounts with other isps and they were fine last night.
Click to expand...

For those who know me they know I'm as transparent as possible where possible.

Due to competitors trolling forums I'm not going to show more than a tiny bit of our network cleavage. http://i.imgur.com/gBFU1cf.png

For those who don't know how to read the graph, that white space between the red and blue is a good thing! The dotted grey line is our warning level. We have automated warning systems when we reach X% and then there is a human review of the network with regards to what's going on, what the customer base is doing, what kind of traffic, what protocols are highest, trends, forecasts and such in order for us to be well aware of when we need to upgrade our network when needed as opposed to letting it look like Table Mountain. Keep in mind as you walk around the NetOps and MNOC areas of the business these graphs are monitored in real time as well.

Here's a view into the traffic profile for yesterday: http://i.imgur.com/SsMBMN4.png

I hope this helps understand us a bit better.

(And for my work colleagues reading this, yes it was approved first! :D)

Regards,
Chris
_____________________________

Chris Van Wie
Solution Architect
Vox Telecom Limited
 
Duan said:
VOX having some issues right now. Streaming on 10 mb line is horrible. Constant buffering.
Click to expand...

Local and international capacity are more than available.

Duan - contact Telkom and have them reset your port and test again.

If you have your DSL line with us, I'm fairly sure our service centre can reset the port for you as well.

What are you streaming? Netflix? Hulu? Twitch? YouTube? or something else?
 
cvanwie said:
For those who know me they know I'm as transparent as possible where possible.

Due to competitors trolling forums I'm not going to show more than a tiny bit of our network cleavage. http://i.imgur.com/gBFU1cf.png

For those who don't know how to read the graph, that white space between the red and blue is a good thing! The dotted grey line is our warning level. We have automated warning systems when we reach X% and then there is a human review of the network with regards to what's going on, what the customer base is doing, what kind of traffic, what protocols are highest, trends, forecasts and such in order for us to be well aware of when we need to upgrade our network when needed as opposed to letting it look like Table Mountain. Keep in mind as you walk around the NetOps and MNOC areas of the business these graphs are monitored in real time as well.

Here's a view into the traffic profile for yesterday: http://i.imgur.com/SsMBMN4.png

I hope this helps understand us a bit better.

(And for my work colleagues reading this, yes it was approved first! :D)

Regards,
Chris
_____________________________

Chris Van Wie
Solution Architect
Vox Telecom Limited
Click to expand...

Hi Chris

You are the man! When I was with Afrihost I tried to get them to show us something like this when things started to go wrong, which they refused. So thanks for showing us this and giving us some peace of mind! Just a question...do those graphs show the total traffic or only for a certain region?

Thanks again!
 
Some nice info there thanks. what is the outside top 10?

I was streaming hulu perfectly then all of a sudden it started buffering like crazy, this was between 7-7-30pm. can't comment on the rest of the night, i did kickoff game download at 9pm (2.7GB) and i was quick.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X