Vox Telecom Fatpipe

Talking of lemons Teamviewer on Vox Bolt-on appears to be down for me? Doing the same thing it did a week ago...
 
Things have gone to ****.

serious lag spikes on 41.193.3.102 - 200 ms.
 
Line seems fine but everything else not so great

Zertop's "Is it my Line" Results
Date/Time: Sun Oct 11 11:17:51 CAT 2015


Basic Report:


Your packet loss was 0%.
Your average ping was 11ms.
Your maximum ping was 41ms.

Looking at your average ping, your line seems to be running perfectly.
Looking at your maximum ping, however, it seems as though there could be a slight intermittant issue on the line. If required, please post the results to a forum post.

Detailed Report:
Code:
Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=25ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=41ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 8ms, Maximum = 41ms, Average = 11ms

C:\>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

1 1 ms 1 ms 3 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 10 ms 11 ms 41.193.3.101
4 147 ms 144 ms 145 ms 41.193.3.102
5 188 ms 168 ms 145 ms 196.41.12.0
6 141 ms 132 ms 122 ms 41.193.32.149
7 119 ms 115 ms 113 ms 41.193.32.202
8 125 ms 130 ms 130 ms 41.193.119.38
9 118 ms 112 ms 110 ms 72.14.220.136
10 11 ms 11 ms 11 ms 72.14.237.239
11 134 ms 133 ms 137 ms jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.
 
We could not access carbonite.co.za yesterday. Now we are totally off the interwebz.
 
vox vs mweb..

Code:
C:\>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms    11 ms    11 ms  41.193.3.101
  4    89 ms    82 ms    84 ms  41.193.3.102
  5   119 ms   118 ms   112 ms  196.41.12.0
  6   132 ms   125 ms   113 ms  41.193.32.149
  7   123 ms   166 ms   122 ms  41.193.32.202
  8   166 ms   168 ms   226 ms  41.193.119.38
  9    93 ms    92 ms   100 ms  72.14.220.136
 10    12 ms    12 ms    11 ms  72.14.237.239
 11   119 ms     *      106 ms  jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\>tracert www.google.co.za

Tracing route to www.google.co.za [197.80.128.34]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    10 ms    10 ms  197-80-96-161.jhb.mweb.co.za [197.80.96.161]
  4    11 ms     9 ms     9 ms  154.po-channel50.vic-ipc-1.optinet.net [197.80.96.162]
  5     9 ms     9 ms     9 ms  vl92.vic-hscore-1.optinet.net [197.80.2.1]
  6    11 ms    14 ms    14 ms  11.te0-0-0-2.vic-p-2.optinet.net [197.80.5.226]
  7     9 ms    12 ms    13 ms  197-80-7-46.jhb.mweb.co.za [197.80.7.46]
  8    13 ms    10 ms    10 ms  197-80-128-34.jhb.mweb.co.za [197.80.128.34]

Trace complete.
 
vox vs mweb..

Code:
C:\>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.3]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    10 ms    11 ms    11 ms  41.193.3.101
  4    89 ms    82 ms    84 ms  41.193.3.102
  5   119 ms   118 ms   112 ms  196.41.12.0
  6   132 ms   125 ms   113 ms  41.193.32.149
  7   123 ms   166 ms   122 ms  41.193.32.202
  8   166 ms   168 ms   226 ms  41.193.119.38
  9    93 ms    92 ms   100 ms  72.14.220.136
 10    12 ms    12 ms    11 ms  72.14.237.239
 11   119 ms     *      106 ms  jnb01s07-in-f3.1e100.net [216.58.223.3]

Trace complete.

C:\>tracert www.google.co.za

Tracing route to www.google.co.za [197.80.128.34]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    12 ms    10 ms    10 ms  197-80-96-161.jhb.mweb.co.za [197.80.96.161]
  4    11 ms     9 ms     9 ms  154.po-channel50.vic-ipc-1.optinet.net [197.80.96.162]
  5     9 ms     9 ms     9 ms  vl92.vic-hscore-1.optinet.net [197.80.2.1]
  6    11 ms    14 ms    14 ms  11.te0-0-0-2.vic-p-2.optinet.net [197.80.5.226]
  7     9 ms    12 ms    13 ms  197-80-7-46.jhb.mweb.co.za [197.80.7.46]
  8    13 ms    10 ms    10 ms  197-80-128-34.jhb.mweb.co.za [197.80.128.34]

Trace complete.
That seems to mirror what I get, apart from the Telkom hop time-out of course. Lol.
 
As of about an hour ago, there were 15 strands of fiber left to repair.

Once completed I'll update again.

For those who are experiencing problems north of Cape Town, this is the cause.
 
LoL EUW server ping is still 400+ for me :(

Cant load some sites like carbonite either
 
Ahh, cable break. Was wondering why my ping on SAIX jumped to 1883 and my download speed was an almighty 0.34 mps
 
As of about an hour ago, there were 15 strands of fiber left to repair.

Once completed I'll update again.

For those who are experiencing problems north of Cape Town, this is the cause.

What about the Durban area?
 
As of about an hour ago, there were 15 strands of fiber left to repair.

Once completed I'll update again.

For those who are experiencing problems north of Cape Town, this is the cause.

Tx for the info. I PM'ed you but this answers my one question.
 
As of about an hour ago, there were 15 strands of fiber left to repair.

Once completed I'll update again.

For those who are experiencing problems north of Cape Town, this is the cause.

Thanks for keeping us posted, do you know what happened to the fiber yesterday evening?
 
Top
Sign up to the MyBroadband newsletter
X