Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Had some issues this week with the green and failed connections just had to guide my mother over the phone to change back to normal @afrihost.co.za not sure what the issue was as im unable to run some proper tests my side but shall do so this weekend and report back.

Other than these past days the @afrigreen was working amazing.
 
AfriMan said:
Just a heads up.

Some changes being implemented that may result in a few minutes of downtime.

Shouldn't be long :)
Click to expand...

Why don't you guys send an e-mail to those on the network about 10 minutes beforehand? It will result in a reduced number of complaints.
 
Im getting packet loss on the network today. Seems like it was better at first, but now it reminds me of the old network.
 
Pete_A said:
Im getting packet loss on the network today. Seems like it was better at first, but now it reminds me of the old network.
Click to expand...

They just said they are implementing changes right now, so you will experience problems for a little bit.
 
Johnatan56 said:
Why don't you guys send an e-mail to those on the network about 10 minutes beforehand? It will result in a reduced number of complaints.
Click to expand...

Mail isn't the best communication for these kind of changes as they're sporadic and will happen multiple times a day. The more time passes the less amount of tweaks will be needed that require the network be offline :)
 
I'm seriously getting fed up now. Not only have I given my contact details to have my issue dealt with, and this has not happened, but for the first time last night I was ACTUALLY able to use Afrigreen with NO timeouts. But, as I expected, the bull**** started happening again this morning. Not only do the tests I post seem to be ignored in this thread, but my patience is seriously running thin now, and I'm absolutely fed up with this shocking service.

If the so called problem is on my side, and I haven't changed ANYTHING, why was I able to use Afrigreen fine last night, but now I can't? I see plenty of complaints about time outs, packet loss and poor throughput in general from quite a few people here, but issues just get dismissed because you don't 'see' it on your side. I've been trying really hard to be patient with this test network, but seriously, what are we paying you for? Both of my Afrihost accounts are useless as of now and I'm beyond tired of waiting, and waiting, and waiting still, for something to come right.

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 41.170.79.229
4 21 ms 20 ms 54 ms 41.170.79.230
5 * 19 ms 20 ms 41.170.79.236
6 21 ms 20 ms 20 ms 41.160.2.33
7 23 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 23 ms 23 ms * jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 * 22 ms 22 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
10 23 ms 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]
11 22 ms 22 ms 23 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
 
isabelladol said:
Tracing route to afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 41.170.79.229
4 21 ms 20 ms 54 ms 41.170.79.230
5 * 19 ms 20 ms 41.170.79.236
6 21 ms 20 ms 20 ms 41.160.2.33
7 23 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 23 ms 23 ms * jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 * 22 ms 22 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
10 23 ms 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]
11 22 ms 22 ms 23 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
Click to expand...

I dont see an issue?
 
Afrinormal
t9iDsqZ.png


Afrigreen
TjnrsG6.png


Aside from the patchyness last night, thumbs up.
 
isabelladol said:
I'm seriously getting fed up now. Not only have I given my contact details to have my issue dealt with, and this has not happened, but for the first time last night I was ACTUALLY able to use Afrigreen with NO timeouts. But, as I expected, the bull**** started happening again this morning. Not only do the tests I post seem to be ignored in this thread, but my patience is seriously running thin now, and I'm absolutely fed up with this shocking service.

If the so called problem is on my side, and I haven't changed ANYTHING, why was I able to use Afrigreen fine last night, but now I can't? I see plenty of complaints about time outs, packet loss and poor throughput in general from quite a few people here, but issues just get dismissed because you don't 'see' it on your side. I've been trying really hard to be patient with this test network, but seriously, what are we paying you for? Both of my Afrihost accounts are useless as of now and I'm beyond tired of waiting, and waiting, and waiting still, for something to come right.

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 41.170.79.229
4 21 ms 20 ms 54 ms 41.170.79.230
5 * 19 ms 20 ms 41.170.79.236
6 21 ms 20 ms 20 ms 41.160.2.33
7 23 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 23 ms 23 ms * jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 * 22 ms 22 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
10 23 ms 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]
11 22 ms 22 ms 23 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
Click to expand...

You were definitely scheduled to receive a call. I'll follow up on that.

In terms of results, the main thing is that we need to recreate results. Being on one IPC means that we should all be getting the same experience, aside from backhaul issues. But then every Durban client will have a similar experience, Cape Town, etc. We definitely don't want to dismiss feedback, it's all very helpful, but we need to isolate anomalies from general issues so we don't end up on a wild goose chase.
 
Rickster said:
I dont see an issue?
Click to expand...

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 41.170.79.229
4 21 ms 20 ms 54 ms 41.170.79.230
5 * 19 ms 20 ms 41.170.79.236
6 21 ms 20 ms 20 ms 41.160.2.33
7 23 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 23 ms 23 ms * jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 * 22 ms 22 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
10 23 ms 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
11 22 ms 22 ms 23 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 20 ms 20 ms 41.170.79.229
4 22 ms 19 ms 19 ms 41.170.79.230
5 * 19 ms 19 ms 41.170.79.236
6 20 ms 20 ms 20 ms 41.160.2.33
7 22 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 * * 23 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
9 * 45 ms * jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
10 * 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
11 22 ms 22 ms 22 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Not the timeouts to a local site. This causes webpages to take over 10 seconds to load. On international sites like this:

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 24 ms 41.170.79.229
4 24 ms 24 ms 19 ms 41.170.79.230
5 20 ms 20 ms 20 ms 41.170.79.236
6 20 ms * 20 ms 41.160.2.33
7 20 ms 56 ms 31 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [2
16.6.55.37]
8 * 303 ms 268 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 628 ms 465 ms 412 ms if-0-1-1.core2.PV9-Lisbon.as6453.net [41.206.164.65]
10 796 ms 715 ms 692 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 905 ms 868 ms 792 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 670 ms 584 ms 786 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 * 345 ms 250 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139
.42]
14 * 494 ms 259 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
15 * 344 ms 406 ms 195.219.83.26
16 362 ms 336 ms 211 ms ae5.mpr2.lhr2.uk.zip.zayo.com [64.125.21.9]
17 439 ms 440 ms 365 ms v113.ae29.cr1.lga5.us.zip.zayo.com [64.125.30.10
8]
18 330 ms 268 ms * ae2.er3.lga5.us.zip.zayo.com [64.125.31.214]
19 411 ms 320 ms * 128.177.165.234.IPYX-100687-870-ZYO.zip.zayo.comv[128.177.165.234]
20 280 ms 576 ms 336 ms be1.bb01.lga1.tfbnw.net [204.15.20.190]
21 286 ms 263 ms 263 ms ae15.bb03.dca1.tfbnw.net [74.119.76.20]
22 280 ms 279 ms 329 ms be21.bb01.frc3.tfbnw.net [31.13.30.223]
23 280 ms 281 ms 280 ms ae60.dr03.frc3.tfbnw.net [74.119.79.11]
24 * * * Request timed out.
25 * * * Request timed out.
26 280 ms 280 ms 280 ms edge-star-shv-12-frc3.facebook.com [173.252.120.6]

Time outs alone make any service unusable.
 
AfriMan said:
You were definitely scheduled to receive a call. I'll follow up on that.

In terms of results, the main thing is that we need to recreate results. Being on one IPC means that we should all be getting the same experience, aside from backhaul issues. But then every Durban client will have a similar experience, Cape Town, etc. We definitely don't want to dismiss feedback, it's all very helpful, but we need to isolate anomalies from general issues so we don't end up on a wild goose chase.
Click to expand...

I don't understand how this can't be related to the network directly. Just browsing through this thread I see more than a hand full of people complaining of timeouts and packet loss as well. I'm not the only one.
 
isabelladol said:
Tracing route to afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 21 ms 41.170.79.229
4 21 ms 20 ms 54 ms 41.170.79.230
5 * 19 ms 20 ms 41.170.79.236
6 21 ms 20 ms 20 ms 41.160.2.33
7 23 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 23 ms 23 ms * jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 * 22 ms 22 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
10 23 ms 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
11 22 ms 22 ms 23 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 20 ms 20 ms 41.170.79.229
4 22 ms 19 ms 19 ms 41.170.79.230
5 * 19 ms 19 ms 41.170.79.236
6 20 ms 20 ms 20 ms 41.160.2.33
7 22 ms 22 ms 22 ms mtnns-2.jinx.net.za [196.223.14.31]
8 * * 23 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
9 * 45 ms * jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
10 * 22 ms * 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]
11 22 ms 22 ms 22 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Not the timeouts to a local site. This causes webpages to take over 10 seconds to load. On international sites like this:

Tracing route to facebook.com [173.252.120.6]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 21 ms 21 ms 24 ms 41.170.79.229
4 24 ms 24 ms 19 ms 41.170.79.230
5 20 ms 20 ms 20 ms 41.170.79.236
6 20 ms * 20 ms 41.160.2.33
7 20 ms 56 ms 31 ms ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [2
16.6.55.37]
8 * 303 ms 268 ms if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 628 ms 465 ms 412 ms if-0-1-1.core2.PV9-Lisbon.as6453.net [41.206.164.65]
10 796 ms 715 ms 692 ms if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
11 905 ms 868 ms 792 ms if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 670 ms 584 ms 786 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 * 345 ms 250 ms if-11-2.tcore1.L78-London.as6453.net [80.231.139
.42]
14 * 494 ms 259 ms if-17-2.tcore1.LDN-London.as6453.net [80.231.130
.130]
15 * 344 ms 406 ms 195.219.83.26
16 362 ms 336 ms 211 ms ae5.mpr2.lhr2.uk.zip.zayo.com [64.125.21.9]
17 439 ms 440 ms 365 ms v113.ae29.cr1.lga5.us.zip.zayo.com [64.125.30.10
8]
18 330 ms 268 ms * ae2.er3.lga5.us.zip.zayo.com [64.125.31.214]
19 411 ms 320 ms * 128.177.165.234.IPYX-100687-870-ZYO.zip.zayo.comv[128.177.165.234]
20 280 ms 576 ms 336 ms be1.bb01.lga1.tfbnw.net [204.15.20.190]
21 286 ms 263 ms 263 ms ae15.bb03.dca1.tfbnw.net [74.119.76.20]
22 280 ms 279 ms 329 ms be21.bb01.frc3.tfbnw.net [31.13.30.223]
23 280 ms 281 ms 280 ms ae60.dr03.frc3.tfbnw.net [74.119.79.11]
24 * * * Request timed out.
25 * * * Request timed out.
26 280 ms 280 ms 280 ms edge-star-shv-12-frc3.facebook.com [173.252.120.6]

Time outs alone make any service unusable.
Click to expand...

This is what I'm seeing

traceroute to facebook.com (173.252.120.6), 64 hops max, 52 byte packets
1 router (192.168.1.1) 4.797 ms 0.733 ms 0.708 ms
2 * * *
3 41.170.79.229 (41.170.79.229) 15.792 ms 14.000 ms 13.717 ms
4 41.170.79.230 (41.170.79.230) 14.866 ms 13.768 ms 13.479 ms
5 41.170.79.236 (41.170.79.236) 13.785 ms 14.631 ms 14.257 ms
6 41.160.2.33 (41.160.2.33) 14.033 ms 14.492 ms 13.568 ms
7 ix-0-3-0-0.tcore1.jso-johannesburg.as6453.net (216.6.55.37) 14.956 ms 14.075 ms 14.652 ms
8 if-4-2.tcore1.klt-cape-town.as6453.net (41.206.178.2) 193.726 ms 191.406 ms 193.307 ms
9 if-1-0-0-3.core2.pv9-lisbon.as6453.net (195.219.214.34) 288.735 ms 354.263 ms 296.145 ms
10 if-0-0-0-2000.tcore1.pv9-lisbon.as6453.net (80.231.158.1) 190.246 ms 190.386 ms 189.620 ms
11 if-1-3.tcore1.sv8-highbridge.as6453.net (80.231.158.30) 192.151 ms 193.742 ms 222.202 ms
12 if-19-2.tcore2.l78-london.as6453.net (80.231.138.22) 191.291 ms 193.871 ms 194.245 ms
13 if-11-2.tcore1.l78-london.as6453.net (80.231.139.42) 191.513 ms
if-2-2.tcore1.l78-london.as6453.net (80.231.131.2) 187.435 ms
if-11-2.tcore1.l78-london.as6453.net (80.231.139.42) 194.767 ms
14 if-17-2.tcore1.ldn-london.as6453.net (80.231.130.130) 193.769 ms 196.473 ms 193.620 ms
15 195.219.83.26 (195.219.83.26) 187.073 ms 190.746 ms 212.217 ms
16 ae5.mpr2.lhr2.uk.zip.zayo.com (64.125.21.9) 192.726 ms 194.944 ms 190.589 ms
17 v113.ae29.cr1.lga5.us.zip.zayo.com (64.125.30.108) 247.813 ms 250.983 ms 247.486 ms
18 ae2.er3.lga5.us.zip.zayo.com (64.125.31.214) 254.353 ms 256.746 ms 254.506 ms
19 128.177.165.234.ipyx-100687-870-zyo.zip.zayo.com (128.177.165.234) 251.086 ms 252.468 ms 251.428 ms
20 be1.bb01.lga1.tfbnw.net (204.15.20.190) 273.214 ms 274.454 ms 274.545 ms
21 be29.bb02.dca1.tfbnw.net (74.119.78.164) 273.427 ms
be29.bb01.dca1.tfbnw.net (74.119.78.78) 270.085 ms 271.268 ms
22 ae11.bb03.frc3.tfbnw.net (31.13.31.249) 272.079 ms
ae11.bb04.frc3.tfbnw.net (204.15.20.75) 280.413 ms
ae18.bb03.frc3.tfbnw.net (74.119.77.219) 270.955 ms
23 ae60.dr01.frc3.tfbnw.net (204.15.23.247) 271.889 ms
ae29.dr06.frc3.tfbnw.net (31.13.27.163) 276.008 ms
ae62.dr01.frc3.tfbnw.net (173.252.65.101) 267.243 ms
24 * * *
25 * * *
26 edge-star-shv-12-frc3.facebook.com (173.252.120.6) 273.661 ms 270.691 ms 270.540 ms

6vHfgSP.png


I'm not saying you're not experiencing what you clearly are. But let's figure out what's different between your experience and mine and let's see if we can eliminate everything until we get to the differentiator.
 
Here we go:


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.0.1
2 * * * Request timed out.
3 32 ms 119 ms 31 ms 41.170.79.229
4 31 ms 30 ms 30 ms 41.170.79.230
5 32 ms 32 ms 32 ms 41.170.79.236
6 30 ms 30 ms 29 ms 41.160.2.33
7 33 ms 32 ms 34 ms mtnns-2.jinx.net.za [196.223.14.31]
8 35 ms 35 ms 35 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]

9 41 ms 35 ms 34 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
10 33 ms 33 ms 33 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X