Official Vox DSL feedback thread

cvanwie · Oct 22, 2015

Vox was mostly business, you probably heard of @lantic. Vox owned a bunch of companies such as Amvia, @lantic, Orion, Datapro, and the such. Over the last few years, we've been consolidating all the brands into just the Vox Telecom brand.

Thanks for the compliments guys!

AntiGanda · Oct 22, 2015

cvanwie said:
When sharing a problem, we need a brief description of the problem, trace routes to demonstrate the problem that you're sharing.

Well I keep sharing stuff but it keeps being the same. Kinda de-ja-vu.

Tracing route to twitter.com [199.16.156.230]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 * * * Request timed out.
4 9 ms 8 ms 8 ms 41.193.121.10
5 10 ms 9 ms 8 ms 209.203.1.41
6 10 ms 10 ms 9 ms 41.193.120.113
7 176 ms 176 ms 177 ms 196.41.24.174
8 176 ms 176 ms 177 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 176 ms 177 ms 176 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.3
3]
10 176 ms 176 ms 177 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.3
3]
11 175 ms 176 ms 176 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120
.66]
12 282 ms 282 ms 282 ms ae65.atl1-er2.twttr.com [192.133.76.19]
13 283 ms 283 ms 283 ms 199.16.156.230

Trace complete.

CS1977 · Oct 22, 2015

Cape Town broken again

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

1 <1 ms <1 ms <1 ms home.gateway.pace.net [10.0.0.2]
2 7 ms 8 ms 6 ms dsl-197-245-130-1.voxdsl.co.za [197.245.130.1]
3 204 ms 204 ms 207 ms 41.193.121.38
4 206 ms 205 ms 196 ms 196.41.29.233
5 206 ms 189 ms 180 ms africainx.ct1.napafrica.net [196.10.140.7]
6 206 ms 209 ms 214 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
7 215 ms 201 ms 199 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
8 181 ms 180 ms 180 ms 141.101.112.56

Trace complete.

Seeyou · Oct 22, 2015

Yep, latency borked again.

AntiGanda · Oct 22, 2015

Ag, so tired of this. Back to last month's episode where I get bombed out of games every 10 minutes.

justinTek · Oct 22, 2015

AntiGanda said:
Well I keep sharing stuff but it keeps being the same. Kinda de-ja-vu.

Tracing route to twitter.com [199.16.156.230]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms dsl-197-245-124-1.voxdsl.co.za [197.245.124.1]
3 * * * Request timed out.
4 9 ms 8 ms 8 ms 41.193.121.10
5 10 ms 9 ms 8 ms 209.203.1.41
6 10 ms 10 ms 9 ms 41.193.120.113
7 176 ms 176 ms 177 ms 196.41.24.174
8 176 ms 176 ms 177 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.1
3]
9 176 ms 177 ms 176 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.3
3]
10 176 ms 176 ms 177 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.3
3]
11 175 ms 176 ms 176 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120
.66]
12 282 ms 282 ms 282 ms ae65.atl1-er2.twttr.com [192.133.76.19]
13 283 ms 283 ms 283 ms 199.16.156.230

Trace complete.

you're being routed ZA->London->USA

at under 300ms ping, what more do you expect?

avr-rulez · Oct 22, 2015

CT - southern subs as a comparison
20Mbps ADSL2+ Capped account

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

1 <1 ms <1 ms <1 ms Billion.400G [192.168.1.1]
2 * * * Request timed out.
3 22 ms 12 ms 53 ms 41.193.121.9
4 27 ms 26 ms 52 ms 41.193.121.10
5 31 ms * 18 ms 209.203.1.41
6 22 ms 31 ms 19 ms africainx.ct1.napafrica.net [196.10.140.7]
7 36 ms 86 ms 55 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
8 28 ms 23 ms 46 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 67 ms 60 ms 63 ms 190.93.243.55

Trace complete.

justinTek · Oct 22, 2015

avr-rulez said:
CT - southern subs as a comparison
20Mbps ADSL2+ Capped account

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

1 <1 ms <1 ms <1 ms Billion.400G [192.168.1.1]
2 * * * Request timed out.
3 22 ms 12 ms 53 ms 41.193.121.9
4 27 ms 26 ms 52 ms 41.193.121.10
5 31 ms * 18 ms 209.203.1.41
6 22 ms 31 ms 19 ms africainx.ct1.napafrica.net [196.10.140.7]
7 36 ms 86 ms 55 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za [41.84.13.228]
8 28 ms 23 ms 46 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 67 ms 60 ms 63 ms 190.93.243.55

Trace complete.

this site uses cloudflare and you may be routed differently each time so try and maybe use something else for tests

out of curiosity, this is what i get

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

1 * * * Request timed out.
2 4 ms 4 ms 4 ms 41.193.164.85
3 4 ms 3 ms 3 ms 41.193.164.86
4 5 ms 4 ms 4 ms 41.193.164.92
5 5 ms 5 ms 5 ms 41.193.119.13
6 5 ms 5 ms 4 ms 41.193.119.30
7 5 ms 4 ms 4 ms africainx.jb1.napafrica.net [196.46.25.135]
8 4 ms 4 ms 4 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 4 ms 4 ms 4 ms 190.93.241.55

Trace complete.

AntiGanda · Oct 22, 2015

justinTek said:
you're being routed ZA->London->USA

at under 300ms ping, what more do you expect?

Are you blind? It times out on the 3rd hop. I made it red specially for you.

Earlier this afternoon it was well over 300.

justinTek · Oct 22, 2015

AntiGanda said:
Are you blind? It times out on the 3rd hop. I made it red specially for you.

Earlier this afternoon it was well over 300.

You provided one test, to one IP, hosted in the US. You provided no other information as to whether other services other than ICMP requests were timing out on one hop in the route. You must have your site but you are the one that is truly blind.

justinTek · Oct 22, 2015

My test to Twitter.com

Tracing route to twitter.com [185.45.5.32]
over a maximum of 30 hops:

1 * * * Request timed out.
2 4 ms 4 ms 4 ms 41.193.164.85
3 4 ms 4 ms 3 ms 41.193.164.86
4 5 ms 4 ms 4 ms 41.193.164.92
5 5 ms 5 ms 5 ms 41.193.119.45
6 180 ms 180 ms 180 ms 196.41.27.70
7 180 ms 180 ms 180 ms 196.41.27.114
8 180 ms 180 ms 180 ms xe-10-2-2.edge4.London1.Level3.net [195.50.120.13]
9 180 ms 180 ms 180 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.33]
10 180 ms 180 ms 180 ms ae-123-3509.edge5.London1.Level3.net [4.69.166.33]
11 180 ms 180 ms 180 ms TWITTER-INC.edge5.London1.Level3.net [195.50.120.66]
12 180 ms 180 ms 180 ms 185.45.5.32

Trace complete.

AntiGanda · Oct 22, 2015

justinTek said:
My test to Twitter.com

Justin, you are really starting to annoy me with your clone trolling. Clearly it works for you and you are happy.

I would not have done a few traceroutes if the service wasn't slow to begin with would I?

At present (11:53 PM) even YouTube is buffering like a mad goat and timing out in the same place.

cvanwie · Oct 23, 2015

As mentioned just a few times, the Cape Town latency issue is still in place and there is a change tonight at midnight to resolve the issue.

I posted a link to understanding how trace route works, it's a good read.

During a trace route, each hop is reviewed separately. If a hop doesn't respond or times out, it's not an indication of a problem.

Just to show you:

Code:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\chris.vanwie>ping 199.16.156.230

Pinging 199.16.156.230 with 32 bytes of data:
Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55
Reply from 199.16.156.230: bytes=32 time=[B]279ms[/B] TTL=55
Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55
Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55

Ping statistics for 199.16.156.230:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 276ms, Maximum = 279ms, Average = 276ms

C:\Users\chris.vanwie>

Code:

C:\Users\chris.vanwie>tracert 199.16.156.230

Tracing route to 199.16.156.230 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  172.16.72.2
  2     1 ms     1 ms     1 ms  172.16.255.10
  3     1 ms     1 ms     1 ms  196.41.212.29
  4     1 ms     1 ms     1 ms  41.193.32.133
  5     2 ms     2 ms     2 ms  41.193.32.198
  6   177 ms   177 ms   177 ms  196.41.27.70
  7   177 ms   178 ms   176 ms  ldn-b5-link.telia.net [213.248.86.21]
  8   177 ms   176 ms   182 ms  ldn-bb2-link.telia.net [62.115.138.154]
  9   177 ms   177 ms   177 ms  ldn-b3-link.telia.net [213.155.133.5]
 10   177 ms   186 ms   177 ms  twitter-ic-302264-ldn-b3.c.telia.net [62.115.34.
10]
 11   276 ms   276 ms   276 ms  ae65.atl1-er2.twttr.com [192.133.76.19]
 12   [B]284 ms   276 ms   276 ms[/B]  199.16.156.230

Trace complete.

I hope this helps you understand how to read these outputs.

EDIT: AntiGanda on a side note, I believe your third hop (the one that didn't reply) is 41.193.121.9 -- try pinging it and sharing the result. This IP is the Telkom Upload VLAN (where the latency problem was found)

AntiGanda · Oct 23, 2015

cvanwie said:
As mentioned just a few times, the Cape Town latency issue is still in place and there is a change tonight at midnight to resolve the issue.

I posted a link to understanding how trace route works, it's a good read.

During a trace route, each hop is reviewed separately. If a hop doesn't respond or times out, it's not an indication of a problem.

Just to show you:

Code:

Microsoft Windows [Version 6.3.9600] (c) 2013 Microsoft Corporation. All rights reserved. C:\Users\chris.vanwie>ping 199.16.156.230 Pinging 199.16.156.230 with 32 bytes of data: Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55 Reply from 199.16.156.230: bytes=32 time=[B]279ms[/B] TTL=55 Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55 Reply from 199.16.156.230: bytes=32 time=[B]276ms[/B] TTL=55 Ping statistics for 199.16.156.230: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 276ms, Maximum = 279ms, Average = 276ms C:\Users\chris.vanwie>

Code:

C:\Users\chris.vanwie>tracert 199.16.156.230 Tracing route to 199.16.156.230 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 172.16.72.2 2 1 ms 1 ms 1 ms 172.16.255.10 3 1 ms 1 ms 1 ms 196.41.212.29 4 1 ms 1 ms 1 ms 41.193.32.133 5 2 ms 2 ms 2 ms 41.193.32.198 6 177 ms 177 ms 177 ms 196.41.27.70 7 177 ms 178 ms 176 ms ldn-b5-link.telia.net [213.248.86.21] 8 177 ms 176 ms 182 ms ldn-bb2-link.telia.net [62.115.138.154] 9 177 ms 177 ms 177 ms ldn-b3-link.telia.net [213.155.133.5] 10 177 ms 186 ms 177 ms twitter-ic-302264-ldn-b3.c.telia.net [62.115.34. 10] 11 276 ms 276 ms 276 ms ae65.atl1-er2.twttr.com [192.133.76.19] 12 [B]284 ms 276 ms 276 ms[/B] 199.16.156.230 Trace complete.

I hope this helps you understand how to read these outputs.

EDIT: AntiGanda on a side note, I believe your third hop (the one that didn't reply) is 41.193.121.9 -- try pinging it and sharing the result. This IP is the Telkom Upload VLAN (where the latency problem was found)

If the fault is known and identified, why was it working on Wednesday but not Thursday.

Is JustinTek one of your's (hope not)?

Pinging 41.193.121.9 with 32 bytes of data:
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60

Ping statistics for 41.193.121.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms

cvanwie · Oct 23, 2015

AntiGanda said:
If the fault is known and identified, why was it working on Wednesday but not Thursday.

Is JustinTek one of your's (hope not)?

Pinging 41.193.121.9 with 32 bytes of data:
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60
Reply from 41.193.121.9: bytes=32 time=9ms TTL=60

Ping statistics for 41.193.121.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms

I believe Wednesday night Telkom put in a temp fix and reverted during investigation. Tonight midnight is when the big change comes in. Removing part of our IPC and replacing it with new technology to match the other IPC link in Cape Town. (can't give more detail than that)

I don't know who JustinTek is.

AntiGanda · Oct 23, 2015

OK.

Now Steam is not connecting at all, and BitComet is complaining about "Could not listen to Port 16315".

cvanwie · Oct 23, 2015

AntiGanda said:
OK.

Now Steam is not connecting at all, and BitComet is complaining about "Could not listen to Port 16315".

Here's what I see happening on your connection: http://i.imgur.com/gqgRYPu.png

We don't block ports on our network.

EDIT: looks like your torrents are working (51 HTTP Get flows)

AntiGanda · Oct 23, 2015

cvanwie said:
Here's what I see happening on your connection: http://i.imgur.com/gqgRYPu.png

We don't block ports on our network.

EDIT: looks like your torrents are working (51 HTTP Get flows)

Definitely odd events here. It eventually worked, but I didn't start any torrents. How recent is that snapshot?

cvanwie · Oct 23, 2015

AntiGanda said:
Definitely odd events here. It eventually worked, but I didn't start any torrents. How recent is that snapshot?

Was taken about 2 minutes before I posted.

hayted · Oct 23, 2015

Good luck for tonight Chris - hope all goes well as well as smoothly. Thanks for also keeping us well-informed and honest in the forums. Other ISP's could really take a page out of Vox's book

Join the MyBroadband community

Get started

Official Vox DSL feedback thread

Senior Member

Banned

Active Member

Expert Member

Banned

Active Member

Expert Member

Active Member

Banned

Active Member

Active Member

Banned

Senior Member

Banned

Senior Member

Banned

Senior Member

Banned

Senior Member

Well-Known Member