Vox Telecom Fatpipe

screen 1.png

Once again, issues with connecting to Apple (Akamai?) servers/services.

So tired of this. And it just seems to be completely ignored.

I am really starting to re-consider my decision to go with Vox.
 
Last edited:
Once again, issues with connecting to Apple (Akamai?) servers/services.

So tired of this. And it just seems to be completely ignored.

I am really starting to re-consider my decision to go with Vox.

yup.... my apple tv stopped working about 30 mins ago.

I am not at all ready to leave VOX though.

I have been having a lot of DNS issues lately.
 
I think something just broke :( anyone else having issues with latency right now?
Bolton and Fatpipe has high latency

Tracing route to mybroadband.co.za [190.93.240.55]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 7 ms 9 ms 41.193.3.101
3 244 ms 232 ms 224 ms 41.193.3.102
4 224 ms 198 ms 253 ms 196.41.12.0
5 233 ms 249 ms 234 ms 41.193.32.137
6 225 ms 213 ms 214 ms 41.193.32.198
7 206 ms 207 ms 216 ms 41.193.119.22
8 * * * Request timed out.
9 222 ms 218 ms 220 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
10 212 ms 226 ms 241 ms 190.93.240.55

Trace complete.

Test with an IS account working fine

Tracing route to mybroadband.co.za [190.93.242.55]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 8 ms 7 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134
]
3 8 ms 9 ms 7 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 7 ms 7 ms 7 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 9 ms 11 ms 11 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]

6 8 ms 7 ms 8 ms 168.209.1.192
7 8 ms 8 ms 8 ms mi-za-rba-gsrpe1-gi2-0-2.ip.isnet.net [168.209.8
6.122]
8 7 ms 8 ms 8 ms 197.96.148.73
9 7 ms 7 ms 7 ms 197.96.148.74
10 8 ms 8 ms 8 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-2.AINX.P2P.10G.za
[41.84.13.228]
11 37 ms 17 ms 8 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
12 8 ms 8 ms 7 ms 190.93.242.55

Trace complete.
 
Something broken on the VOX network between JHB and CPT. Any ideas?
My traceroute [v0.85]
fw (0.0.0.0) Sat Oct 10 20:54:42 2015
Keys: Help Display mode Restart statistics Order of field
s quit Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
1. fw 0.0% 37 0.3 0.4 0.3 0.7 0.0
2. ???
3. 41.193.3.101 0.0% 37 8.6 9.2 8.4 11.9 0.6
4. 41.193.3.102 2.8% 37 220.1 229.4 159.8 270.7 24.5
5. 196.41.12.0 2.8% 37 226.8 228.7 161.7 263.9 23.9
6. 41.193.32.137 0.0% 36 252.3 273.4 229.1 327.6 27.0
7. 41.193.106.102 2.8% 36 243.1 232.5 181.1 285.5 23.1
8. 41.193.106.98 0.0% 36 240.8 234.2 180.9 291.3 22.2
9. 41.193.106.106 0.0% 36 293.6 291.1 245.9 351.6 26.0
10. 41.193.120.90 5.6% 36 253.4 244.2 188.5 283.9 22.0
11. 41.193.101.182 8.3% 36 244.2 244.6 181.4 289.6 23.4
 
I'm getting astronomic pings to local game servers and to Twitter.

Whatever changes were made are either not working or making things worse.

We need traceroutes to assist with isolating where the problem is. Thanks in advance.
 
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.


By chance are you ADSL and not VDSL?
 
yup.... my apple tv stopped working about 30 mins ago.

I am not at all ready to leave VOX though.

I have been having a lot of DNS issues lately.

We suffered a network failure at 8pm which is affecting JHB, I'll update once it's recovered.

Everything north of Cape Town will be affected.
 
We suffered a network failure at 8pm which is affecting JHB, I'll update once it's recovered.

Everything north of Cape Town will be affected.

Chris, any idea about any possible P2P protocol issues in Durban?

Ta.
 
View attachment 304450

Once again, issues with connecting to Apple (Akamai?) servers/services.

So tired of this. And it just seems to be completely ignored.

I am really starting to re-consider my decision to go with Vox.

We can't fix Akamai ... That's like saying you won't buy at Spar because chickens don't eat spaghetti.

Although, I would say that the problem is due to the network failure we are experiencing right now. As soon as I get word on the resolution, I'll update.

Hang in there.
 
MATvCCf.png


8pm killed everything
 
P2P appears to be down for me in Durban.

With a failure in the network, we've lost capacity and the network is shaping to accommodate for the loss of capacity. During such an event P2P takes a beating for obvious reasons.

As soon as we recover the broken segment, I'll update.
 
Top
Sign up to the MyBroadband newsletter
X