Vox Telecom Fatpipe

Fatpipe data on Vuma fibre

Nick_K said:
Anybody know if I can use my Fatpipe data on Vuma fibre?
Click to expand...

Fat pipe will only work with Telkom Fibre.

On Vuma fibre , you would need to choose a Vox fibre data bundle.
 
ItherNiT said:
client portal seems broken again....

I disconnected my account, but it shows that it's still active in session logs.
Click to expand...

They are having an incident this morning... They are saying its telkom (again) and affect Cape Town area.
 
Code: 
Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

  1    3 ms     2 ms    4 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3   783 ms   582 ms   550 ms  telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
  4   739 ms   688 ms   472 ms  vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
  5   346 ms   247 ms   245 ms  vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
  6   331 ms   334 ms   366 ms  41.193.120.45
  7   685 ms   777 ms   879 ms  41.193.106.105
  8   359 ms   471 ms   602 ms  41.193.106.97
  9   540 ms     *      815 ms  41.193.106.101
 10   453 ms   606 ms   517 ms  41.193.32.198
 11   504 ms   351 ms   358 ms  41.193.119.86
 12   614 ms   706 ms   650 ms  google.jb1.napafrica.net [196.46.25.166]
 13   550 ms   579 ms   508 ms  72.14.237.239
 14   590 ms   471 ms   450 ms  jnb01s07-in-f4.1e100.net [216.58.223.4]

Could this be related to the current issue or must I start nagging Telkom to fix this?

It would make it a lot easier if Vox had a freaking network status message on their site.
 
Kwerty said:
Code: 
Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

  1    3 ms     2 ms    4 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3   783 ms   582 ms   550 ms  telkom-upload-vlan-barrack-ipc.vox.co.za [41.193
.121.9]
  4   739 ms   688 ms   472 ms  vox-upload-teraco-cpt-barrack-ipc.vox.co.za [41.
193.121.10]
  5   346 ms   247 ms   245 ms  vox-b2b-pts-barrack-ipc-int.vox.co.za [209.203.1
.41]
  6   331 ms   334 ms   366 ms  41.193.120.45
  7   685 ms   777 ms   879 ms  41.193.106.105
  8   359 ms   471 ms   602 ms  41.193.106.97
  9   540 ms     *      815 ms  41.193.106.101
 10   453 ms   606 ms   517 ms  41.193.32.198
 11   504 ms   351 ms   358 ms  41.193.119.86
 12   614 ms   706 ms   650 ms  google.jb1.napafrica.net [196.46.25.166]
 13   550 ms   579 ms   508 ms  72.14.237.239
 14   590 ms   471 ms   450 ms  jnb01s07-in-f4.1e100.net [216.58.223.4]

Could this be related to the current issue or must I start nagging Telkom to fix this?

It would make it a lot easier if Vox had a freaking network status message on their site.
Click to expand...

I'm not sure, also been having issues all week, battling to stream anything in SD, never mind HD.

Byrons-MacBook-Pro:~ byronstarkey$ traceroute www.google.com
traceroute to www.google.com (172.217.20.100), 64 hops max, 52 byte packets
1 192.168.3.1 (192.168.3.1) 2.191 ms 1.570 ms 1.397 ms
2 * * *
3 41.193.72.125 (41.193.72.125) 105.141 ms 85.211 ms 50.921 ms
4 41.193.72.126 (41.193.72.126) 22.789 ms 18.103 ms 21.845 ms
5 41.193.72.132 (41.193.72.132) 19.516 ms 19.295 ms 18.630 ms
6 41.193.119.33 (41.193.119.33) 36.100 ms 32.035 ms 30.362 ms
7 41.193.119.86 (41.193.119.86) 29.872 ms 37.839 ms 31.210 ms
8 google.jb1.napafrica.net (196.46.25.166) 29.451 ms 166.582 ms 42.599 ms
9 72.14.232.102 (72.14.232.102) 306.473 ms 199.668 ms 301.561 ms
10 209.85.253.10 (209.85.253.10) 292.683 ms 317.335 ms 294.802 ms
11 216.239.57.246 (216.239.57.246) 201.396 ms 233.950 ms
216.239.58.10 (216.239.58.10) 201.675 ms
12 216.239.57.144 (216.239.57.144) 205.094 ms
216.239.57.142 (216.239.57.142) 234.322 ms
216.239.57.144 (216.239.57.144) 222.748 ms
13 66.249.94.69 (66.249.94.69) 229.334 ms 229.691 ms 267.838 ms
14 fra02s28-in-f4.1e100.net (172.217.20.100) 238.539 ms 242.507 ms 270.027 m

perhaps Zertop can shed some light.... is it Vox or Telkom?? unfortunately i can never get his line tool to work on my system
 
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    26 ms    26 ms    26 ms  41.193.164.85
  4    77 ms    77 ms     *     41.193.164.86
  5    65 ms    64 ms    66 ms  41.193.164.92
  6    72 ms    71 ms    70 ms  google.jb1.napafrica.net [196.46.25.166]
  7    26 ms    26 ms    27 ms  72.14.239.35
  8    76 ms    75 ms    73 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.
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    24 ms  jhb-up8b.ip.adsl.co.za [169.1.5.56]
  5    25 ms    26 ms    25 ms  169-1-5-241.ip.afrihost.co.za [169.1.5.241]
  6    26 ms    25 ms    25 ms  72.14.239.53
  7    25 ms    26 ms    25 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Is there some problem in Northen region?
 
Random local ping spikes and packet loss. Wasn't like i was playing cs go competitive match or anything :mad:
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X