Vox Telecom Fatpipe

Fanus1 said:
It seems VOX Fatpipe is running at full speed again. What's the chance we ever get an explanation about what happened over Dec/Jan?
Click to expand...

Hi Fanus

We performed various infrastructure upgrades as well as we did alot of work to streamline traffic routing.

The Seacom and Wacs outages did not help progress but we cannot contribute all issues towards these failures.

We are continuing our work to further improve services.

Regards,
Voxy
 
Cancelled my Fatpipe since I am moving to Telkom LTE. To my pleasant surprise VOX left my remaining rollover data for depletion. Nice move - none of the other ISP's that offer data rollover does this.

EDIT: Spoke too soon. After a power failure I am unable to authenticate. 23GB wasted.
 
Last edited:
my fatpipe is sick again.

download a 27mb video off facebook taking more than 5 (five) minutes on a 10 (12) mb line...

ai
 
Voxtelecom is getting worse by the day if you ask me. They had amazing deals. They promise on their website unshaped experience and there was even a time that they had an image that said “no shaping” but now they shape the internet every night like clockwork.
Forget about local gaming in the evening. The ping to a Cape Town server range from 70ms - 250ms. When I switch to my Afrihost or Telkom account the ping is stable and I don't have any problems.
 
Well sometime this year I will be with Vox for 3 years now and no matter what time of day or what protocol I need it goes full speed, the exception of course when we have a cable break in JHB or international.
 
I had issues again yesterday. My modem in syncing at +10Mbps, but download speeds were < 5 Mbps. A port recreate sorted it out for me.
 
It looks like DNS is dead for me. Can't connect on my VOX account.

Code: 
C:\Users\Duan>ping [url]www.google.com[/url]

Pinging [url]www.google.com[/url] [216.58.223.36] with 32 bytes of data:
Reply from 216.58.223.36: bytes=32 time=62ms TTL=55
Reply from 216.58.223.36: bytes=32 time=58ms TTL=55
Reply from 216.58.223.36: bytes=32 time=62ms TTL=55
Reply from 216.58.223.36: bytes=32 time=63ms TTL=55

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

C:\Users\Duan>ping [url]www.google.com[/url]
Ping request could not find host [url]www.google.com[/url]. Please check the name and try a
gain.

C:\Users\Duan>

Top is WA bottom is VOX

Edit:
Aaaaand it's back
 
Last edited:
lostWinner said:
Voxtelecom is getting worse by the day if you ask me. They had amazing deals. They promise on their website unshaped experience and there was even a time that they had an image that said “no shaping” but now they shape the internet every night like clockwork.
Forget about local gaming in the evening. The ping to a Cape Town server range from 70ms - 250ms. When I switch to my Afrihost or Telkom account the ping is stable and I don't have any problems.
Click to expand...

Hi lostwinner

Please pm me you details so I can get in contact with you

Regards,
Voxy
 
Hi guys.
Over past few days, VOIP services such as Skype & Facetime haven't been working properly.. Breaking up all the time. Any ideas? Trying to talk to my girlfriend in South Korea (she's got a 100mbps fibre line, so definitely not her issue). It worked perfectly the whole of last month. Usually talk around 1pm SA time. Any ideas? I have a 10mbps line and 250gigs fatpipe account.
 
Is there something wrong with the WACS connection again? Having my League of Legends games go the slow route, adding an extra 60ms to the ping times. Pity, it's been good for a few weeks.

Tracing route to 185.40.65.154 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms router [192.168.88.1]
2 * * * Request timed out.
3 25 ms 24 ms 25 ms telkom-upload-vlan-barrack-ipc.vox.co.za [41.193.121.9]
4 26 ms 27 ms 25 ms vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.193.121.10]
5 25 ms 25 ms 26 ms vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1.41]
6 25 ms 26 ms 26 ms 41.193.120.37
7 46 ms 45 ms 47 ms 41.193.119.49
8 46 ms 45 ms 46 ms 41.193.119.74
9 234 ms 238 ms 240 ms 196.41.27.70
10 229 ms 226 ms 225 ms ldn-b5-link.telia.net [213.248.86.21]
11 234 ms 227 ms 230 ms ldn-bb3-link.telia.net [62.115.136.110]
12 237 ms 239 ms 234 ms ldn-b9-link.telia.net [62.115.117.15]
13 241 ms 252 ms 247 ms riot-ic-310578-ldn-b3.c.telia.net [62.115.54.154]
14 * * * Request timed out.
 
Oh for crying out loud VOX!! Unable to stream anything tonight!! Please enlighten me to the issues you currently have!?
 
Can someone run a PSN network test on VOX - this has been horrible - on my 20mb VDSL I get 4mbps down 700kbps up.

Doing speedtests shows no issues:




I have logged a number of tickets with Vox as this seem to only affect PS4-PSN and they have no resolution.
 
Vox:
Code: 
C:\Users\ItherNiT>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  192.168.1.1
  2     *        *        *     Request timed out.
  3    25 ms    26 ms    26 ms  41.193.164.85
  4    77 ms    76 ms    77 ms  41.193.164.86
  5    52 ms    46 ms    42 ms  41.193.164.92
  6    55 ms    60 ms    59 ms  41.193.119.101
  7    61 ms    59 ms    56 ms  41.193.119.106
  8    61 ms    54 ms    60 ms  72.14.220.136
  9    26 ms    27 ms    26 ms  72.14.239.53
 10    75 ms    72 ms    70 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\ItherNiT>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=55
Reply from 8.8.8.8: bytes=32 time=77ms TTL=55
Reply from 8.8.8.8: bytes=32 time=67ms TTL=55
Reply from 8.8.8.8: bytes=32 time=54ms TTL=55
Reply from 8.8.8.8: bytes=32 time=69ms TTL=55
Reply from 8.8.8.8: bytes=32 time=56ms TTL=55
Reply from 8.8.8.8: bytes=32 time=63ms TTL=55
Reply from 8.8.8.8: bytes=32 time=71ms TTL=55
Reply from 8.8.8.8: bytes=32 time=64ms TTL=55
Reply from 8.8.8.8: bytes=32 time=66ms TTL=55
Reply from 8.8.8.8: bytes=32 time=68ms TTL=55
Reply from 8.8.8.8: bytes=32 time=72ms TTL=55
Reply from 8.8.8.8: bytes=32 time=73ms TTL=55

Ping statistics for 8.8.8.8:
    Packets: Sent = 268, Received = 268, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 78ms, Average = 64ms

Afrihost
Code: 
C:\Users\ItherNiT>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     *        *        *     Request timed out.
  2    26 ms    26 ms    26 ms  jhb-up3.ip.adsl.co.za [169.1.5.29]
  3    27 ms    26 ms    26 ms  jhb-in2.ip.adsl.co.za [169.1.5.30]
  4    26 ms    26 ms    26 ms  jhb-up8b.ip.adsl.co.za [169.1.5.56]
  5    27 ms    26 ms    26 ms  google.jb1.napafrica.net [196.46.25.166]
  6    26 ms    25 ms    25 ms  72.14.239.117
  7    25 ms    27 ms    26 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

C:\Users\ItherNiT>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=25ms TTL=58
Reply from 8.8.8.8: bytes=32 time=25ms TTL=58
Reply from 8.8.8.8: bytes=32 time=25ms TTL=58
Reply from 8.8.8.8: bytes=32 time=25ms TTL=58

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

Latency is way lower during the day, usually <30.
Voxy any problems I should know about?
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X