Beri
Expert Member
- Joined
- Sep 26, 2006
- Messages
- 4,347
- Reaction score
- 68
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Hi AfriGuy, I've also signed up with new network as was notified to wait until new users added. Was hoping you could assist. Sent you a PM with my account details.
Can you drop me a PM with your ADSL username as well please, I can get you sorted ASAP.
I'm pretty certain the ADSL username was in the PM?
Except that you sent the PM to AfriGuy - who left - and not to me - AfriGenie.![]()
My bad sorry about that, have since sent you a PM. Thanks in advance.
There are no additional costs involved around Afrigreen.
Have you run through the official thread?
I dont think you understand. I will be giving the money that I gave to you this month (for a service that is not working), to WebAfrica next month (for a service that seems to be working). I am not going to pay WA for data and then you as well in order to test your AfriGreen account. If you give me a free account (not a 1G test account) I will test it, but I am not going to pay for it.
I am sure that can be arranged, if you are willing that is.![]()

Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=12 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=56 time=10 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=11 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=10 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=10 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=8 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=7 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=7 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=7 ms
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 192.168.2.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 41.170.79.2 90 ms 8 ms 9 ms
4 41.170.79.2 8 ms 8 ms 8 ms
5 41.170.79.2 7 ms 7 ms 7 ms
6 41.160.2.3 8 ms 8 ms 7 ms
7 196.223.14.3 10 ms 10 ms 9 ms
8 196.44.0.2 11 ms 11 ms 11 ms
9 196.44.31.9 11 ms 11 ms 12 ms
10 196.30.1.5 11 ms 11 ms 11 ms
11 196.31.220.2 12 ms 11 ms 11 ms
12 196.31.63.2 11 ms 11 ms 11 ms
13 196.30.42.1 10 ms 17 ms 10 ms
14 197.242.144.1 10 ms 11 ms 11 ms
traceroute -n 8.8.8.8
1 192.168.2.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 41.170.79.2 9 ms 7 ms 8 ms
4 41.170.79.2 8 ms 8 ms 8 ms
5 41.170.79.2 7 ms 7 ms 7 ms
6 196.46.25.1 7 ms 7 ms 7 ms
7 72.14.239.3 8 ms 7 ms 7 ms
8 8.8.8.8 8 ms 7 ms 7 ms
DNS Test:
nslookup www.afrihost.com
Name: www.afrihost.com
Address: 41.181.185.18
nslookup www.google.com
Name: www.google.com
Address: 216.58.223.4
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
Ok, ill bite. It cant get any worse that what it currently is. PM sent.
AfriGenie, some stats for you and the team:
Location: Daspoort, Pretoria using @afrigreen account:
View attachment 236938
Code:Ping Test: ping 197.242.144.102 64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=12 ms 64 bytes from 197.242.144.102: icmp_req=2 ttl=56 time=10 ms 64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=11 ms 64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=10 ms 64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=10 ms ping 8.8.8.8 64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=8 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=7 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=7 ms 64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=7 ms Request timeout for icmp_seq 5 Trace Test: traceroute -n 197.242.144.102 1 192.168.2.1 1 ms 1 ms 1 ms 2 Request timed out * * * 3 41.170.79.2 90 ms 8 ms 9 ms 4 41.170.79.2 8 ms 8 ms 8 ms 5 41.170.79.2 7 ms 7 ms 7 ms 6 41.160.2.3 8 ms 8 ms 7 ms 7 196.223.14.3 10 ms 10 ms 9 ms 8 196.44.0.2 11 ms 11 ms 11 ms 9 196.44.31.9 11 ms 11 ms 12 ms 10 196.30.1.5 11 ms 11 ms 11 ms 11 196.31.220.2 12 ms 11 ms 11 ms 12 196.31.63.2 11 ms 11 ms 11 ms 13 196.30.42.1 10 ms 17 ms 10 ms 14 197.242.144.1 10 ms 11 ms 11 ms traceroute -n 8.8.8.8 1 192.168.2.1 1 ms 1 ms 1 ms 2 Request timed out * * * 3 41.170.79.2 9 ms 7 ms 8 ms 4 41.170.79.2 8 ms 8 ms 8 ms 5 41.170.79.2 7 ms 7 ms 7 ms 6 196.46.25.1 7 ms 7 ms 7 ms 7 72.14.239.3 8 ms 7 ms 7 ms 8 8.8.8.8 8 ms 7 ms 7 ms DNS Test: nslookup www.afrihost.com Name: www.afrihost.com Address: 41.181.185.18 nslookup www.google.com Name: www.google.com Address: 216.58.223.4 nslookup thishouldfail.afrihost.com ** server can't find thisshouldfail.com: NXDOMAIN
Pinging youtube.com [216.58.223.14] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Request timed out.
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Request timed out.
Request timed out.
Reply from 216.58.223.14: bytes=32 time=183ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Request timed out.
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=184ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Request timed out.
Reply from 216.58.223.14: bytes=32 time=181ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Reply from 216.58.223.14: bytes=32 time=182ms TTL=53
Ping statistics for 216.58.223.14:
Packets: Sent = 24, Received = 17, Lost = 7 (29% loss),
Approximate round trip times in milli-seconds:
Minimum = 181ms, Maximum = 184ms, Average = 182ms
Control-C
^C
http://mybroadband.co.za/vb/showthread.php?t=712920Would some one be so kind as to post a link to the Afrihost Green feedback thread?
I received my login details but the email didn't contain a link.
Very erratic...
Code:Pinging youtube.com [216.58.223.14] with 32 bytes of data: Request timed out. Request timed out. Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Request timed out. Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Request timed out. Request timed out. Reply from 216.58.223.14: bytes=32 time=183ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Request timed out. Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=184ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Request timed out. Reply from 216.58.223.14: bytes=32 time=181ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Reply from 216.58.223.14: bytes=32 time=182ms TTL=53 Ping statistics for 216.58.223.14: Packets: Sent = 24, Received = 17, Lost = 7 (29% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 184ms, Average = 182ms Control-C ^C
Since getting my AfriGreen details today, my packetloss in CS:GO for example is 0% where before it was always 10% - 15%. Ping was mostly low, in the 30ms - 50ms range. So far so good, lets see if it hold up.