Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Just a quick one guys, busy running through some prep work for the migration tomorrow.
We need to see a bit more load from the South though - can you guys load up some HD YouTube vids?

YouTube ain't pretty on my end.
CPT, Century City, 20mbps
Throughput erratic. Drops to 10mbps. Lots of dropped frames.
youtube-test1.png
Hope it improves on the production network.
 
PING bras.afrihost.com (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=97.367 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=58.375 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=28.016 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=8.480 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=19.118 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=162.894 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=186.402 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=168.755 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=197.363 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=135.074 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=24.184 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=140.339 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=67.193 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=189.626 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=102.828 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=33.400 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=33.688 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=33.020 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=167.750 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=42.886 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=16.116 ms
^C
--- bras.afrihost.com ping statistics ---
21 packets transmitted, 21 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.480/91.089/197.363/66.091 ms
 
PING 188.165.200.200 (188.165.200.200): 56 data bytes
64 bytes from 188.165.200.200: icmp_seq=0 ttl=45 time=248.430 ms
64 bytes from 188.165.200.200: icmp_seq=1 ttl=45 time=278.129 ms
64 bytes from 188.165.200.200: icmp_seq=2 ttl=45 time=313.112 ms
64 bytes from 188.165.200.200: icmp_seq=3 ttl=45 time=242.714 ms
64 bytes from 188.165.200.200: icmp_seq=4 ttl=45 time=213.663 ms
64 bytes from 188.165.200.200: icmp_seq=5 ttl=45 time=191.889 ms
64 bytes from 188.165.200.200: icmp_seq=6 ttl=45 time=236.860 ms
64 bytes from 188.165.200.200: icmp_seq=7 ttl=45 time=245.153 ms
64 bytes from 188.165.200.200: icmp_seq=8 ttl=45 time=330.036 ms
64 bytes from 188.165.200.200: icmp_seq=9 ttl=45 time=499.634 ms
64 bytes from 188.165.200.200: icmp_seq=10 ttl=45 time=553.505 ms
64 bytes from 188.165.200.200: icmp_seq=11 ttl=45 time=473.308 ms
64 bytes from 188.165.200.200: icmp_seq=12 ttl=45 time=459.183 ms
64 bytes from 188.165.200.200: icmp_seq=13 ttl=45 time=472.237 ms
Request timeout for icmp_seq 14
64 bytes from 188.165.200.200: icmp_seq=15 ttl=45 time=236.962 ms
64 bytes from 188.165.200.200: icmp_seq=16 ttl=45 time=296.528 ms
64 bytes from 188.165.200.200: icmp_seq=17 ttl=45 time=393.961 ms
64 bytes from 188.165.200.200: icmp_seq=18 ttl=45 time=525.812 ms
^C
--- 188.165.200.200 ping statistics ---
20 packets transmitted, 18 packets received, 10.0% packet loss
round-trip min/avg/max/stddev = 191.889/345.062/553.505/117.862 ms


not looking that good and 10% packet loss
 
Last edited:
Okay, that is enough YouTube for me today. :p

Best wishes for tomorrow. :)
 
Not at all happy here in Somerset West Tracert from 22:27

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 582 ms 579 ms 565 ms cpt-rx2.net.afrihost.co.za [169.1.5.82]
4 523 ms 389 ms 418 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
5 406 ms 388 ms 489 ms 41.164.52.40
6 581 ms * 311 ms 172.18.32.33
7 506 ms * 512 ms mtnns-2.cinx.net.za [196.223.22.31]
8 515 ms * 600 ms 196.44.0.75
9 * 512 ms 496 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 593 ms * 544 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
11 547 ms * 548 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
12 450 ms 528 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
13 581 ms * 485 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
Just a quick one guys, busy running through some prep work for the migration tomorrow.
We need to see a bit more load from the South though - can you guys load up some HD YouTube vids?

Looking good

1d9005ead8.jpg

Good luck with the migration tomorrow ;)
 
I think a lot of your queries have been addressed here/ via PM - but as I've said, he is massively busy.
You're welcome to follow up with him via mail, but realistically I'd expect a reply after the migration.

I actually expect a reply from Gian as it involves certain topivs that have not been addressed in PMs or in the thread.


My boss runs 2 companies (etail and retail) and he receives hundreds of mails a day, but when he sees a complaint he addresses it as a priority because he knows that good service and happy clients are what keeps the coffers filled. (but yeah, I guess I can't expect that kind of service from Gian)


Regarding the tests I was supposed to do, forgot entirely due to a family emergency, if I get another off day sometime this month I will do the comparison tests.
 
Last edited:
New network!

Well, here's a traceroute from PE on the new network ... looks like fun!

traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 * * *
2 cpt-tx2.net.afrihost.co.za (169.1.5.81) 29.659 ms 30.729 ms 32.955 ms
3 cpt-rx2.net.afrihost.co.za (169.1.5.82) 43.316 ms 43.768 ms 45.471 ms
4 cpt-net1.net.afrihost.co.za (169.1.5.128) 46.377 ms 47.877 ms 50.315 ms
5 41.164.52.40 (41.164.52.40) 52.493 ms 53.719 ms 55.432 ms
6 172.18.1.162 (172.18.1.162) 71.933 ms 45.386 ms 46.788 ms
7 72.14.194.206 (72.14.194.206) 53.391 ms 53.145 ms 53.359 ms
8 72.14.239.33 (72.14.239.33) 55.095 ms 72.14.239.117 (72.14.239.117) 55.817 ms 72.14.239.33 (72.14.239.33) 55.859 ms
9 google-public-dns-a.google.com (8.8.8.8) 54.137 ms 54.403 ms 54.608 ms
 
That definitely not good. Can you also run the full trace when this happens so we can see where the latency occurs?

Yep, Lag spikes is still sporadic tried some Diablo III last night between 6:30 and 9 pm, with latencey running between ~200 and ~700 ..... definitely not ideal when one gets ganked by mobs on a glass canon Witch Doctor :(

5:30 am this morning - the latency spikes still present :wtf:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Igor III>ping bras.afrihost.com -t

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=603ms TTL=63
Reply from 155.239.255.250: bytes=32 time=573ms TTL=63
Reply from 155.239.255.250: bytes=32 time=716ms TTL=63
Reply from 155.239.255.250: bytes=32 time=639ms TTL=63
Reply from 155.239.255.250: bytes=32 time=649ms TTL=63
Reply from 155.239.255.250: bytes=32 time=583ms TTL=63
Reply from 155.239.255.250: bytes=32 time=515ms TTL=63
Reply from 155.239.255.250: bytes=32 time=722ms TTL=63
Reply from 155.239.255.250: bytes=32 time=660ms TTL=63
Reply from 155.239.255.250: bytes=32 time=614ms TTL=63
Reply from 155.239.255.250: bytes=32 time=669ms TTL=63
Reply from 155.239.255.250: bytes=32 time=566ms TTL=63
Reply from 155.239.255.250: bytes=32 time=648ms TTL=63
Reply from 155.239.255.250: bytes=32 time=690ms TTL=63
Reply from 155.239.255.250: bytes=32 time=643ms TTL=63
Reply from 155.239.255.250: bytes=32 time=672ms TTL=63
Reply from 155.239.255.250: bytes=32 time=636ms TTL=63
Reply from 155.239.255.250: bytes=32 time=684ms TTL=63
Reply from 155.239.255.250: bytes=32 time=621ms TTL=63
Reply from 155.239.255.250: bytes=32 time=571ms TTL=63
Reply from 155.239.255.250: bytes=32 time=640ms TTL=63
Reply from 155.239.255.250: bytes=32 time=617ms TTL=63
Reply from 155.239.255.250: bytes=32 time=682ms TTL=63
Reply from 155.239.255.250: bytes=32 time=121ms TTL=63
Reply from 155.239.255.250: bytes=32 time=149ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=62ms TTL=63
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=45ms TTL=63
Reply from 155.239.255.250: bytes=32 time=18ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=54ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=28ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=27ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=78ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=35ms TTL=63
Reply from 155.239.255.250: bytes=32 time=36ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=48ms TTL=63
Reply from 155.239.255.250: bytes=32 time=38ms TTL=63
Reply from 155.239.255.250: bytes=32 time=29ms TTL=63
Reply from 155.239.255.250: bytes=32 time=37ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=19ms TTL=63
Reply from 155.239.255.250: bytes=32 time=30ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=12ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 70, Received = 70, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 722ms, Average = 227ms
Control-C
^C
C:\Users\Igor III>tracert bras.afrihost.com

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

1 <1 ms <1 ms 10 ms 192.168.1.1
2 15 ms 26 ms 19 ms 155.239.255.250

Trace complete.

C:\Users\Igor III>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms 19 ms 5 ms 192.168.1.1
2 * * * Request timed out.
3 17 ms 13 ms 16 ms jhb-up3.net.afrihost.co.za [169.1.5.29]
4 59 ms 17 ms 13 ms jhb-in1.net.afrihost.co.za [169.1.5.42]
5 59 ms 33 ms 12 ms jhb-net1.net.afrihost.co.za [169.1.5.52]
6 88 ms 13 ms 24 ms 41.169.57.216
7 20 ms 19 ms 36 ms 41.160.2.69
8 16 ms 14 ms 25 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 25 ms 39 ms 24 ms 196.43.39.166
10 65 ms 41 ms 19 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 80 ms 40 ms 17 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 72 ms 22 ms 20 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Igor III>tracert bras.afrihost.com

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

1 3 ms 5 ms <1 ms 192.168.1.1
2 13 ms 23 ms 11 ms 155.239.255.250

Trace complete.

C:\Users\Igor III>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 39 ms 15 ms 15 ms jhb-up3.net.afrihost.co.za [169.1.5.29]
4 19 ms 22 ms 22 ms jhb-in1.net.afrihost.co.za [169.1.5.42]
5 19 ms 13 ms 12 ms jhb-net1.net.afrihost.co.za [169.1.5.52]
6 13 ms 37 ms 39 ms 41.169.57.216
7 55 ms 38 ms 25 ms 41.160.2.69
8 15 ms 14 ms 13 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 40 ms 18 ms 13 ms 196.43.39.166
10 27 ms 25 ms 16 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 36 ms 27 ms 18 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 28 ms 22 ms 33 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.


Don't want to sound full of cr@p, but ............. with the 23rd getting closer and with the "miracle" network still being in "test phase" I am not sure if my disappointment with the "latency" experienced on my Afrihost account is premature and if I should stick it out for another month (reminds me of the classic song from The Clash - Should I stay or should I go :D)
 
Last edited:
traceroute to 188.165.200.200 (188.165.200.200), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.533 ms 0.305 ms 0.422 ms
2 * * *
3 cpt-rx2.net.afrihost.co.za (169.1.5.82) 363.659 ms 475.807 ms 421.276 ms
4 cpt-net1.net.afrihost.co.za (169.1.5.128) 520.160 ms 386.825 ms 459.830 ms
5 41.164.52.40 (41.164.52.40) 127.357 ms 37.879 ms 21.098 ms
6 172.18.32.33 (172.18.32.33) 21.684 ms 17.549 ms 16.644 ms
7 ix-0-3-0-0.tcore1.klt-cape-town.as6453.net (41.206.164.9) 47.235 ms 33.946 ms 13.901 ms
8 if-1-0-0-5.core2.pv9-lisbon.as6453.net (195.219.214.53) 164.261 ms
if-1-0-0-3.core2.pv9-lisbon.as6453.net (195.219.214.34) 205.349 ms 341.235 ms
9 if-0-0-0-2000.tcore1.pv9-lisbon.as6453.net (80.231.158.1) 332.197 ms 341.479 ms 363.343 ms
10 if-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30) 316.750 ms 275.837 ms 319.556 ms
11 if-19-2.tcore2.l78-london.as6453.net (80.231.138.22) 343.279 ms 346.511 ms 275.151 ms
12 if-15-2.tcore2.ldn-london.as6453.net (80.231.131.118) 251.295 ms 319.702 ms 257.620 ms
13 ldn-1-a9.uk.eu (213.251.130.109) 279.252 ms 246.437 ms 297.403 ms
14 rbx-g1-a9.fr.eu (91.121.128.86) 311.663 ms 230.110 ms 204.063 ms
15 vss-3b-6k.routers.ovh.net (213.186.32.254) 193.021 ms 190.254 ms 176.753 ms
16 ns345728.ip-188-165-200.eu (188.165.200.200) 210.153 ms 240.996 ms 260.246 ms

PING bras.afrihost.com (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=97.367 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=58.375 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=28.016 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=8.480 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=19.118 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=162.894 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=186.402 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=168.755 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=197.363 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=135.074 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=24.184 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=140.339 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=67.193 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=189.626 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=102.828 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=33.400 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=33.688 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=33.020 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=167.750 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=42.886 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=16.116 ms
^C
--- bras.afrihost.com ping statistics ---
21 packets transmitted, 21 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.480/91.089/197.363/66.091 ms

PING 188.165.200.200 (188.165.200.200): 56 data bytes
64 bytes from 188.165.200.200: icmp_seq=0 ttl=45 time=248.430 ms
64 bytes from 188.165.200.200: icmp_seq=1 ttl=45 time=278.129 ms
64 bytes from 188.165.200.200: icmp_seq=2 ttl=45 time=313.112 ms
64 bytes from 188.165.200.200: icmp_seq=3 ttl=45 time=242.714 ms
64 bytes from 188.165.200.200: icmp_seq=4 ttl=45 time=213.663 ms
64 bytes from 188.165.200.200: icmp_seq=5 ttl=45 time=191.889 ms
64 bytes from 188.165.200.200: icmp_seq=6 ttl=45 time=236.860 ms
64 bytes from 188.165.200.200: icmp_seq=7 ttl=45 time=245.153 ms
64 bytes from 188.165.200.200: icmp_seq=8 ttl=45 time=330.036 ms
64 bytes from 188.165.200.200: icmp_seq=9 ttl=45 time=499.634 ms
64 bytes from 188.165.200.200: icmp_seq=10 ttl=45 time=553.505 ms
64 bytes from 188.165.200.200: icmp_seq=11 ttl=45 time=473.308 ms
64 bytes from 188.165.200.200: icmp_seq=12 ttl=45 time=459.183 ms
64 bytes from 188.165.200.200: icmp_seq=13 ttl=45 time=472.237 ms
Request timeout for icmp_seq 14
64 bytes from 188.165.200.200: icmp_seq=15 ttl=45 time=236.962 ms
64 bytes from 188.165.200.200: icmp_seq=16 ttl=45 time=296.528 ms
64 bytes from 188.165.200.200: icmp_seq=17 ttl=45 time=393.961 ms
64 bytes from 188.165.200.200: icmp_seq=18 ttl=45 time=525.812 ms
^C
--- 188.165.200.200 ping statistics ---
20 packets transmitted, 18 packets received, 10.0% packet loss
round-trip min/avg/max/stddev = 191.889/345.062/553.505/117.862 ms


not looking that good and 10% packet loss

Thanks so much for posting some tests!
The results are showing very high and intermittent latency to your exchange though. If you've seen these results on both your old account and the new one, chances are that's where the issue is.

You can confirm 100% by using a backup ISP or the Telkom guest account (although not always accurate) to confirm.
 
traceroute to 188.165.200.200 (188.165.200.200), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 0.533 ms 0.305 ms 0.422 ms
2 * * *
3 cpt-rx2.net.afrihost.co.za (169.1.5.82) 363.659 ms 475.807 ms 421.276 ms
4 cpt-net1.net.afrihost.co.za (169.1.5.128) 520.160 ms 386.825 ms 459.830 ms
5 41.164.52.40 (41.164.52.40) 127.357 ms 37.879 ms 21.098 ms
6 172.18.32.33 (172.18.32.33) 21.684 ms 17.549 ms 16.644 ms
7 ix-0-3-0-0.tcore1.klt-cape-town.as6453.net (41.206.164.9) 47.235 ms 33.946 ms 13.901 ms
8 if-1-0-0-5.core2.pv9-lisbon.as6453.net (195.219.214.53) 164.261 ms
if-1-0-0-3.core2.pv9-lisbon.as6453.net (195.219.214.34) 205.349 ms 341.235 ms
9 if-0-0-0-2000.tcore1.pv9-lisbon.as6453.net (80.231.158.1) 332.197 ms 341.479 ms 363.343 ms
10 if-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30) 316.750 ms 275.837 ms 319.556 ms
11 if-19-2.tcore2.l78-london.as6453.net (80.231.138.22) 343.279 ms 346.511 ms 275.151 ms
12 if-15-2.tcore2.ldn-london.as6453.net (80.231.131.118) 251.295 ms 319.702 ms 257.620 ms
13 ldn-1-a9.uk.eu (213.251.130.109) 279.252 ms 246.437 ms 297.403 ms
14 rbx-g1-a9.fr.eu (91.121.128.86) 311.663 ms 230.110 ms 204.063 ms
15 vss-3b-6k.routers.ovh.net (213.186.32.254) 193.021 ms 190.254 ms 176.753 ms
16 ns345728.ip-188-165-200.eu (188.165.200.200) 210.153 ms 240.996 ms 260.246 ms

PING bras.afrihost.com (155.239.255.250): 56 data bytes
64 bytes from 155.239.255.250: icmp_seq=0 ttl=63 time=97.367 ms
64 bytes from 155.239.255.250: icmp_seq=1 ttl=63 time=58.375 ms
64 bytes from 155.239.255.250: icmp_seq=2 ttl=63 time=28.016 ms
64 bytes from 155.239.255.250: icmp_seq=3 ttl=63 time=8.480 ms
64 bytes from 155.239.255.250: icmp_seq=4 ttl=63 time=19.118 ms
64 bytes from 155.239.255.250: icmp_seq=5 ttl=63 time=162.894 ms
64 bytes from 155.239.255.250: icmp_seq=6 ttl=63 time=186.402 ms
64 bytes from 155.239.255.250: icmp_seq=7 ttl=63 time=168.755 ms
64 bytes from 155.239.255.250: icmp_seq=8 ttl=63 time=197.363 ms
64 bytes from 155.239.255.250: icmp_seq=9 ttl=63 time=135.074 ms
64 bytes from 155.239.255.250: icmp_seq=10 ttl=63 time=24.184 ms
64 bytes from 155.239.255.250: icmp_seq=11 ttl=63 time=140.339 ms
64 bytes from 155.239.255.250: icmp_seq=12 ttl=63 time=67.193 ms
64 bytes from 155.239.255.250: icmp_seq=13 ttl=63 time=189.626 ms
64 bytes from 155.239.255.250: icmp_seq=14 ttl=63 time=102.828 ms
64 bytes from 155.239.255.250: icmp_seq=15 ttl=63 time=33.400 ms
64 bytes from 155.239.255.250: icmp_seq=16 ttl=63 time=33.688 ms
64 bytes from 155.239.255.250: icmp_seq=17 ttl=63 time=33.020 ms
64 bytes from 155.239.255.250: icmp_seq=18 ttl=63 time=167.750 ms
64 bytes from 155.239.255.250: icmp_seq=19 ttl=63 time=42.886 ms
64 bytes from 155.239.255.250: icmp_seq=20 ttl=63 time=16.116 ms
^C
--- bras.afrihost.com ping statistics ---
21 packets transmitted, 21 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 8.480/91.089/197.363/66.091 ms

PING 188.165.200.200 (188.165.200.200): 56 data bytes
64 bytes from 188.165.200.200: icmp_seq=0 ttl=45 time=248.430 ms
64 bytes from 188.165.200.200: icmp_seq=1 ttl=45 time=278.129 ms
64 bytes from 188.165.200.200: icmp_seq=2 ttl=45 time=313.112 ms
64 bytes from 188.165.200.200: icmp_seq=3 ttl=45 time=242.714 ms
64 bytes from 188.165.200.200: icmp_seq=4 ttl=45 time=213.663 ms
64 bytes from 188.165.200.200: icmp_seq=5 ttl=45 time=191.889 ms
64 bytes from 188.165.200.200: icmp_seq=6 ttl=45 time=236.860 ms
64 bytes from 188.165.200.200: icmp_seq=7 ttl=45 time=245.153 ms
64 bytes from 188.165.200.200: icmp_seq=8 ttl=45 time=330.036 ms
64 bytes from 188.165.200.200: icmp_seq=9 ttl=45 time=499.634 ms
64 bytes from 188.165.200.200: icmp_seq=10 ttl=45 time=553.505 ms
64 bytes from 188.165.200.200: icmp_seq=11 ttl=45 time=473.308 ms
64 bytes from 188.165.200.200: icmp_seq=12 ttl=45 time=459.183 ms
64 bytes from 188.165.200.200: icmp_seq=13 ttl=45 time=472.237 ms
Request timeout for icmp_seq 14
64 bytes from 188.165.200.200: icmp_seq=15 ttl=45 time=236.962 ms
64 bytes from 188.165.200.200: icmp_seq=16 ttl=45 time=296.528 ms
64 bytes from 188.165.200.200: icmp_seq=17 ttl=45 time=393.961 ms
64 bytes from 188.165.200.200: icmp_seq=18 ttl=45 time=525.812 ms
^C
--- 188.165.200.200 ping statistics ---
20 packets transmitted, 18 packets received, 10.0% packet loss
round-trip min/avg/max/stddev = 191.889/345.062/553.505/117.862 ms


not looking that good and 10% packet loss

Not at all happy here in Somerset West Tracert from 22:27

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

1 2 ms 2 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 582 ms 579 ms 565 ms cpt-rx2.net.afrihost.co.za [169.1.5.82]
4 523 ms 389 ms 418 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
5 406 ms 388 ms 489 ms 41.164.52.40
6 581 ms * 311 ms 172.18.32.33
7 506 ms * 512 ms mtnns-2.cinx.net.za [196.223.22.31]
8 515 ms * 600 ms 196.44.0.75
9 * 512 ms 496 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
10 593 ms * 544 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
11 547 ms * 548 ms jh-dca-1.za--jh-cr-2.za-a.mtnns.net [41.181.180.8]
12 450 ms 528 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
13 581 ms * 485 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Those results don't look good at all :(
Can you ping bras.afrihost.com please?
 
Yep, Lag spikes is still sporadic tried some Diablo III last night between 6:30 and 9 pm, with latencey running between ~200 and ~700 ..... definitely not ideal when one gets ganked by mobs on a glass canon Witch Doctor :(

5:30 am this morning - the latency spikes still present :wtf:

-snip


Don't want to sound full of cr@p, but ............. with the 23rd getting closer and with the "miracle" network still being in "test phase" I am not sure if my disappointment with the "latency" experienced on my Afrihost account is premature and if I should stick it out for another month (reminds me of the classic song from The Clash - Should I stay or should I go :D)

We're running through the final preps for migration now, so we're all setup for today. Our guys have been at is since 3am.
Was anything being run on the line when you started that ping? Seeing very high latency to your exchange on the initial test.
 
Last edited:
We're running through the final preps for migration now, so we're all setup for today. Our guys have been at is since 3am.
Was anything being run on the line when you started that ping? Seeing very high latency to your exchange on the initial test.

Yeah, silly me ....... when I noticed the latency during my "pre-Salt Mine" gaming session (nothing better to get one in the mood for the office like slaughtering a few mobs in DIII - and ofc, it helps with the road rage en route to the office :p), I turned on my torrents (at half bandwidth) just to see how they were doing (they were running perfect ofc) and forgot to turn them off again when I ran the traceroute :whistle: (what a pro I am :o)

PS: Torrents were active at half bandwidth during all the posted tests
 
Yeah, silly me ....... when I noticed the latency during my "pre-Salt Mine" gaming session (nothing better to get one in the mood for the office like slaughtering a few mobs in DIII - and ofc, it helps with the road rage en route to the office :p), I turned on my torrents (at half bandwidth) just to see how they were doing (they were running perfect ofc) and forgot to turn them off again when I ran the traceroute :whistle: (what a pro I am :o)

PS: Torrents were active at half bandwidth during all the posted tests

Ah OK.
So cancelling those results out, your ping looks really good. Let's get through the migration and we can run some more tests :)
 
Looking good thus far...

4763196291.png


/pats AfriTeam on the backs!
 
Morning guys

Updates are being provided on a migration update page. I'll post as much info as I can here though.
https://www.afrihost.com/landing/network_updates/

Morning AfriGuy

According to that Network IP check page both my AfriGreen and old/normal accounts are running on the new network. When doing a tracert I do see a difference between how they route. Is this expected? Specifically look at hop 4

AfriGreen:
Code:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     6 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     9 ms     7 ms     8 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94] 
  5    10 ms     7 ms     7 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6     8 ms     8 ms     8 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7    12 ms    11 ms    12 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8     7 ms     8 ms     7 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    14 ms    13 ms    11 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     9 ms     9 ms     8 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Old Account:
Code:
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     6 ms     6 ms     6 ms  169-0-54-1.ip.afrihost.co.za [169.0.54.1] 
  3     *        *        *     Request timed out.
  4     8 ms     7 ms     7 ms  cpt-rx2.net.afrihost.co.za [169.1.5.82] 
  5     7 ms     7 ms     7 ms  cpt-net1.net.afrihost.co.za [169.1.5.128] 
  6     9 ms     8 ms     8 ms  optinet.ct1.napafrica.net [196.10.140.145] 
  7     8 ms    11 ms    13 ms  te0-0-0-1.cpt-p-1.optinet.net [197.84.7.1] 
  8     9 ms    12 ms     8 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9     9 ms     8 ms     8 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10     8 ms     9 ms     9 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X