Vox Telecom Fatpipe

Mmmmmmm... Bolt-on, multiple heavily seeded torrents, getting 40% of max line speed. JHB.

From the network POV -- plenty of IPC at this hour, only reason for slowness would be the 10Mbps rate limiter on Bolt on. Beyond that... not sure!
 
Good morning everyone!

The change last night in Cape Town did include additional capacity.

Something I wanted to share for those interested, is that since the community has become aware of the midnight to 6am zero rated aspect of the Fatpipe, we have seen usage in that time slot start to pick up slowly. Those front ends really instill the confidence that you need I'm sure.

I'll get an update early next week as to when the dashboards will be updated to show/display accurately the difference between what's free and what isn't.

Share you experience after 6pm tonight in Cape Town, I'm expecting good reports tonight guys!

No complaints here at all... close to line speed on the free download data timeslots.

Really appreciating this.

Thanks Vox okes!!!
 
Things are amazeballs right now. Keeping fingers crossed for tonight.
 
Vox has been really awesome lately. I'm just wondering whether afrihost might not outdo them in the future once their new network is implemented... We'll see :)
 
Vox has been really awesome lately. I'm just wondering whether afrihost might not outdo them in the future once their new network is implemented... We'll see :)

With Afrihost, it will probably be fixed and work for 3 months then crash and burn again. Afrihost has NEVER worked for more than 3 months... not on their MTN network and nor on their POC "production ready" Green thing.

Vox has nothing to worry about... and has become THE disruptor at the moment.
 
By chance do you have a Zyxel router?

We don't send packet of disconnects on our network since we have a subscriber management platform that allows us to alter a customers experience on the net "mid-flight" whereas in the past, we would have to disconnect the customer in order to apply some sort of a change.

When you authenticate on our network, we do assign a session limiter which is configured here: Session-Timeout="1209600" (2 weeks)

Nope . Netgear N300, buy everyday at 9am and 9pm
 
Diablo 3 Latency seems to vary between green/orange/red at the moment. Swapped to WA which remains solid green.
In Western cape area. Is there a general problem or just me?
 
Diablo 3 Latency seems to vary between green/orange/red at the moment. Swapped to WA which remains solid green.
In Western cape area. Is there a general problem or just me?

General problem. Gets worse from 6-11. Then becomes completely stable at 11:30.
 
I'm getting astronomic pings to local game servers and to Twitter.

Whatever changes were made are either not working or making things worse.
 
Is there a price on 8Mbps ADSL line? If I go with Vox I'll be going Fatpipe Lite and would probably also have Vox manage my ADSL line. I see on your website that the Home uncapped has an 8Mbps price point (https://www.voxtelecom.co.za/home-uncapped) so presumably you have 8Mbps profiles tested and working but on the "ADSL Lines" page there are still only 2/4/10Mbps price points (plus the VDSL options) listed; no 8Mbps option is showing there.

Are you offering an 8Mbps line speed option for Fatpipe customers who want you to manage their line and if yes then what is the price?

- Julian
 
Good morning everyone!

The change last night in Cape Town did include additional capacity.

Something I wanted to share for those interested, is that since the community has become aware of the midnight to 6am zero rated aspect of the Fatpipe, we have seen usage in that time slot start to pick up slowly. Those front ends really instill the confidence that you need I'm sure.

I'll get an update early next week as to when the dashboards will be updated to show/display accurately the difference between what's free and what isn't.

Share you experience after 6pm tonight in Cape Town, I'm expecting good reports tonight guys!

Still not fixed. 100 ping started at 3pm. Looks like an avg night.
 
Ye still broken in Cape Town :(

Pinging www.google.co.za [216.58.223.3] with 32 bytes of data:
Reply from 216.58.223.3: bytes=32 time=188ms TTL=51
Reply from 216.58.223.3: bytes=32 time=173ms TTL=51
Reply from 216.58.223.3: bytes=32 time=172ms TTL=51
Reply from 216.58.223.3: bytes=32 time=176ms TTL=51

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

And here with alternative ISP

Pinging www.google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=34ms TTL=53
Reply from 216.58.223.35: bytes=32 time=33ms TTL=53
Reply from 216.58.223.35: bytes=32 time=33ms TTL=53
Reply from 216.58.223.35: bytes=32 time=32ms TTL=53

Ping statistics for 216.58.223.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 34ms, Average = 33ms
 
Last edited:
Yeah, changes don't appear to have had any effect - if anything, the degradation is happening earlier:

HTML:
 Host                                   Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. router.asus.com                      0.0%    37    0.2   0.2   0.2   0.5   0.0
 2. dsl-197-XXX-XXX-1.voxdsl.co.za       0.0%    37   15.1  14.9  14.4  18.8   0.6
 3. 41.193.121.38                        0.0%    37   94.1  93.2  68.9 121.9  12.4
 4. 196.41.29.233                        0.0%    37   90.7  93.4  65.4 122.4  13.4
 5. 41.193.120.117                       0.0%    37   87.7  93.0  70.5 120.8  12.9
 6. 41.193.106.105                       0.0%    37  100.2 103.8  79.1 132.6  12.8
 7. 41.193.106.97                        0.0%    37   99.9 104.2  78.0 138.7  12.7
 8. 41.193.106.101                       0.0%    37  107.9 109.5  83.7 146.0  13.1
 9. 41.193.32.198                        0.0%    36  110.0 112.3  82.1 149.8  13.8
10. 41.193.119.42                        0.0%    36  111.6 110.8  83.0 147.5  13.0
11. 72.14.220.136                        0.0%    36  106.9 108.9  80.3 143.9  12.2
12. 72.14.239.117                        0.0%    36  106.3 108.7  81.2 143.3  12.4
13. google-public-dns-a.google.com       0.0%    36  105.2 109.5  83.3 154.2  14.7
 
Are these "Cape Town" issues, specifically to Cape Town, or Cape Town IPC users? I ask because here in Mossel Bay my traces are fine, and playing BF4 on the PS4 this afternoon was also great!

Code:
C:\>tracert [url]www.google.com[/url]

Tracing route to [url]www.google.com[/url] [216.58.223.4]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    58 ms    23 ms    22 ms  41.193.121.9
  4    33 ms    24 ms    22 ms  41.193.121.10
  5    30 ms    29 ms    23 ms  209.203.1.41
  6    48 ms    43 ms    54 ms  41.193.120.89
  7    38 ms    46 ms    52 ms  41.193.106.105
  8    34 ms    35 ms    34 ms  41.193.106.97
  9    39 ms    39 ms    39 ms  41.193.106.101
 10    74 ms    40 ms    44 ms  41.193.32.198
 11    79 ms    42 ms    45 ms  41.193.119.42
 12    58 ms    43 ms    47 ms  72.14.220.136
 13    40 ms    43 ms    40 ms  72.14.237.239
 14    50 ms    39 ms    39 ms  jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Also just downloaded a 900MB torrent at line speed.
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X