Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Gian must be laughing with his mouth full of teeth at these fools still testing this POC network, while he walked with millions.
 
Last few days have not been too good:

Ping Test dropping out:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=24 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=56 time=23 ms
Request timeout for icmp_seq 3
64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=23 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=29 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=42 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=28 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=27 ms
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=28 ms

Not consistent - see lines 3 & 4

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.1.2 26 ms 26 ms 123 ms
4 169.1.1.2 26 ms 70 ms 24 ms
5 41.170.79.2 19 ms 19 ms 19 ms
6 41.160.2.3 25 ms 26 ms 25 ms
7 196.223.14.3 49 ms 28 ms 29 ms
8 196.44.0.2 56 ms 50 ms
196.44.31.9 30 ms
9 196.44.31.9 31 ms
196.30.1.5 30 ms 28 ms
10 196.31.220.2 23 ms 23 ms 24 ms
11 196.31.63.2 24 ms 25 ms 24 ms
12 196.30.42.1 28 ms 29 ms 31 ms
13 197.242.144.1 24 ms 23 ms 24 ms
 
Last edited:
Bryn said:
The P2P performance on Afrigreen is becoming a serious pain in the arse. Does Afrigreen differentiate between capped/business and home users?
Click to expand...
Do I test at the correct times or am I just lucky?

Link.JPG
 
al4bb said:
Last few days have not been too good:
/snip
Click to expand...
Did the same test.
Code: 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 197.242.144.102

Pinging 197.242.144.102 with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56
Reply from 197.242.144.102: bytes=32 time=49ms TTL=56
Reply from 197.242.144.102: bytes=32 time=49ms TTL=56
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 50ms, Average = 49ms

C:\Users\Lara>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=46ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57
Reply from 8.8.8.8: bytes=32 time=44ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 46ms, Average = 45ms
 
AfriGuy said:
Will you run through some tests with our team at least? I really do want to help, but you do need to post some substance so we can help. I haven't seen any test results posted by you, even when things have been working fine. Unfortunately I can't do much with "things aren't working so well" :(
Click to expand...

AfriGuy, I've been in the exact same situation that electrofreeze and the other guys points they raising...

Cycle is this, I get back from work (say Monday) Afrigreen speeds are unsable +-2Mbps speed with pings of over 100-200 and certain sites not working... I posted a question after hours only to get your guys feedback the next morning asking us to "please post speed test and traceroutes", that evening I get back home any my speeds are perfectly fine - a few day passes with no issues until Friday evening and speeds are worse than ever. So off I go and do all the trace routes and speeds tests you requested. However your response is the next morning and you kick of by saying "can you please post a comparison with another network..."
Cycle continues, and Wednesday the problem creeps up, I post all the necessary tests and comparisons and I get told you never had the same issues in the evening...

When I escalated this issue further on your support portal it took over 2 months to finally get an engineer who was willing to sit down and look at the issues. However debugging through my logs and network I've been told it's my upload speed that is causing the issues. So the cycle continues, the last test I did, I ensured there was nothing being uploaded and no other machine/device connected to my wifi/network yet the problem persists, right now I've given up trying to convince you there's some strange problem with your network as you guys seem to treat it as a red herring.

So I have to say I'm glad this problem is being experienced by other users now. Good luck trying to brush it off...
 
Last edited:
internet is the worst it has ever been since friday on both accounts and it looks like an ipc issue
looks like they are throttling as well to keep latency down
it is time now for a worst isp of the year award
i hope they will fix the problems and stop playing for time
 
LaraC said:
Did the same test.
Click to expand...

Where are you located?

Performance is now the worst I've had.

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=118 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=289 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=170 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=98 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=160 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=179 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=248 ms



Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 70 ms
Request timed out *
2 Request timed out *
41.170.79.2 157 ms
3 196.223.14.3 27 ms
41.160.2.3 93 ms
4 197.242.144.1 50 ms
196.44.0.2 124 ms
5 196.30.1.5 88 ms
6 196.31.220.2 39 ms
7 196.30.42.1 202 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms
Request timed out *
2 Request timed out *
169.1.1.2 119 ms
3 169.1.1.2 139 ms
41.170.79.2 92 ms
4 41.170.79.2 212 ms
72.14.239.1 51 ms
5 72.14.239.1 227 ms
8.8.8.8 74 ms
 
al4bb said:
Where are you located?
Click to expand...
Account type: 10Mbps Home Capped
Location: Despatch, Eastern Cape

Test results:
Code: 
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 197.242.144.102

Pinging 197.242.144.102 with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=51ms TTL=56
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56
Reply from 197.242.144.102: bytes=32 time=55ms TTL=56

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 50ms, Maximum = 55ms, Average = 51ms

C:\Users\Lara>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=46ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 45ms, Maximum = 46ms, Average = 45ms

C:\Users\Lara>tracert 197.242.144.102

Tracing route to cms-gm.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    42 ms    40 ms    40 ms  169-1-1-249.ip.afrihost.co.za [169.1.1.249]
  4    41 ms    40 ms    40 ms  169-1-1-250.ip.afrihost.co.za [169.1.1.250]
  5    45 ms    45 ms    44 ms  41.170.79.236
  6    45 ms    45 ms    46 ms  41.160.2.33
  7    48 ms    49 ms    47 ms  mtnns-2.jinx.net.za [196.223.14.31]
  8    49 ms    51 ms    49 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223]
  9    44 ms    44 ms    43 ms  196.44.31.99
 10    44 ms    44 ms    44 ms  196.30.1.39
 11    49 ms    49 ms    49 ms  196.31.220.21
 12    48 ms    49 ms    49 ms  196.31.63.202
 13     *       50 ms    48 ms  vl9-ah-ha-1.za.mtnbusiness.net [196.30.42.132]
 14    48 ms    49 ms    49 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
@ electrofreeze and fishfly

It is very frustrating not to get answers but it is just as frustrating to give answers to question if it isn’t asked properly.

I believe the aim of this thread was for testers to post their result and not just for them to mention poor performance. Posting trace routes and ping tests provide data which can be followed up. It can also be tested by another forumite for comparison purposes. (Something I like to do)

ps. You should post stats the moment you experience bad connectivity.
 
al4bb said:
Where are you located?

Performance is now the worst I've had.

Code: 
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=118 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=289 ms
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5

Code: 
ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=170 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=98 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=160 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=179 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=248 ms

Trace Test:

Code: 
traceroute -n 197.242.144.102

  1	192.168.1.1       	70 ms     	
   	Request timed out 	*         	
  2	Request timed out 	*         	
   	41.170.79.2       	157 ms    	
  3	196.223.14.3      	27 ms     	
   	41.160.2.3        	93 ms     	
  4	197.242.144.1     	50 ms     	
   	196.44.0.2        	124 ms    	
  5	196.30.1.5        	88 ms     	
  6	196.31.220.2      	39 ms     	
  7	196.30.42.1       	202 ms
Code: 
traceroute -n 8.8.8.8

  1	192.168.1.1       	1 ms      	
   	Request timed out 	*         	
  2	Request timed out 	*         	
   	169.1.1.2         	119 ms    	
  3	169.1.1.2         	139 ms    	
   	41.170.79.2       	92 ms     	
  4	41.170.79.2       	212 ms    	
   	72.14.239.1       	51 ms     	
  5	72.14.239.1       	227 ms    	
   	8.8.8.8           	74 ms
Click to expand...

Me pinging the same address:

Code: 
Pinging 197.242.144.102 with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=101ms TTL=56
Reply from 197.242.144.102: bytes=32 time=525ms TTL=56
Reply from 197.242.144.102: bytes=32 time=953ms TTL=56
Reply from 197.242.144.102: bytes=32 time=613ms TTL=56

Ping statistics for 197.242.144.102:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 101ms, Maximum = 953ms, Average = 548ms
Code: 
Tracing route to cms-gm.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

  1     1 ms   2 ms     1 ms     home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3   170 ms   185 ms    37 ms  169-1-1-237.ip.afrihost.co.za [169.1.1.237]
  4   210 ms    41 ms   267 ms  169-1-1-238.ip.afrihost.co.za [169.1.1.238]
  5    71 ms    35 ms   270 ms  41.170.79.236
  6   498 ms   615 ms   814 ms  41.160.2.33
  7   170 ms   224 ms   395 ms  mtnns-2.jinx.net.za [196.223.14.31]
  8    60 ms    87 ms    54 ms  jh-cr-2.za--jh-pr-1.za.mtnns.net [196.44.0.223] 
  9    39 ms   920 ms   408 ms  196.44.31.99
 10    39 ms   797 ms   205 ms  196.31.220.8
 11   536 ms   511 ms   611 ms  196.31.220.27
 12    57 ms   683 ms   509 ms  196.31.63.202
 13   327 ms   720 ms   710 ms  vl9-ah-ha-1.za.mtnbusiness.net [196.30.42.132]
 14    45 ms  1087 ms   307 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Me pinging Vienna.
Code: 
Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=512ms TTL=46
Reply from 194.183.128.94: bytes=32 time=278ms TTL=46
Reply from 194.183.128.94: bytes=32 time=819ms TTL=46
Reply from 194.183.128.94: bytes=32 time=430ms TTL=46

Ping statistics for 194.183.128.94:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 278ms, Maximum = 819ms, Average = 509ms
Code: 
Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1     1 ms   2 ms   3 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3   654 ms   814 ms   619 ms  169-1-1-237.ip.afrihost.co.za [169.1.1.237]
  4   834 ms   509 ms   920 ms  169-1-1-238.ip.afrihost.co.za [169.1.1.238]
  5   548 ms   807 ms   294 ms  41.170.79.236
  6   163 ms   657 ms   320 ms  41.160.2.33
  7   331 ms   306 ms   303 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  8  1154 ms   221 ms   565 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
  9  ^C
 
DonaldMickey said:
You don't say? Why do you think so many people are complaining.
Click to expand...
I know that there are problems with the network. Even I experienced slow downloads at times. It is however not crippling like it is for some. It is still good to post your tests which Afrihost can analyse to find why some have great connectivity and others not.
 
LaraC said:
@ electrofreeze and fishfly

It is very frustrating not to get answers but it is just as frustrating to give answers to question if it isn’t asked properly.

I believe the aim of this thread was for testers to post their result and not just for them to mention poor performance. Posting trace routes and ping tests provide data which can be followed up. It can also be tested by another forumite for comparison purposes. (Something I like to do)

ps. You should post stats the moment you experience bad connectivity.
Click to expand...

LaraC it's not about the poor performance - that I can deal with, my problem is that there is something going on with the AH and Afrigreen network - Either they are shaping/throttling the services or there is a genuine issue they not willing to investigate. Either or stringing along the few customers that's willing to try test the POC and provide feedback is not the way they should run their business... if I wasn't waiting for fibre - so I can cancel completely - I don't wanted to deal with the hassle of moving my line off AH back to Telkom then I would have cancelled my services months ago...
 
Last edited:
LaraC said:
@ electrofreeze and fishfly

It is very frustrating not to get answers but it is just as frustrating to give answers to question if it isn’t asked properly.

I believe the aim of this thread was for testers to post their result and not just for them to mention poor performance. Posting trace routes and ping tests provide data which can be followed up. It can also be tested by another forumite for comparison purposes. (Something I like to do)

ps. You should post stats the moment you experience bad connectivity.
Click to expand...

we have given them enough stats and nothing happened or improved and we know many other people with the same problems
this is not about the problems of 1 person it is about a bad network that they know about and are playing for time and trying to hide it
there is no other isp that has so many problems in so few days that has been going on for so long
 
LaraC said:
I know that there are problems with the network. Even I experienced slow downloads at times. It is however not crippling like it is for some. It is still good to post your tests which Afrihost can analyse to find why some have great connectivity and others not.
Click to expand...

The only thing that seems to come from the analysis is more excuses i.e. "I never saw anything when I was testing", "you shouldn't be seeing results like that" etc.

Get told to give speedtests (which we do) and get told "it isn't a good indicator of real world performance".

And then the ultimate:
We get told to test with another isp and then when we post reaults we get told "oh could be that the port got reset and that is why the results are better".

Sorry for the rant but I am just getting really gatvol of this s***.
My patience is wearing very thin.
 
@ DonaldMickey, electrofreeze and fishfly
All I can say is that I wish your network experience improves.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X