Afrihost POC Network - Afrigreen Feedback

[AfriGenie]

PM Sent

Got it! Thanks.

 

[8-BALL]

Still getting local latency even though it appears to be routing through CPT

Tracing route to mc.shadowraze.net [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 70 ms 33 ms 53 ms cpt-up1.net.afrihost.co.za [169.1.5.105]
4 60 ms 63 ms 29 ms cpt-up2.net.afrihost.co.za [169.1.5.106]
5 32 ms 30 ms 19 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
6 47 ms 28 ms 8 ms 41.164.52.40
7 83 ms 64 ms 70 ms 172.18.16.3
8 38 ms 69 ms 36 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
9 255 ms 206 ms 251 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 177 ms 235 ms 281 ms if-1-0-0-5.core2.PV9-Lisbon.as6453.net [195.219.214.53]
11 226 ms 194 ms 212 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
12 227 ms 275 ms 223 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 220 ms 244 ms 252 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
14 242 ms 205 ms 206 ms if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
15 229 ms 247 ms 282 ms ldn-1-a9.uk.eu [213.251.130.109]
16 240 ms 197 ms 266 ms rbx-g1-a9.fr.eu [91.121.128.86]
17 206 ms 217 ms 243 ms vss-3-6k.routers.ovh.net [94.23.122.237]
18 247 ms 253 ms 215 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.

 

[AfriGenie]

Still getting local latency even though it appears to be routing through CPT

Tracing route to mc.shadowraze.net [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 70 ms 33 ms 53 ms cpt-up1.net.afrihost.co.za [169.1.5.105]
4 60 ms 63 ms 29 ms cpt-up2.net.afrihost.co.za [169.1.5.106]
5 32 ms 30 ms 19 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
6 47 ms 28 ms 8 ms 41.164.52.40
7 83 ms 64 ms 70 ms 172.18.16.3
8 38 ms 69 ms 36 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
9 255 ms 206 ms 251 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 177 ms 235 ms 281 ms if-1-0-0-5.core2.PV9-Lisbon.as6453.net [195.219.214.53]
11 226 ms 194 ms 212 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
12 227 ms 275 ms 223 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 220 ms 244 ms 252 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
14 242 ms 205 ms 206 ms if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
15 229 ms 247 ms 282 ms ldn-1-a9.uk.eu [213.251.130.109]
16 240 ms 197 ms 266 ms rbx-g1-a9.fr.eu [91.121.128.86]
17 206 ms 217 ms 243 ms vss-3-6k.routers.ovh.net [94.23.122.237]
18 247 ms 253 ms 215 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.

Our Team is working on this with our upstream provider at the moment, so you should see an improvement in that regard.

 

[LaraC]

PM Sent

Got it! Thanks.

Aye yai yai, the suspense is killing me. Post the new test results please.

 

[Flikka]

@LaraC

Unfortunately same issue after the account has been refreshed, working with AfriGenie to see if we can get it sorted out.

 

[LaraC]

@LaraC

Unfortunately same issue after the account has been refreshed, working with AfriGenie to see if we can get it sorted out.

Oh no's. Hope it is fixed soon.

 

[Hummercellc]

Everything still seems fine this end, patiently waiting for the east cut over here. But might be moving to Neotel Fibre, so not really focusing on what's happening at the moment on Afrigreen.

 

[electrofreeze]

looks like the 6-11pm slump is back

 

[AfriGenie]

@LaraC

Unfortunately same issue after the account has been refreshed, working with AfriGenie to see if we can get it sorted out.

Oh no's. Hope it is fixed soon.

Looks like there is an issue on the line or at the Exchange, the same latency is present with a Telkom account.

BUT!

We will get it resolved!

 

[AfriGenie]

looks like the 6-11pm slump is back

There shouldn't be at all on your Afrigreen account. Are you connecting using a legacy @afrihost.co.za account or an @afrigreen account?

 

[LaraC]

Looks like there is an issue on the line or at the Exchange, the same latency is present with a Telkom account.

BUT!

We will get it resolved!

That is cool, a real team effort.

 

[electrofreeze]

As you can see, there is a big spike in latency at AH:

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 315 ms * 321 ms 169-1-5-82.ip.afrihost.co.za [169.1.5.82]
4 322 ms 423 ms 322 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
5 421 ms 402 ms 392 ms 41.164.52.40
6 374 ms 412 ms 406 ms 172.18.1.162
7 * * * Request timed out.
8 479 ms 491 ms 564 ms if-1-2-0-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.17]
9 511 ms 683 ms 462 ms if-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
10 657 ms 439 ms 509 ms if-1-0-0-3.core2.PV9-Lisbon.as6453.net [195.219.214.34]
11 517 ms 493 ms 476 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
12 544 ms 520 ms 617 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 479 ms 567 ms 528 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
14 515 ms 667 ms * if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
15 503 ms 653 ms 472 ms ldn-1-a9.uk.eu [213.251.130.109]
16 571 ms 492 ms 435 ms rbx-g1-a9.fr.eu [91.121.128.86]
17 531 ms 544 ms 500 ms vss-3-6k.routers.ovh.net [94.23.122.237]
18 492 ms 452 ms 534 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.

 

[junwin]

Looks like you guys have a problem with your peering to neotel. I cannot VPN to the office,

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.10.1 0.0% 15 1.4 2.6 1.2 16.5 3.9
2. 169-0-56-1.ip.afrihost.co.za 0.0% 15 11.6 8.7 7.4 13.0 1.5
3. ???
4. 169-1-5-162.ip.afrihost.co.za 0.0% 15 11.1 11.6 9.7 19.9 2.5
5. 169-1-5-204.ip.afrihost.co.za 0.0% 15 10.1 10.4 9.3 13.5 1.0
6. 41.162.84.192 0.0% 15 10.3 11.1 10.3 14.5 0.9
7. 172.18.1.59 0.0% 15 35.4 20.2 18.3 35.4 4.2
8. 41.160.0.248 0.0% 15 19.1 19.2 18.4 20.0 0.0
9. ???

 

[junwin]

Ok, connectivity appears to be restored.

 

[electrofreeze]

speeds are up and down again this evening dropping to half the line speed

 

[Igor III]

Early morning and the latency on the new afrigreen network definitely do not look good

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

C:\Users\Igor III>ping telkom.co.za -t

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=1091ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1158ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1029ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1138ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1110ms TTL=244
Reply from 196.43.22.222: bytes=32 time=792ms TTL=244
Reply from 196.43.22.222: bytes=32 time=842ms TTL=244
Reply from 196.43.22.222: bytes=32 time=841ms TTL=244
Reply from 196.43.22.222: bytes=32 time=964ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1117ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1240ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1144ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1101ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1017ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1071ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1169ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1050ms TTL=244
Reply from 196.43.22.222: bytes=32 time=920ms TTL=244
Reply from 196.43.22.222: bytes=32 time=875ms TTL=244
Reply from 196.43.22.222: bytes=32 time=958ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1058ms TTL=244
Reply from 196.43.22.222: bytes=32 time=950ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1116ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1036ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1053ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1178ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1107ms TTL=244
Reply from 196.43.22.222: bytes=32 time=981ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1068ms TTL=244
Reply from 196.43.22.222: bytes=32 time=991ms TTL=244
Reply from 196.43.22.222: bytes=32 time=923ms TTL=244

Ping statistics for 196.43.22.222:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 792ms, Maximum = 1240ms, Average = 1035ms
Control-C
^C

Thank goodness, this is not permanent .............. 10 minutes later, latency is down to an average of 20 ms to the same IP.

 

[AfriMan]

As you can see, there is a big spike in latency at AH:

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 315 ms * 321 ms 169-1-5-82.ip.afrihost.co.za [169.1.5.82]
4 322 ms 423 ms 322 ms cpt-net1.net.afrihost.co.za [169.1.5.128]
5 421 ms 402 ms 392 ms 41.164.52.40
6 374 ms 412 ms 406 ms 172.18.1.162
7 * * * Request timed out.
8 479 ms 491 ms 564 ms if-1-2-0-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.17]
9 511 ms 683 ms 462 ms if-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
10 657 ms 439 ms 509 ms if-1-0-0-3.core2.PV9-Lisbon.as6453.net [195.219.214.34]
11 517 ms 493 ms 476 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
12 544 ms 520 ms 617 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 479 ms 567 ms 528 ms if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
14 515 ms 667 ms * if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
15 503 ms 653 ms 472 ms ldn-1-a9.uk.eu [213.251.130.109]
16 571 ms 492 ms 435 ms rbx-g1-a9.fr.eu [91.121.128.86]
17 531 ms 544 ms 500 ms vss-3-6k.routers.ovh.net [94.23.122.237]
18 492 ms 452 ms 534 ms ns345728.ip-188-165-200.eu [188.165.200.200]

Trace complete.

Can you ping bras.afrihost.com?

 

[AfriMan]

Looks like you guys have a problem with your peering to neotel. I cannot VPN to the office,

Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.10.1 0.0% 15 1.4 2.6 1.2 16.5 3.9
2. 169-0-56-1.ip.afrihost.co.za 0.0% 15 11.6 8.7 7.4 13.0 1.5
3. ???
4. 169-1-5-162.ip.afrihost.co.za 0.0% 15 11.1 11.6 9.7 19.9 2.5
5. 169-1-5-204.ip.afrihost.co.za 0.0% 15 10.1 10.4 9.3 13.5 1.0
6. 41.162.84.192 0.0% 15 10.3 11.1 10.3 14.5 0.9
7. 172.18.1.59 0.0% 15 35.4 20.2 18.3 35.4 4.2
8. 41.160.0.248 0.0% 15 19.1 19.2 18.4 20.0 0.0
9. ???

I think we peer directly at NAP so that's concerning. I see it was resolved but please let me know if that happens again

 

[AfriMan]

Early morning and the latency on the new afrigreen network definitely do not look good

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

C:\Users\Igor III>ping telkom.co.za -t

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=1091ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1158ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1029ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1138ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1110ms TTL=244
Reply from 196.43.22.222: bytes=32 time=792ms TTL=244
Reply from 196.43.22.222: bytes=32 time=842ms TTL=244
Reply from 196.43.22.222: bytes=32 time=841ms TTL=244
Reply from 196.43.22.222: bytes=32 time=964ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1117ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1240ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1144ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1101ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1017ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1071ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1169ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1050ms TTL=244
Reply from 196.43.22.222: bytes=32 time=920ms TTL=244
Reply from 196.43.22.222: bytes=32 time=875ms TTL=244
Reply from 196.43.22.222: bytes=32 time=958ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1058ms TTL=244
Reply from 196.43.22.222: bytes=32 time=950ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1116ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1036ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1053ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1178ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1107ms TTL=244
Reply from 196.43.22.222: bytes=32 time=981ms TTL=244
Reply from 196.43.22.222: bytes=32 time=1068ms TTL=244
Reply from 196.43.22.222: bytes=32 time=991ms TTL=244
Reply from 196.43.22.222: bytes=32 time=923ms TTL=244

Ping statistics for 196.43.22.222:
Packets: Sent = 31, Received = 31, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 792ms, Maximum = 1240ms, Average = 1035ms
Control-C
^C

Thank goodness, this is not permanent .............. 10 minutes later, latency is down to an average of 20 ms to the same IP.

That definitely not good. Can you also run the full trace when this happens so we can see where the latency occurs?

 

[Igor III]

That definitely not good. Can you also run the full trace when this happens so we can see where the latency occurs?

Will do .......... currently I am at the Salt Mine, earning my daily keep