Afrihost POC Network - Afrigreen Feedback

[AfriGuy]

Armored Warfare has just gone into Open Beta. Afrigreen uncapped resulted in full packet loss and 2000ms ping. Web Africa Free 1 GB had no issues. I play on EU servers.

I'd definitely recommend submitting the details through on ClientZone - our network guys will be able to check out what needs to be tweaked

 

[AfriGuy]

Hi AfriFella,

Any update on your review?

I'll ask him to stop by
Was it a PM convo?

 

[signeffex]

Yawn

?

 

[Igor III]

I'll ask him to stop by
Was it a PM convo?

Nope - was in this thread, I passed him my last fault log code - to which he replied that he will have a look at my account and fault logs and let me know what he sees.

 

[AfriGuy]

Nope - was in this thread, I passed him my last fault log code - to which he replied that he will have a look at my account and fault logs and let me know what he sees.

Coolios, will follow up with him.

 

[Emissary_Of_Pain]

When is this network supposed to be working now ... cause I am getting tired of not being able to stream or game


:::EDIT:::

Still no reply from Gian

 

[AfriGuy]

When is this network supposed to be working now ... cause I am getting tired of not being able to stream or game


:::EDIT:::

Still no reply from Gian

Hi

As mentioned, we'll be posting further updates when they're available.
The timeline for a production roll out is still the same - within October.

 

[caroper]

Hi

As mentioned, we'll be posting further updates when they're available.
The timeline for a production roll out is still the same - within October.

October 2015?
Afrihost definition of Soon tends to vary from weeks to years.

 

[Vorastra]

I'd definitely recommend submitting the details through on ClientZone - our network guys will be able to check out what needs to be tweaked

Done. Just a question. Will they get back to me, or is it just one-way feedback? I assume it's through email if they do respond?

 

[AfriGuy]

Done. Just a question. Will they get back to me, or is it just one-way feedback? I assume it's through email if they do respond?

I promise you it'll be looked at as it's something we'll definitely want to launch with production using those rules.

 

[Vorastra]

I promise you it'll be looked at as it's something we'll definitely want to launch with production using those rules.

Oh OK. I wanted to know since it's not an email account I frequently use.
Thanks.

 

[AfriGuy]

Oh OK. I wanted to know since it's not an email account I frequently use.
Thanks.

No worries
It'll definitely be looked at.

 

[LaraC]

Account type: 10Mbps Home Capped.

Still very happy with AfriGreen’s performance.

 

[AfriGuy]

Account type: 10Mbps Home Capped.

Still very happy with AfriGreen’s performance.

View attachment 303834
View attachment 303836

Super consistent results those

 

[LaraC]

Super consistent results those

Were the network guys able to find the reason why business and uncapped customers had unsatisfactory throughput during evenings?

 

[AfriGuy]

Were the network guys able to find the reason why business and uncapped customers had unsatisfactory throughput during evenings?

Demand generally increases in the evenings - so we're reaching some limitations on the network which causes slow throughput.
This should only really be affected P2P and downloads though.

 

[LaraC]

Thank you, this test was done during contentious time.

 

[Igor III]

I think let it run for at least 30 seconds to a minute a minute or so, we want to be able to identify clearly if the ping is consistent and what that ping response is in general.

For starters, I must say that my connection tonight is much better than the last two weeks (and I really mean much better).

Out of 5 ping plotter tests one shows a high latency spike on hop 3, making the average out of 5 runs only 50 ms.

This can also be seen in the ping test as every once in a while there is one that runs around the 300 ms mark, whilst most is more around the 200 mark.

As I said this is the best connection I had on AfriGreen in two weeks, not sure what has changed (nothing on my side is altered in anyway).

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

C:\Users\Mine> ping fweu1.en.perfectworld.eu -t

Pinging fweu1.en.perfectworld.eu [95.172.91.23] with 32 bytes of data:
Reply from 95.172.91.23: bytes=32 time=210ms TTL=37
Reply from 95.172.91.23: bytes=32 time=205ms TTL=37
Reply from 95.172.91.23: bytes=32 time=197ms TTL=37
Reply from 95.172.91.23: bytes=32 time=209ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=221ms TTL=37
Reply from 95.172.91.23: bytes=32 time=208ms TTL=37
Reply from 95.172.91.23: bytes=32 time=202ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=238ms TTL=37
Reply from 95.172.91.23: bytes=32 time=252ms TTL=37
Reply from 95.172.91.23: bytes=32 time=205ms TTL=37
Reply from 95.172.91.23: bytes=32 time=231ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=203ms TTL=37
Reply from 95.172.91.23: bytes=32 time=206ms TTL=37
Reply from 95.172.91.23: bytes=32 time=223ms TTL=37
Reply from 95.172.91.23: bytes=32 time=197ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=197ms TTL=37
Reply from 95.172.91.23: bytes=32 time=202ms TTL=37
Reply from 95.172.91.23: bytes=32 time=213ms TTL=37
Reply from 95.172.91.23: bytes=32 time=225ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=206ms TTL=37
Reply from 95.172.91.23: bytes=32 time=203ms TTL=37
Reply from 95.172.91.23: bytes=32 time=212ms TTL=37
Reply from 95.172.91.23: bytes=32 time=205ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=317ms TTL=37
Reply from 95.172.91.23: bytes=32 time=229ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=268ms TTL=37
Reply from 95.172.91.23: bytes=32 time=273ms TTL=37
Reply from 95.172.91.23: bytes=32 time=244ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=202ms TTL=37
Reply from 95.172.91.23: bytes=32 time=202ms TTL=37
Reply from 95.172.91.23: bytes=32 time=210ms TTL=37
Reply from 95.172.91.23: bytes=32 time=250ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=201ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=247ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=225ms TTL=37
Reply from 95.172.91.23: bytes=32 time=201ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=222ms TTL=37
Reply from 95.172.91.23: bytes=32 time=206ms TTL=37
Reply from 95.172.91.23: bytes=32 time=222ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=211ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=208ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=205ms TTL=37
Reply from 95.172.91.23: bytes=32 time=277ms TTL=37
Reply from 95.172.91.23: bytes=32 time=212ms TTL=37
Reply from 95.172.91.23: bytes=32 time=207ms TTL=37
Reply from 95.172.91.23: bytes=32 time=212ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=252ms TTL=37
Reply from 95.172.91.23: bytes=32 time=266ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=197ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=207ms TTL=37
Reply from 95.172.91.23: bytes=32 time=204ms TTL=37
Reply from 95.172.91.23: bytes=32 time=218ms TTL=37
Reply from 95.172.91.23: bytes=32 time=203ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=204ms TTL=37
Reply from 95.172.91.23: bytes=32 time=197ms TTL=37
Reply from 95.172.91.23: bytes=32 time=252ms TTL=37
Reply from 95.172.91.23: bytes=32 time=234ms TTL=37
Reply from 95.172.91.23: bytes=32 time=203ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=215ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=217ms TTL=37
Reply from 95.172.91.23: bytes=32 time=212ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=198ms TTL=37
Reply from 95.172.91.23: bytes=32 time=227ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=236ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=200ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=311ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=199ms TTL=37
Reply from 95.172.91.23: bytes=32 time=208ms TTL=37

Ping statistics for 95.172.91.23:
Packets: Sent = 112, Received = 112, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 197ms, Maximum = 317ms, Average = 211ms
Control-C

 

[AfriGuy]

Thank you, this test was done during contentious time.
View attachment 303854
View attachment 303856

Doesn't look bad at all.
Would you be able to run another test at around 8pm tonight?

 

[AfriGuy]

For starters, I must say that my connection tonight is much better than the last two weeks (and I really mean much better).

Out of 5 ping plotter tests one shows a high latency spike on hop 3, making the average out of 5 runs only 50 ms.

This can also be seen in the ping test as every once in a while there is one that runs around the 300 ms mark, whilst most is more around the 200 mark.

As I said this is the best connection I had on AfriGreen in two weeks, not sure what has changed (nothing on my side is altered in anyway).

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

C:\Users\Mine> ping fweu1.en.perfectworld.eu -t

-snip

Not looking too bad, much better compared to the results you've previously posted