Official Vox DSL feedback thread

Electric said:
Yeh but that is currently your only option.
Uncapped does not allow for bolt-on, only fatpipe.
Click to expand...

Yeah, i kinda figured that. Ill try it out for a bit and see how it goes. I've been very happy with VOX's service so far for the past couple months, so im sure it will stay the same.
 
Joka69 said:
Yeah, i kinda figured that. Ill try it out for a bit and see how it goes. I've been very happy with VOX's service so far for the past couple months, so im sure it will stay the same.
Click to expand...

It's a pity you missed the 150Gb special for R169.
 
Deanoblado said:
C:\WINDOWS\system32>tracert www.netflix.com

Tracing route to www.netflix.com.netflix-cluster.unostructure.com [173.208.224.4
5]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 123 ms 16 ms 98 ms 41.193.164.85
4 1224 ms 1643 ms 2242 ms 41.193.164.86
5 3163 ms 2627 ms 2686 ms 41.193.164.92
6 3143 ms 2290 ms 1220 ms 41.193.119.45
7 1484 ms 2243 ms 2971 ms 196.41.27.70
8 3709 ms 2003 ms 999 ms 196.41.27.114
9 1663 ms 2021 ms 2759 ms 40ge1-3.core1.lon2.he.net [195.66.224.21]
10 * * 910 ms 100ge1-1.core1.nyc4.he.net [72.52.92.166]
11 1919 ms 2377 ms 1737 ms 100ge7-2.core1.chi1.he.net [184.105.223.161]
12 637 ms 533 ms 479 ms 10ge3-3.core1.mci1.he.net [72.52.92.2]
13 828 ms 549 ms 700 ms 10ge1-1.core1.mci2.he.net [184.105.213.2]
14 350 ms 844 ms 1327 ms wholesale-internet-inc.10gigabitethernet1-3.core
1.mci2.he.net [216.66.78.90]
15 1077 ms 1234 ms 1115 ms lag-to-oak.edge-a.clay1.mci.us.as32097.net [69.3
0.209.163]
16 877 ms 535 ms 585 ms lag-core-b.dist-1-2.clay1.mci.us.as32097.net [20
8.110.88.3]
17 463 ms * 1193 ms 173.208.224.45

Trace complete.
Click to expand...
Ah, is that ping change normal in one hop? I'm still trying to get an explanation about that.
Chris, please comment.
 
AntiGanda said:
Your link is not correct.

Let me try again.

There are 3 pings, which vary wildly. To me, this is very unusual.
Click to expand...

AntiGanda, my link is 100% correct; that user had his port reset and the problem was resolved.

The pings were very different, that's why he chose to contact Telkom to have his port reset, which is the appropriate thing to do in this case.

I'm unsure why you fail to see that?

As posted in another forum, I think if you need further assistance, please reach out to our support department.
 
@cvanwie Hey, Has that FUP update been applied to the Uncapped accounts already? It seems like it has been applied to my account? I am on a 4 Meg Uncapped account, my usage is around 140gigs, and these are the speeds im getting (2meg) since this morning:

http://www.speedtest.net/my-result/4785690263
http://www.speedtest.net/my-result/4785682344
http://www.speedtest.net/my-result/4785677755

I also ran a tracert, and this is the result:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Beast>tracert http://www.mybroadband.co.za

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

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 76 ms 12 ms 11 ms 41.193.164.85
4 139 ms 134 ms 159 ms 41.193.164.86
5 63 ms 82 ms 87 ms 41.193.164.92
6 50 ms 13 ms 44 ms 41.193.119.45
7 96 ms 97 ms 104 ms 41.193.119.22
8 22 ms 37 ms 31 ms http://africainx.jb1.napafrica.net [196.46.25.135]
9 118 ms 119 ms 122 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
http://inx.net [41.66.181.59]
10 12 ms 12 ms 12 ms 104.20.72.110

Trace complete.
 
Joka69 said:
@cvanwie Hey, Has that FUP update been applied to the Uncapped accounts already? It seems like it has been applied to my account? I am on a 4 Meg Uncapped account, my usage is around 140gigs, and these are the speeds im getting (2meg) since this morning:

http://www.speedtest.net/my-result/4785690263
http://www.speedtest.net/my-result/4785682344
http://www.speedtest.net/my-result/4785677755

I also ran a tracert, and this is the result:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Beast>tracert http://www.mybroadband.co.za

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

1 1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 76 ms 12 ms 11 ms 41.193.164.85
4 139 ms 134 ms 159 ms 41.193.164.86
5 63 ms 82 ms 87 ms 41.193.164.92
6 50 ms 13 ms 44 ms 41.193.119.45
7 96 ms 97 ms 104 ms 41.193.119.22
8 22 ms 37 ms 31 ms http://africainx.jb1.napafrica.net [196.46.25.135]
9 118 ms 119 ms 122 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
http://inx.net [41.66.181.59]
10 12 ms 12 ms 12 ms 104.20.72.110

Trace complete.
Click to expand...

It doesn't help that the FUP for uncapped accounts leads to a 404 error.

https://www.voxtelecom.co.za/images/products/pdf/FUP1Oct.pdf
 
Code: 
Tracing route to www.rt.com [37.48.108.112]
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  3779 ms  3545 ms  2822 ms  41.193.121.9
  4     8 ms     9 ms     9 ms  41.193.121.10
  5    10 ms     9 ms     9 ms  209.203.1.41
  6    10 ms     9 ms    10 ms  41.193.120.113
  7   176 ms   176 ms   177 ms  196.41.24.174
  8   176 ms   176 ms   176 ms  ldn-b3-link.telia.net [213.248.100.161]
  9   175 ms   188 ms   193 ms  ldn-bb2-link.telia.net [62.115.140.248]
 10   181 ms   181 ms   182 ms  adm-bb4-link.telia.net [213.155.130.26]
 11   183 ms   182 ms   183 ms  adm-b3-link.telia.net [62.115.137.149]
 12   183 ms   183 ms   183 ms  leaseweb-ic-307010-adm-b3.c.telia.net [62.115.46
.86]
 13   184 ms   181 ms   182 ms  po1001.ngn-ams1-cs2-new.leaseweb.net [5.79.79.24
1]
 14   181 ms   183 ms   181 ms  37.48.108.112

Trace complete.

C:\Users\Ant>tracert www.rt.com

Tracing route to www.rt.com [37.48.108.112]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     8 ms     8 ms  41.170.71.97
  3    20 ms    10 ms    10 ms  cpt-up1.ip.adsl.co.za [169.1.5.105]
  4    11 ms    10 ms    11 ms  cpt-in1.ip.adsl.co.za [169.1.5.118]
  5    10 ms     9 ms     9 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    14 ms    10 ms    10 ms  41.164.52.40
  7    10 ms    10 ms    10 ms  172.18.32.33
  8    11 ms    10 ms    10 ms  ix-0-3-0-0.tcore1.KLT-Cape-Town.as6453.net [41.2
06.164.9]
  9   133 ms   135 ms   134 ms  Pos-channel6.core2.PV9-Lisbon.as6453.net [41.206
.164.6]
 10   169 ms   168 ms   181 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.2
31.158.1]
 11   165 ms   165 ms   169 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.
158.30]
 12   171 ms   170 ms   169 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138
.22]
 13   176 ms   174 ms   173 ms  if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.1
31.6]
 14   173 ms   174 ms   174 ms  if-10-2.thar1.HNN-Amsterdam.as6453.net [80.231.2
05.9]
 15   168 ms   169 ms   168 ms  80.231.205.22
 16   165 ms   165 ms   165 ms  po1003.ngn-ams1-cs2-new.leaseweb.net [37.48.95.2
01]
 17   168 ms   169 ms   168 ms  37.48.108.112

Trace complete.

RT working fine on Axxess, but not Vox. Streaming is poor.
 
AntiGanda said:
Code: 
Tracing route to www.rt.com [37.48.108.112]
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  3779 ms  3545 ms  2822 ms  41.193.121.9
  4     8 ms     9 ms     9 ms  41.193.121.10
  5    10 ms     9 ms     9 ms  209.203.1.41
  6    10 ms     9 ms    10 ms  41.193.120.113
  7   176 ms   176 ms   177 ms  196.41.24.174
  8   176 ms   176 ms   176 ms  ldn-b3-link.telia.net [213.248.100.161]
  9   175 ms   188 ms   193 ms  ldn-bb2-link.telia.net [62.115.140.248]
 10   181 ms   181 ms   182 ms  adm-bb4-link.telia.net [213.155.130.26]
 11   183 ms   182 ms   183 ms  adm-b3-link.telia.net [62.115.137.149]
 12   183 ms   183 ms   183 ms  leaseweb-ic-307010-adm-b3.c.telia.net [62.115.46
.86]
 13   184 ms   181 ms   182 ms  po1001.ngn-ams1-cs2-new.leaseweb.net [5.79.79.24
1]
 14   181 ms   183 ms   181 ms  37.48.108.112

Trace complete.

<snip>

RT working fine on Axxess, but not Vox. Streaming is poor.[/QUOTE]

rt.com fine here...

C:\>tracert www.rt.com

Tracing route to www.rt.com [37.48.108.112]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2    31 ms    23 ms    24 ms  41.193.121.9
  3    37 ms    23 ms    50 ms  41.193.121.10
  4    25 ms    24 ms    33 ms  209.203.1.41
  5    21 ms    21 ms    20 ms  41.193.120.113
  6   188 ms   190 ms   189 ms  196.41.24.174
  7   193 ms   188 ms   197 ms  ldn-b3-link.telia.net [213.248.100.161]
  8   202 ms   188 ms   187 ms  ldn-bb2-link.telia.net [80.91.254.18]
  9   192 ms   230 ms   193 ms  adm-bb4-link.telia.net [213.155.136.87]
 10   196 ms   195 ms   195 ms  adm-b3-link.telia.net [62.115.137.147]
 11   196 ms   201 ms   194 ms  leaseweb-ic-307009-adm-b3.c.telia.net [62.115.46.90]
 12   201 ms   196 ms   207 ms  po1003.ngn-ams1-cs2-new.leaseweb.net [37.48.95.201]
 13   194 ms   194 ms   195 ms  37.48.108.112

Trace complete.

C:\>
Click to expand...
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X