How did it affect you guys ?Are you asking what happened with the DDoS in 2019?
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
How did it affect you guys ?Are you asking what happened with the DDoS in 2019?
Is there a big difference that you are wanting to move?My experience with Afrihost has been great. Good stable internet, and slightly cheaper than Cool Ideas, their support has been decent and timely via WhatsApp. That being said, I am busy migrating to CISP to enjoy their far superior routing and gaming latencies on EU servers.
I hit blizzard on CISP at 149ms where a friend of mine on Afrihost also Cape Town hits Blizzard at 176ms.. 27ms difference... They get 196ms in Overwatch i get 159ms both in CT, they run a VPN whenever they are gamingIs there a big difference that you are wanting to move?
Yes. About 50ms difference between my Afrihost connection to Pubg, and my folks CISP connection. I get 200ms on Afrihost. My folks get 150ms on CISP.Is there a big difference that you are wanting to move?
@AfriNatic it's less of a feeling and more of a "here are the facts" kind of issue. I experience 200ms pings to Pubg with you due to the poorer routing to the EU on Afrihost vs CISP. I used a vpn to improve my pings which dropped my pings by 20ms using WarpVPN, but that just costs me extra. Cisp has much better routing to the EU. Don't know why. Peering or something?Hi,
I'm sorry you feel our latency to EU is not as good.
If you have examples for me I can assist if you are experiencing any issues.
@AfriNatic it's less of a feeling and more of a "here are the facts" kind of issue. I experience 200ms pings to Pubg with you due to the poorer routing to the EU on Afrihost vs CISP. I used a vpn to improve my pings which dropped my pings by 20ms using WarpVPN, but that just costs me extra. Cisp has much better routing to the EU. Don't know why. Peering or something?
I'm also still experiencing a soft capped line speed of 50mbit down on Afrihost while I'm apparently paying for 100mbit. I contacted your supported on WhatsApp but they were clueless in helping me. I would have complained a little more, but honestly it's not worth my time right now as I'm moving to CISP.
If you can improve my pings to frankfurt AWS by 50ms, then you've got a happy remaining customer.If you can provide me with some trace routes for me to investigate if there is something we can do to improve the latency we can investigate that.
With regards to your speeds I can also have a look into that for you.
Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dlinkrouter.Dlink [192.168.0.1]
2 * * * Request timed out.
3 8 ms 10 ms 4 ms 165-73-14-137.ip.afrihost.co.za [165.73.14.137]
4 6 ms 5 ms 6 ms 169-1-21-149.ip.afrihost.co.za [169.1.21.149]
5 10 ms 5 ms 6 ms 169-1-21-2.ip.afrihost.co.za [169.1.21.2]
6 6 ms 5 ms 6 ms 169-1-21-3.ip.afrihost.co.za [169.1.21.3]
7 7 ms 5 ms 6 ms 52.95.218.148
8 5 ms 6 ms 5 ms 52.93.57.42
9 4 ms 6 ms 6 ms 52.93.57.49
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Pinging 35.156.63.252 with 32 bytes of data:
Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=199ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=199ms TTL=231
Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
Reply from 35.156.63.252: bytes=32 time=196ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
Reply from 35.156.63.252: bytes=32 time=199ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=199ms TTL=231
Reply from 35.156.63.252: bytes=32 time=196ms TTL=231
Reply from 35.156.63.252: bytes=32 time=198ms TTL=231
Reply from 35.156.63.252: bytes=32 time=200ms TTL=231
Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
Wa wa wee wah! 156ms! @AfriNatic figure that out, and figure out how your customers can also enjoy that latency, and then you'll have a good case against the gamer community to join Afrihost.
AfrihostIf you can provide me with some trace routes for me to investigate if there is something we can do to improve the latency we can investigate that.
With regards to your speeds I can also have a look into that for you.


If you can improve my pings to frankfurt AWS by 50ms, then you've got a happy remaining customer.
I'm not entirely sure how you would investigate that though, as traffic to AWS ECS instances jump through many hops that just time out. A trace route to one of the apparent Frankfurt AWS instances that hosts the Pubg server (found by googling) yields little information.
Code:Tracing route to ec2-35-156-63-252.eu-central-1.compute.amazonaws.com [35.156.63.252] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms dlinkrouter.Dlink [192.168.0.1] 2 * * * Request timed out. 3 8 ms 10 ms 4 ms 165-73-14-137.ip.afrihost.co.za [165.73.14.137] 4 6 ms 5 ms 6 ms 169-1-21-149.ip.afrihost.co.za [169.1.21.149] 5 10 ms 5 ms 6 ms 169-1-21-2.ip.afrihost.co.za [169.1.21.2] 6 6 ms 5 ms 6 ms 169-1-21-3.ip.afrihost.co.za [169.1.21.3] 7 7 ms 5 ms 6 ms 52.95.218.148 8 5 ms 6 ms 5 ms 52.93.57.42 9 4 ms 6 ms 6 ms 52.93.57.49 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete.
But here is the ping to that server:
Code:Pinging 35.156.63.252 with 32 bytes of data: Reply from 35.156.63.252: bytes=32 time=197ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=199ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=199ms TTL=231 Reply from 35.156.63.252: bytes=32 time=197ms TTL=231 Reply from 35.156.63.252: bytes=32 time=196ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=197ms TTL=231 Reply from 35.156.63.252: bytes=32 time=199ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=199ms TTL=231 Reply from 35.156.63.252: bytes=32 time=196ms TTL=231 Reply from 35.156.63.252: bytes=32 time=198ms TTL=231 Reply from 35.156.63.252: bytes=32 time=200ms TTL=231 Reply from 35.156.63.252: bytes=32 time=197ms TTL=231 Reply from 35.156.63.252: bytes=32 time=197ms TTL=231
I totally understand it's a dilemma you have to resolve, but unfortunately for you, that is your problem to solve.That is the scenic route that AWS takes after we give them the traffic at
52.95.218.148
It's difficult thing to balance. The advantage of AWS direct connect vs picking the traffic up in the UK or France.
You have 10 clients that want lower latency to AWS Middle East when that route is up and then you have 10 people that want lower latency to EU. How does an ISP decide who gets what.
What is the name of this tool ?
Pingplotter there is a free versionWhat is the name of this tool ?
hellopeter is not a reputable site anymore, they got bought out a couple years ago and hardly anyone uses them anymore they charge quite a bit to be on their site... use the forums as a means of comparing, you generally have people who know what they talking about on here, if you look on facebook and other sites you will see people completely destroying ISP's when in fact the FNO is the issue i see a lot it in my area since people think Vumatel or Octotel is an ISP...I see both Afrihost and CISP have their fair share of complaints.