Vox Telecom Fatpipe

whatever_sa said:
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.
Click to expand...

Great question.

Here's the thing, we load balance our international links for best experience so while you're having an issue, the route will change mid-flight. There are a few types of congestion as well to consider:

1) Telkom exchange/infrastructure
2) Vox network
3) Peer network links
4) International links (Seacom/Wacs)

The reason we ask for a traceroute is to narrow down the path which you took through our network in order to trace down where the problem is and take it up with the 3rd party, if it's not our fault.

So to answer your question: Provide a traceroute to the destination that you're struggling with.

Give it a look tonight and let me know tomorrow.

And as others have shown, rebooting your router sometimes helps... So do that before you start tonight.

-Chris
 
cvanwie said:
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.
Click to expand...
That's two thumbs up from me! We all do appreciate you guys looking into this and providing the constant feedback until it is resolved
 
I tested now (my router was restarted). The problem remains. I got a call from vox also asking for trace routes... I just sent it through... Will wait for them to investigate. I am very happy to find that the people that I have spoken to know what they are doing (unlike afrihost).


tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 9 ms 7 ms 7 ms 41.193.121.10
4 10 ms 9 ms 7 ms 209.203.1.41
5 178 ms 175 ms 174 ms 41.193.120.89
6 190 ms 200 ms 196 ms 41.193.106.105
7 203 ms 196 ms 194 ms 41.193.106.97
8 206 ms 209 ms 208 ms 41.193.106.101
9 190 ms 220 ms 191 ms 41.193.32.198
10 183 ms 182 ms 183 ms 41.193.119.42
11 146 ms 148 ms 149 ms 72.14.220.136
12 139 ms 140 ms 143 ms 72.14.239.53
13 153 ms 154 ms 150 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.



tracert news24.co.za

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 7 ms 7 ms 7 ms 41.193.121.10
4 8 ms 6 ms 7 ms 209.203.1.41
5 108 ms 139 ms 105 ms mweb.ct1.napafrica.net [196.10.140.15]
6 113 ms 119 ms 109 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
7 110 ms 111 ms * vl12.cpt-hscore-2.optinet.net [197.84.5.254]
8 101 ms 97 ms 94 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
9 118 ms 111 ms 112 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

10 121 ms 125 ms * OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
11 145 ms 145 ms 143 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
12 150 ms 149 ms 145 ms 41-86-110-143.mweb.co.za [41.86.110.143]



tracert www.mybroadband.co.za

Tracing route to www.mybroadband.co.za [190.93.242.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 15 ms 15 ms 15 ms 41.193.121.10
4 25 ms 19 ms 18 ms 209.203.1.41
5 134 ms 130 ms 132 ms africainx.ct1.napafrica.net [196.10.140.7]
6 161 ms 162 ms * CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
7 150 ms 150 ms 147 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
8 151 ms 152 ms 154 ms 190.93.242.55

Trace complete.
 
VOX

tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 4 ms 5 ms 3 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 146 ms 234 ms 225 ms 41.193.121.37
4 159 ms 156 ms 154 ms 41.193.121.38
5 161 ms 161 ms 161 ms 196.41.29.233
6 165 ms 167 ms 155 ms 41.193.120.117
7 147 ms 158 ms 152 ms 41.193.106.105
8 133 ms 138 ms 136 ms 41.193.106.97
9 129 ms 131 ms 122 ms 41.193.106.101
10 138 ms 141 ms 137 ms 41.193.32.198
11 130 ms 134 ms 139 ms 41.193.119.42
12 157 ms 159 ms 168 ms 72.14.220.136
13 129 ms 123 ms 118 ms 72.14.239.33
14 123 ms 127 ms 123 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

tracert news24.co.za

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 3 ms 4 ms 3 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 157 ms 160 ms 152 ms 41.193.121.37
4 159 ms 152 ms 150 ms 41.193.121.38
5 129 ms 128 ms 132 ms 196.41.29.233
6 153 ms 160 ms 161 ms mweb.cinx.net.za [196.223.22.32]
7 141 ms 146 ms 149 ms te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2]
8 160 ms * 149 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
9 200 ms 143 ms 155 ms 196.28.178.66
10 171 ms 176 ms 176 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]

11 170 ms 171 ms 179 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
12 168 ms * 160 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 150 ms 152 ms 149 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

tracert www.mybroadband.co.za

Tracing route to www.mybroadband.co.za [190.93.242.55]
over a maximum of 30 hops:

1 6 ms 4 ms 4 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 225 ms 287 ms 325 ms 41.193.121.37
4 175 ms 189 ms 177 ms 41.193.121.38
5 180 ms 179 ms 173 ms 196.41.29.233
6 156 ms 158 ms 158 ms africainx.ct1.napafrica.net [196.10.140.7]
7 168 ms 167 ms 166 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za[41.84.13.228]
8 176 ms 174 ms * 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 165 ms 171 ms 166 ms 190.93.242.55

Trace complete.


Afrihost reference:

tracert www.mybroadband.co.za

Tracing route to www.mybroadband.co.za [190.93.242.55]
over a maximum of 30 hops:

1 3 ms 3 ms 5 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 34 ms 33 ms 34 ms 41.181.222.102
5 34 ms 33 ms 34 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 34 ms 34 ms 34 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 34 ms * * ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 34 ms 33 ms 33 ms 196.44.0.74
9 35 ms 38 ms 34 ms africainx.cinx.net.za [196.223.22.47]
10 44 ms 44 ms 44 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za[41.84.13.228]
11 45 ms * 43 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
12 47 ms 44 ms * 190.93.242.55
13 43 ms 42 ms 42 ms 190.93.242.55

Trace complete
 
Last edited:
Tracing route to mybroadband.co.za [190.93.242.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms unknown [192.168.1.1]
2 10 ms 11 ms 15 ms dsl-197-245-37-1.voxdsl.co.za [197.245.37.1]
3 157 ms 156 ms 156 ms 41.193.121.38
4 166 ms 163 ms 166 ms 196.41.29.233
5 171 ms 174 ms 196 ms africainx.ct1.napafrica.net [196.10.140.7]
6 186 ms 180 ms 180 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
7 193 ms 190 ms 190 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
8 191 ms 200 ms 200 ms 190.93.242.55
 
Youtube was fine during the day. However again tonight its constant buffering...

frustration-clipart.jpg
 
Last edited:
Via Vox:
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.local [192.168.0.1]
2 * * * Request timed out.
3 3 ms 2 ms 2 ms 41.193.121.9
4 26 ms 24 ms 24 ms 41.193.121.10
5 2 ms 3 ms 3 ms 209.203.1.41
6 123 ms 118 ms 118 ms mweb.ct1.napafrica.net [196.10.140.15]
7 118 ms 126 ms 122 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
8 117 ms 117 ms 121 ms vl12.cpt-hscore-2.optinet.net [197.84.5.254]
9 124 ms 132 ms 124 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
10 132 ms 135 ms 137 ms gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]
11 135 ms 132 ms 132 ms opti-cpt-n1-hosting.optinet.net [197.84.196.6]
12 124 ms 124 ms 122 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
13 130 ms 128 ms 131 ms 41-86-110-200.mweb.co.za [41.86.110.200]

Trace complete.

Via WebAfrica
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.local [192.168.0.1]
2 * * * Request timed out.
3 5 ms 5 ms 5 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
4 4 ms 5 ms 5 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 2 ms 5 ms 2 ms 196.35.115.136
6 3 ms 5 ms 5 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.13]
7 6 ms 12 ms 2 ms 168.209.2.131
8 4 ms 5 ms 5 ms mweb.cinx.net.za [196.223.22.32]
9 6 ms 5 ms 6 ms te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1]
10 3 ms 5 ms 5 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
11 5 ms 4 ms 5 ms 196.28.178.66
12 17 ms 4 ms 6 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 4 ms 5 ms 5 ms opti-cpt-n1-hosting.optinet.net [197.84.196.6]
14 8 ms 7 ms 4 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
15 5 ms 5 ms 5 ms 41-86-110-200.mweb.co.za [41.86.110.200]
 
We found a few additional issues that we have escalated to Telkom. I'll update once we get word back from them.

Thank you all for the great examples, they've helped a lot.
 
Some members said to me VOX is not a problem with Showmax. you know what, after having sh[ty experiance on Vox, i decided to use my telecom account and its perfect.
So VOX is an issue.

Besides that, I am also experiencing a total different experience to what Vox was when I initially signed up. I purchased the 100Gig special and the 300Gig special.
Maybe they realised they made a mistake and decided the only way to get rid of these accounts is to degrade their performance so the users can cancel for whatever adjustments they are making to move for future subscribers.

At the end of the day, this was not how it was.
Not Impressed at all.
 
YeaNutz said:
Some members said to me VOX is not a problem with Showmax. you know what, after having sh[ty experiance on Vox, i decided to use my telecom account and its perfect.
So VOX is an issue.

Besides that, I am also experiencing a total different experience to what Vox was when I initially signed up. I purchased the 100Gig special and the 300Gig special.
Maybe they realised they made a mistake and decided the only way to get rid of these accounts is to degrade their performance so the users can cancel for whatever adjustments they are making to move for future subscribers.

At the end of the day, this was not how it was.
Not Impressed at all.
Click to expand...

I can't blame you for being upset, but be very certain our intention is to fix things. That's why myself and netops engineer spent the entire evening with teamviewer onto machines in Cape Town, found a number of problems including congestion within the Telkom infrastructure between BRAS and exchange which is out of our control.

You are welcome to be frustrated, but please don't assume that we want to get rid of customers; that's unfair. If that was the case, we wouldn't work during family time on our own time to try to isolate problems in order to fix them.

-Chris
 
Chris, thanks for the extra effort you guys are putting in, we really do appreciate it, but you have to admit that things are getting progressively worse by the day, and especially in the evening when the load on the network seems to be higher.
 
Cannot game on this a fatpipe-lite account with uncapped bolton during the evening due to excessive latency. Not even on my normal 100gb fatpipe account.

I now switch to a different ISP for gaming in the evening. Not a big issue but it's extra effort to go through :/
 
cvanwie said:
I can't blame you for being upset, but be very certain our intention is to fix things. That's why myself and netops engineer spent the entire evening with teamviewer onto machines in Cape Town, found a number of problems including congestion within the Telkom infrastructure between BRAS and exchange which is out of our control.

You are welcome to be frustrated, but please don't assume that we want to get rid of customers; that's unfair. If that was the case, we wouldn't work during family time on our own time to try to isolate problems in order to fix them.

-Chris
Click to expand...

Hi Chris.

Thanks for the feedback and I apologise for my rudeness was frustrated and did not control myself.
I appreciate all the work you put into your brand.
Thanks for your efforts.
 
YeaNutz said:
Hi Chris.

Thanks for the feedback and I apologise for my rudeness was frustrated and did not control myself.
I appreciate all the work you put into your brand.
Thanks for your efforts.
Click to expand...

Your statements were quite valid though except for the part about them wanting to get rid of customers.
I have also noticed a clear degradation in the line quality since the launch of the specials.
But with all that being said, me experience with VOX over the years has always been perfect.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X