Vox Telecom Fatpipe

Some complain about not getting 20ms pings or 900+ kbps torrent download speeds (but 500-800kbps)

To be honest those are considered nothing compared to what i had with AH and Axxess

They had terrible packet loss,ping spikes,download speeds and sometimes even browsing took forever

Since i jumped to Vox i got great streaming,decent ping,downloads of torrents are fair,browsing is fast

So im pretty much happy as could be :)

Keep in mind we do live in SA where telkom is the big boy behind all our main problems,yet we tell the isp they suck

Yes the isp's can screw things up as well!
But hey back to vox,i think Vox T is pretty decent for what i'm paying
 
An unbelievable big thank you to CVANWIE who spent 2 hours using teamviewer to help identify the problem.


The issue is somewhere upstream between telkom and VOX.

I have never experienced this level of customer support.


Thank you.
 
requiem said:
An unbelievable big thank you to CVANWIE who spent 2 hours using teamviewer to help identify the problem.


The issue is somewhere upstream between telkom and VOX.

I have never experienced this level of customer support.


Thank you.
Click to expand...

Requiem -- you are very welcome. We do listen and we try everything we can to identify where and what the problem is (as you saw first hand).

Now for the next step in this process... Escalating to Telkom. When I hear something, I'll update accordingly. Until then ... there's nothing more we can do to better the situation.

Just for others to appreciate:

What we found was that the BRAS which Requiem connects to seems to be congested and is spiking upwards of 3000ms; this equipment is the same regardless of what ISP account you use. We also found that the Telkom side of our IPC was also reporting a random spike as well. Our network team is busy escalating these issues to Telkom and hopefully we get this problem resolved soon.

Thanks for your patience requiem, greatly appreciated.

EDIT: both netops and I were very envious to watch your torrent hit 1.9MB ... She has a 4Mbps and I'm stuck at 6Mbps. Not fair!!!

Regards,
Chris
_____________________________

Chris Van Wie
Solution Architect
Vox Telecom Limited
 
Last edited:
requiem said:
Congested BRA's

That would normally be a good thing
Click to expand...

I agree completely!! Except in this case, too much is making your thing slow down! ;)


(disclaimer: "thing" refers to "throughput") :D
 
Last edited:
Hey guys. What's the policy on using multiple concurrent connections on one account? I have a 40mbps line and I want to share my data with my brother on a 2mbps line.
 
furpile said:
How much data will he use? If it's not much there are quite cheap capped packages available (seeing as he already pays for the line).
Click to expand...
He currently gets 10GB but he needs more. I see Vox has a very cheap 25GB account so that looks like a good solution and if it isn't enough I'll use it with the bolt on.

Thanks
 
Hi Chris

If I understand the last few pages of feedback correctly there are a few unresolved Telkom issues. Below is a sample traceroute which has horrible latency via Vox. The last trace via WA is quick (7ms total).

Is this one of the current Telkom issues?

Traceroute to www.news24.com (41.86.110.200), 64 hops max.

1 router.local (192.168.0.1) time=9 ms
2 *
3 41.193.121.9 (41.193.121.9) time=7 ms
4 41.193.121.10 (41.193.121.10) time=6 ms
5 209.203.1.41 (209.203.1.41) time=5 ms
6 196-10-140-145.ct1.napafrica.net (196.10.140.145) time=259 ms
7 te0-0-0-1.cpt-p-1.optinet.net (197.84.7.1) time=234 ms
8 vl12.cpt-hscore-2.optinet.net (197.84.5.254) time=216 ms
9 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) time=220 ms
10 gig5-2-cpt-opt-65-1.optinet.net (196.41.133.166) time=301 ms
11 opti-cpt-n1-hosting.optinet.net (197.84.196.6) time=293 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) time=300 ms
13 41-86-110-200.mweb.co.za (41.86.110.200) time=299 ms*
*** Traceroute at destination ***



1 router.local (192.168.0.1) 0.440 ms 0.393 ms 0.283 ms
2 * * *
3 cdsl2-ctn-vl2473-ipc.ip.isnet.net (196.38.72.194) 25.635 ms 4.898 ms 3.385 ms
4 vlan2473.cdsl2-ctn.isdsl.net (196.38.72.193) 3.817 ms 5.463 ms 3.507 ms
5 196.35.115.136 (196.35.115.136) 4.049 ms 4.484 ms 3.589 ms
6 mi-za-cpt-p7-te0-0-0-0.ip.isnet.net (168.209.6.12) 4.363 ms 4.231 ms 3.565 ms
7 168.209.2.131 (168.209.2.131) 4.106 ms 4.355 ms 2.777 ms
8 mweb.cinx.net.za (196.223.22.32) 6.417 ms 2.866 ms 3.603 ms
9 te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2) 5.025 ms 4.845 ms 6.298 ms
10 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 6.824 ms 4.758 ms 4.019 ms
11 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 6.149 ms 6.188 ms 4.349 ms
12 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 4.794 ms 7.718 ms 7.363 ms
13 opti-cpt-n1-hosting.optinet.net (197.84.196.6) 8.452 ms 5.695 ms 7.777 ms
14 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 9.550 ms 8.698 ms 8.340 ms
15 41-86-110-200.mweb.co.za (41.86.110.200) 6.726 ms 6.210 ms 8.054 ms
*** Traceroute at destination ***

Thanks again for all your effort here. It is greatly appreciated.

Regards
Grant
 
Last edited:
tnarg.retrac said:
Hi Chris

If I understand the last few pages of feedback correctly there are a few unresolved Telkom issues. Below is a sample traceroute which has horrible latency via Vox. The last trace via WA is quick (7ms total).

Is this one of the current Telkom issues?

Traceroute to www.news24.com (41.86.110.200), 64 hops max.

1 router.local (192.168.0.1) time=9 ms
2 *
3 41.193.121.9 (41.193.121.9) time=7 ms
4 41.193.121.10 (41.193.121.10) time=6 ms
5 209.203.1.41 (209.203.1.41) time=5 ms
6 196-10-140-145.ct1.napafrica.net (196.10.140.145) time=259 ms
7 te0-0-0-1.cpt-p-1.optinet.net (197.84.7.1) time=234 ms
8 vl12.cpt-hscore-2.optinet.net (197.84.5.254) time=216 ms
9 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) time=220 ms
10 gig5-2-cpt-opt-65-1.optinet.net (196.41.133.166) time=301 ms
11 opti-cpt-n1-hosting.optinet.net (197.84.196.6) time=293 ms
12 197-84-208-146.cpt.mweb.co.za (197.84.208.146) time=300 ms
13 41-86-110-200.mweb.co.za (41.86.110.200) time=299 ms*
*** Traceroute at destination ***



1 router.local (192.168.0.1) 0.440 ms 0.393 ms 0.283 ms
2 * * *
3 cdsl2-ctn-vl2473-ipc.ip.isnet.net (196.38.72.194) 25.635 ms 4.898 ms 3.385 ms
4 vlan2473.cdsl2-ctn.isdsl.net (196.38.72.193) 3.817 ms 5.463 ms 3.507 ms
5 196.35.115.136 (196.35.115.136) 4.049 ms 4.484 ms 3.589 ms
6 mi-za-cpt-p7-te0-0-0-0.ip.isnet.net (168.209.6.12) 4.363 ms 4.231 ms 3.565 ms
7 168.209.2.131 (168.209.2.131) 4.106 ms 4.355 ms 2.777 ms
8 mweb.cinx.net.za (196.223.22.32) 6.417 ms 2.866 ms 3.603 ms
9 te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2) 5.025 ms 4.845 ms 6.298 ms
10 vl11.cpt-hscore-1.optinet.net (197.84.5.238) 6.824 ms 4.758 ms 4.019 ms
11 vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 6.149 ms 6.188 ms 4.349 ms
12 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 4.794 ms 7.718 ms 7.363 ms
13 opti-cpt-n1-hosting.optinet.net (197.84.196.6) 8.452 ms 5.695 ms 7.777 ms
14 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 9.550 ms 8.698 ms 8.340 ms
15 41-86-110-200.mweb.co.za (41.86.110.200) 6.726 ms 6.210 ms 8.054 ms
*** Traceroute at destination ***

Thanks again for all your effort here. It is greatly appreciated.

Regards
Grant
Click to expand...

The issue in your trace route does not relate to the Telkom issue; it relates to a problem at napafrica cape town (off our network) the latency from that peer causes the delay to the end of that trace route. I've escalated to netops to chase up that peer.

Thanks.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X