Afrihost POC Network - Afrigreen Feedback

[al4bb]

Can you please send me a PM with your Afrigreen username quickly, the Team wants to look into this quickly.

PM sent

For comparison here's on afrihost:

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 20 ms 20 ms 41.181.221.213
4 26 ms 25 ms 25 ms 41.181.221.214
5 20 ms 20 ms 20 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
6 26 ms 27 ms 27 ms rb-cr-2.za--rb-dca-2.za.mtnns.net [196.44.0.155]
7 27 ms 46 ms 26 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
8 20 ms 20 ms 21 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 21 ms 20 ms 21 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

 

[AfriGenie]

PM sent

For comparison here's on afrihost:

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 20 ms 20 ms 41.181.221.213
4 26 ms 25 ms 25 ms 41.181.221.214
5 20 ms 20 ms 20 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.118]
6 26 ms 27 ms 27 ms rb-cr-2.za--rb-dca-2.za.mtnns.net [196.44.0.155]
7 27 ms 46 ms 26 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
8 20 ms 20 ms 21 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 21 ms 20 ms 21 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Got your PM! Thanks. Also, thank you for the comparative test results.

 

[al4bb]

EDIT: Would you mind also pinging bras.afrihost.com and posting the results here.

C:\Windows\system32>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 1 ms 192.168.1.1
2 1206 ms 1684 ms 2518 ms 155.239.255.250

Trace complete.

 

[AfriGenie]

C:\Windows\system32>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 1 ms 192.168.1.1
2 1206 ms 1684 ms 2518 ms 155.239.255.250

Trace complete.

Thanks!

Our Team is seeing significantly higher upload traffic on your account, than download traffic, can you check if you are running any services in the background please.

 

[Igor III]

Are you in Cape Town? We are working in improving Google routing in the South right now.

Nope - in JHB, but I do notice my traffic gets routed from JHB to CPT with Afrihost (IP 216.6.55.37 to 41.206.178.2 - ix-0-3-0-0.tocor1l.JSO-Johannesburg.as645 to if-4-2.tcore1.KLT-Cape-Town.as6453.net)

 

[al4bb]

Thanks!

Our Team is seeing significantly higher upload traffic on your account, than download traffic, can you check if you are running any services in the background please.

I see Zotero just did an upload - have cancelled - nothing should be running at the moment.

 

[AfriGenie]

I see Zotero just did an upload - have cancelled - nothing should be running at the moment.

Thanks!

Would you mind running the traceroute again with your Afrigreen account.

 

[al4bb]

Thanks!

Would you mind running the traceroute again with your Afrigreen account.

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

1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 10 ms 10 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 18 ms 15 ms 17 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 9 ms 9 ms 10 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 16 ms 16 ms 15 ms 41.162.84.192
7 20 ms 19 ms 19 ms 172.18.1.59
8 27 ms 26 ms 41 ms mtnns-2.jinx.net.za [196.223.14.31]
9 31 ms 27 ms 27 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 27 ms 27 ms 27 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11 27 ms 26 ms 27 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

 

[AirWolf]

That's some good news then! How has the consistency of the connection been?

Changed over at the office from Friday - so far so good.

 

[AfriGenie]

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

1 <1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 10 ms 10 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 18 ms 15 ms 17 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 9 ms 9 ms 10 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 16 ms 16 ms 15 ms 41.162.84.192
7 20 ms 19 ms 19 ms 172.18.1.59
8 27 ms 26 ms 41 ms mtnns-2.jinx.net.za [196.223.14.31]
9 31 ms 27 ms 27 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 27 ms 27 ms 27 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11 27 ms 26 ms 27 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Much better! If notice anything similar to this happening again, please let us know!

 

[abjater]

Looks like you are routing these tests differently, possibly using pass through. It would be best to test these accounts by using the router settings, rather than passthrough. Accounts on passthrough generally perform differently, and it can be a misleading test

Done from the mikrotik. Same latency is visible.
WebAfrica:


AfriGreen:

 

[al4bb]

Much better! If notice anything similar to this happening again, please let us know!

Will do. Do you know what went wrong with Afrigreen as the Afrihost side seemed okay?

 

[LaraC]

Will do. Do you know what went wrong with Afrigreen as the Afrihost side seemed okay?

Maybe the following scenario were at play.

While connected to AfriGreen Zotero started its upload and degraded your network experience. You disconnected and connected with Afrihost severing the connection for Zotero which provided you with good results.

 

[AfriGenie]

Will do. Do you know what went wrong with Afrigreen as the Afrihost side seemed okay?

Maybe the following scenario were at play.

While connected to AfriGreen Zotero started its upload and degraded your network experience. You disconnected and connected with Afrihost severing the connection for Zotero which provided you with good results.

LaraC seems to have summed up the exact scenario that the Team came up with.

 

[al4bb]

Maybe the following scenario were at play.

While connected to AfriGreen Zotero started its upload and degraded your network experience. You disconnected and connected with Afrihost severing the connection for Zotero which provided you with good results.

Nope
Switched back and forth several times and results were consistent.
Only after the PM did I close my PDF viewers which initiated the upload which the support team detected.

 

[AfriGenie]

Done from the mikrotik. Same latency is visible.
WebAfrica:
View attachment 307726

AfriGreen:
View attachment 307728

There's still that extra hop on the Afrihost traceroute.

Can you please ping bras.afrihost.com.

 

[al4bb]

Nope
Switched back and forth several times and results were consistent.
Only after the PM did I close my PDF viewers which initiated the upload which the support team detected.

Here's the results while doing a heavy upload - not even close to the terrible performance of last night and this morning.

C:\Windows\system32>tracert www.afrihost.co.za

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 134 ms 150 ms 160 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 399 ms 411 ms 329 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 122 ms 162 ms 20 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 54 ms 45 ms 76 ms 41.162.84.192
7 191 ms 235 ms 212 ms 172.18.1.59
8 512 ms 427 ms 477 ms mtnns-2.jinx.net.za [196.223.14.31]
9 598 ms 685 ms 605 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 197 ms 154 ms 174 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11 168 ms 200 ms 193 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

 

[LaraC]

Nope
Switched back and forth several times and results were consistent.
Only after the PM did I close my PDF viewers which initiated the upload which the support team detected.

In that case AfriGreen is so awesome that Zotero could establish a connection immediately and thus were able to gobble up all your bandwidth.

 

[AfriGenie]

Here's the results while doing a heavy upload - not even close to the terrible performance of last night and this morning.

C:\Windows\system32>tracert www.afrihost.co.za

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 134 ms 150 ms 160 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 399 ms 411 ms 329 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 122 ms 162 ms 20 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 54 ms 45 ms 76 ms 41.162.84.192
7 191 ms 235 ms 212 ms 172.18.1.59
8 512 ms 427 ms 477 ms mtnns-2.jinx.net.za [196.223.14.31]
9 598 ms 685 ms 605 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 197 ms 154 ms 174 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11 168 ms 200 ms 193 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Hmmm, the Team didn't make any changes on their side, we'll need to keep an eye on this, and see if it happens again.

 

[al4bb]

In that case AfriGreen is so awesome that Zotero could establish a connection immediately and thus were able to gobble up all your bandwidth.