Afrihost New Network Feedback

[Francois Marais]

Okay, you did something right. Just sorry that my business account was changed to a normal uncapped account?
But even on the normal account things looks great and must say well done AH. Just sorry for the nasty taste you left as of late.

At least the last 5 days with AH will be a little bit of joy for the amount of money we dished out.

 

[Zertop]

traceroute to google.com (216.58.223.14), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.500 ms 0.756 ms 0.941 ms
2 * * *
3 cpt-rx2.ip.adsl.co.za (169.1.5.82) 14.208 ms 14.798 ms 16.231 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 17.249 ms 18.175 ms 20.361 ms
5 41.164.52.40 (41.164.52.40) 21.614 ms 23.271 ms 24.726 ms
6 172.18.1.162 (172.18.1.162) 46.542 ms 30.045 ms 30.221 ms
7 72.14.194.206 (72.14.194.206) 40.018 ms 40.229 ms 40.286 ms
8 72.14.237.239 (72.14.237.239) 34.624 ms 35.757 ms 37.210 ms
9 jnb01s07-in-f14.1e100.net (216.58.223.14) 38.980 ms 39.456 ms 40.651 ms

traceroute to news24.com (41.86.110.143), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.481 ms 0.678 ms 0.917 ms
2 * * *
3 cpt-rx2.ip.adsl.co.za (169.1.5.82) 14.636 ms 15.221 ms 15.715 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 17.372 ms 18.338 ms 19.302 ms
5 41.164.52.40 (41.164.52.40) 21.250 ms 22.973 ms 24.445 ms
6 172.18.32.33 (172.18.32.33) 25.870 ms 9.417 ms 10.524 ms
7 mweb.cinx.net.za (196.223.22.32) 13.219 ms 17.266 ms 17.320 ms
8 te0-7-0-3.cpt-p-2.optinet.net (197.84.7.2) 39.550 ms te0-0-0-1.cpt-p-1.optinet.net (197.84.7.1) 40.421 ms 44.162 ms
9 vl12.cpt-hscore-2.optinet.net (197.84.5.254) 40.904 ms 40.962 ms vl11.cpt-hscore-1.optinet.net (197.84.5.238) 40.655 ms
10 196.28.178.66 (196.28.178.66) 44.490 ms vp-02-14.bb.ctn.c27.za.net (196.28.178.70) 47.688 ms 196.28.178.66 (196.28.178.66) 45.891 ms
11 gig5-1-cpt-opt-65-1.optinet.net (196.41.133.234) 48.637 ms 49.555 ms 49.951 ms
12 OPTI-CPT-N1-Hosting.optinet.net (197.84.196.6) 43.960 ms 32.991 ms 35.837 ms
13 197-84-208-146.cpt.mweb.co.za (197.84.208.146) 46.559 ms 32.188 ms 33.008 ms
14 41-86-110-143.mweb.co.za (41.86.110.143) 32.277 ms 33.031 ms 34.500 ms

Higher than usual in hops 4-6, but not able to replicate savage's results anymore :/

 

[craigcul]

How about some sort of tutorial for those of us that dont know about network testing and how to interpret the results we must have some network and adsl experts on this forum. I know about computers and running network cables but not much about the through put thanks from Craig.

 

[LaraC]

Higher than usual in hops 4-6, but not able to replicate savage's results anymore :/

Your routing is not the same as savage’s. It is similar to mine and I didn’t have connectivity issues either.

 

[LaraC]

How about some sort of tutorial for those of us that dont know about network testing and how to interpret the results we must have some network and adsl experts on this forum. I know about computers and running network cables but not much about the through put thanks from Craig.

An easy way to test is to use Zertop's line tool. It will test your exchange, pings, trace routes and up and download speeds.

 

[Zertop]

Your routing is not the same as savage’s. It is similar to mine and I didn’t have connectivity issues either.

Yeah true,

However it's odd. We should theoretically route the same once we've reached the IPC

Z

 

[savage]

Well pretty much everything is up to ***** right now.... Once again, can't even d/l emails...

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 4 ms 4 ms 4 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 8 ms 6 ms 6 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 7 ms 7 ms 7 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 6 ms 5 ms 5 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 7 ms 6 ms 6 ms 41.164.52.40
7 2341 ms 2397 ms 3486 ms microsoft.ct1.napafrica.net [196.10.140.47]
8 1960 ms * 3439 ms ae7-0.lon04-96cbe-1a.ntwk.msn.net [191.234.82.143]
9 2682 ms * * ae15-0.lts-96cbe-1a.ntwk.msn.net [191.234.81.155]
10 * * 3203 ms ae4-0.amb-96cbe-1b.ntwk.msn.net [204.152.141.122]
11 3493 ms * 2528 ms ae5-0.am2-96c-1b.ntwk.msn.net [191.234.81.126]
12 3648 ms * 2671 ms ae4-0.am2-96c-1a.ntwk.msn.net [207.46.43.0]
13 * * * Request timed out.
14 2988 ms 1873 ms 2968 ms 10.22.181.171
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 2420 ms 1213 ms * 191.234.225.162
19 * 3480 ms * 191.234.225.162
20 3120 ms * * 191.234.225.162
21 * * * Request timed out.
22 2887 ms 2018 ms * 191.234.225.162
23 * 3037 ms * 191.234.225.162
24 * * * Request timed out.
25 * 2618 ms 3465 ms 191.234.225.162

Trace complete.

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms vl101.wbtg-cn01-cs01.opticnetworks.corp [198.19.255.33]
2 4 ms 4 ms 4 ms 169-0-62-1.ip.afrihost.co.za [169.0.62.1]
3 7 ms 8 ms 11 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 6 ms 6 ms 6 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 7 ms 5 ms 5 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 6 ms 6 ms 6 ms 41.164.52.40
7 7 ms 7 ms 7 ms 172.18.32.33
8 11 ms 9 ms 8 ms mweb.cinx.net.za [196.223.22.32]
9 * * * Request timed out.
10 * * 3314 ms 197.84.5.238
11 3339 ms * * 196.28.178.66
12 1194 ms 3463 ms * gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
13 * * 2298 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
14 * * * Request timed out.
15 * * * Request timed out.
16 2710 ms * * 41-86-110-200.mweb.co.za [41.86.110.200]
17 * * * Request timed out.
18 * * 1324 ms 41-86-110-200.mweb.co.za [41.86.110.200]

Trace complete.

 

[kohlhtor]

Packet loss on the cape pop

 

[AfriMan]

Okay, you did something right. Just sorry that my business account was changed to a normal uncapped account?
But even on the normal account things looks great and must say well done AH. Just sorry for the nasty taste you left as of late.

At least the last 5 days with AH will be a little bit of joy for the amount of money we dished out.

Not sure how that happened. Did your product actually change in ClientZone or are you saying that it behaves more like an Uncapped product now?

 

[AfriMan]

How about some sort of tutorial for those of us that dont know about network testing and how to interpret the results we must have some network and adsl experts on this forum. I know about computers and running network cables but not much about the through put thanks from Craig.

The easiest would be to download our Network Test App.

Runs all the tests we need

https://www.afrihost.com/site/page/afrihost_network_test?src=socmed

 

[AfriMan]

Packet loss on the cape pop
View attachment 310681

Seeing as the issue is related to CDN's, it could show up on any kind of cached content.

Once we have confirmation that the issue has been resolved, I'll update everyone to test again.

 

[Johnatan56]

How about some sort of tutorial for those of us that dont know about network testing and how to interpret the results we must have some network and adsl experts on this forum. I know about computers and running network cables but not much about the through put thanks from Craig.

Well, what everyone is doing is opening command prompt and typing in: tracert URL
The tracert shows the latency to each device on the way to the URL that you are connecting to.

Usually the first hop is from your PC to the router, second is to the exchange, third is onto the Afrihost Network.
The second step in the trace route (tracert) often times out due to the new software Telkom installed on their exchange.
In order to get a direct latency report from you to the exchange, use this command in command prompt: ping bras.afrihost.com

The numbers you want: 1ms for a cable to router (hop 1) or <2ms for WiFi (depending on configuration).
<10ms for the second hop / pinging bras.afrihost.com
<40ms for the third hop but this depends on where you are located, in my case Cape Town.

Any hops after that, hopefully not over 200ms if international traffic.

How to copy paste from command prompt:
right-click > select all > enter
Now you can paste it anywhere else.
Use the [code ] code here [/ code] if posting on MyBroadband.

You can also use the Zeratul tools, Is it my line (Checks if you have congestion/fault) and one to check if you are having bad latency on the ISP side.

EDIT:
An example of a tracert from me with some comments:

Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert afrihost.com

Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  home.gateway.pace.net [192.168.1.1] < local network, this is WiFi (slightly congested due to me downloading)
  2     *        *        *     Request timed out. <telkom's new software does not allow the exchange to respond to tracerts.
  3    33 ms     9 ms    29 ms  cpt-up1.ip.adsl.co.za [169.1.5.105] < hop onto Afrihost's network.
  4    56 ms    78 ms    32 ms  cpt-up2.ip.adsl.co.za [169.1.5.106]
  5    46 ms    29 ms    36 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  6    37 ms    37 ms    24 ms  41.164.52.40
  7    76 ms    46 ms   150 ms  172.18.32.33
  8    11 ms    11 ms    12 ms  mtnns-2.cinx.net.za [196.223.22.31]
  9    13 ms    13 ms    11 ms  ^C < you can hit ctrl-c in order to end a tracert/ping in command prompt.
C:\WINDOWS\system32>

EDIT 2:
Quick way to open command prompt:
Hit the windows key and r at the same time. This will open a box called "Run". Type in: cmd
Hit enter.

EDIT 3:
Me pinging my exchange:

C:\Users\Johnatan56>ping bras.afrihost.com <note that I could also use ping ADDRESS -t which will keep the ping test going until ended with ctrl-c.

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

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

 

[savage]

AAaand - there goes google too...

WTF are we paying you for -shrugs-

 

[kohlhtor]

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=53 time=53 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=53 time=50 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=53 time=50 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=53 time=50 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=53 time=53 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=42 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=42 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=42 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=41 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=41 ms


Trace Test:

traceroute -n 197.242.144.102

**1192.168.178.1***********************************
**2Request timed out ******************************
**3Request timed out **********
***169.1.5.105*******25.562 ms 25.374 ms
**4169.1.5.118*******19.244 ms 18.71 ms**18.197 ms
**5169.1.5.128*******24.71 ms**24.394 ms 25.088 ms
**641.164.52.40******18.907 ms 19.335 ms 20.091 ms
**7172.18.32.33******26.543 ms 26.841 ms 26.496 ms
**8196.223.22.31*****20.643 ms 20.123 ms 46.378 ms
**9196.44.0.75*******22.163 ms 21.231 ms 21.17 ms**
10196.44.31.69******58.198 ms 56.113 ms 43.401 ms
11196.44.0.221******49.891 ms
***196.44.31.97******49.054 ms 49.826 ms
12196.31.220.10*****55.445 ms
***196.31.220.12*****43.333 ms 43.414 ms
13196.31.220.21*****42.409 ms 43.149 ms
***196.31.220.27*****50.047 ms
14196.31.63.202*****42.234 ms 42.658 ms 42.756 ms
15196.30.42.132*****157.5 ms**50.742 ms 62.109 ms
16197.242.144.102***51.02 ms**50.81 ms**51.219 ms


traceroute -n 8.8.8.8

**1192.168.178.1***********************************
**2Request timed out ******************************
**3169.1.5.105*******24.947 ms 25.474 ms 25.909 ms
**4169.1.5.106*******27.273 ms 25.781 ms 26.526 ms
**5169.1.5.128*******24.499 ms 25.096 ms 25.188 ms
**641.164.52.40******19.778 ms 19.779 ms 19.332 ms
**7172.18.1.162******46.545 ms 46.215 ms 48.048 ms
**872.14.194.206*****42.353 ms 40.555 ms 49.894 ms
**972.14.239.33******41.236 ms 41.418 ms
***72.14.239.117*****45.861 ms
108.8.8.8***********41.061 ms 41.612 ms 41.142 ms


DNS Test:

nslookup www.afrihost.com

Name:www.afrihost.com
Address: 41.181.185.18


nslookup www.google.com

Name:www.google.com
Address: 216.58.223.4


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

 

[zs6cey]

Seeing as the issue is related to CDN's, it could show up on any kind of cached content.

Once we have confirmation that the issue has been resolved, I'll update everyone to test again.

Any ideas when ADSL network will be running properly again. Throughput seems intermittent. .

 

[PurSpyk!!]

How much longer does Afrihost expect us to actually keep calm over these continual issues. Now I cannot send emails, wtf. This is not teething problems, this is out right incompetence.

Cant email, cant send small attachments via Skype, browsing does not work.

We spend all out time doing tracerts, what does it actually help, the network no matter what we do is never working as it should. There must be a more fundamental issue to all of this, why can 1 isp have so many issues,. and most similar issues as well.

Reminds me of the cheap car made in china. has all be bells and whistles as the fancy German car, for the first week its feels great, next minute things fall off and you realise, quality cost money, not empty promises.

 

[AirWolf]

Last connection at the office lasted a whole 5 days without disconnecting.

Edit:
11:30pm PDT = 8:30am SAST

 

[savage]

seems to also only be affecting traffic going through NapAfrica (or your peering points). So more than likely some kind of BGP issue...

Guess we as the customer, now need to do your debugging and troubleshooting for you as well.

If the peering is an issue, shut it down so that your customers can work, and troubleshoot it offline without it affecting your customers. A fairly simple process to do with the simple use of a route-map... Really now.

We're approaching 12 hours of this crap now, again!

 

[AfriMan]

snip

Great info here - thanks for taking the time

 

[AfriMan]

Any ideas when ADSL network will be running properly again. Throughput seems intermittent. .

Hopefully soon. If it's a problem with CDN's we peer with, it may take some time for the issue to be resolved, but I'll give updates as I receive them.