Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
The More Info link takes you to the Network Management page that gives a breakdown of how shaping will be applied to the Home Uncapped, Premium Uncapped, Business Uncapped and Shaped Capped accounts.

So if I click on the banner that says:
View attachment 406472

It is taking me to the Home Uncapped, Premium Uncapped, Business Uncapped and Shaped Capped accounts?
That makes less sense than changing the account name on the fly rather than ending double data.
 
So if I click on the banner that says:
View attachment 406472

It is taking me to the Home Uncapped, Premium Uncapped, Business Uncapped and Shaped Capped accounts?
That makes less sense than changing the account name on the fly rather than ending double data.

The button just says More Info... And that's exactly what it's doing. It's providing a breakdown of the differences between the Shaped products.
 
The button just says More Info... And that's exactly what it's doing. It's providing a breakdown of the differences between the Shaped products.

well it clearly states "Guaranteed Unshaped capped data at all times" then the more info button takes you to info on an entirely different product? How does that make sense to any one other than your marketing team?
 
I think what what afrihost should have done is added free time data and unshaped priority including double data to it afrihost plus addon it would made things more simpler.

For example take for instance starting at 100gb going for R99 and then add afrihost plus and it becomes unshaped and double data with now total 200gb and 18 hours of free data you then pay R199pm

That's one way we could have gone.

At the end of the day it's about providing our Clients with the product that they want to use. Plus+ is awesome but's a way to add additional value. :)
 
well it clearly states "Guaranteed Unshaped capped data at all times" then the more info button takes you to info on an entirely different product? How does that make sense to any one other than your marketing team?

I'll be sure to pass on your feedback to the Team that worked on this. :)
 
I'll be sure to pass on your feedback to the Team that worked on this. :)

Well I fortunately saw this cumming and baled out at the end of November, but several of my clients are still with you.
As I am away on leave for 3 weeks starting tomorrow, they will all have to phone you rather than me, so good luck explaining it to non technical people who think thay are paying for an unshaped capped account.
Especially when you tell them that they will have to change packages to continue getting what they bought from you several years ago.
As most of them are already dissatisfied with the Afrihost issues in the South, especially after 6pm, I hope you dont lose too many of them.
 
Well I fortunately saw this cumming and baled out at the end of November, but several of my clients are still with you.
As I am away on leave for 3 weeks starting tomorrow, they will all have to phone you rather than me, so good luck explaining it to non technical people who think thay are paying for an unshaped capped account.
Especially when you tell them that they will have to change packages to continue getting what they bought from you several years ago.
As most of them are already dissatisfied with the Afrihost issues in the South, especially after 6pm, I hope you dont lose too many of them.

It's a top priority for us to ensure that our Team is prepared to assist our Clients with any queries with regards to the new packages.

I'm pretty confident that your and our Clients will continue to have a similar experience in January to what they are having now on our Capped accounts. :)
 
As requested, comparison between webafrica and afrihost:


Afrihost

Ping statistics for 46.4.100.209:
Packets: Sent = 76, Received = 75, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 315ms, Average = 252ms

Webafrica

Ping statistics for 46.4.100.209:
Packets: Sent = 241, Received = 241, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 211ms, Average = 181ms


to bras.afrihost.com

Afrihost
Ping statistics for 155.239.255.250:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 83ms, Average = 56ms

Webafrica
Ping statistics for 155.239.255.250:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 28ms, Average = 16ms


Traceroute via afrihost

Tracing route to static.209.100.4.46.clients.your-server.de [46.4.100.209]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 76 ms 17 ms 16 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 105 ms 102 ms 101 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 72 ms 80 ms 78 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 18 ms 39 ms 41.164.52.40
7 17 ms 16 ms 17 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
8 428 ms 280 ms 255 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
9 289 ms 295 ms 304 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
10 247 ms 246 ms 246 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
11 246 ms 219 ms 229 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
12 278 ms 237 ms 184 ms if-ae-7-2.tcore2.FNM-Frankfurt.as6453.net [80.231.200.78]
13 243 ms 196 ms 248 ms if-ae-4-2.tcore1.FR0-Frankfurt.as6453.net [195.219.87.18]
14 246 ms 236 ms 237 ms 195.219.219.10
15 258 ms 276 ms 306 ms core22.hetzner.de [213.239.245.17]
16 230 ms 237 ms 238 ms ex9k2.rz14.hetzner.de [213.239.229.118]
17 230 ms 244 ms 262 ms static.209.100.4.46.clients.your-server.de [46.4.100.209]

Trace complete.

Via Webafrica
Tracing route to static.209.100.4.46.clients.your-server.de [46.4.100.209]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 26 ms 26 ms 196.38.75.70
4 19 ms 28 ms 16 ms 196.38.75.69
5 19 ms 28 ms 16 ms 196.35.115.128
6 17 ms 16 ms 20 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
7 16 ms 16 ms 16 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
8 172 ms 173 ms 172 ms core1b-dock-ge-0-4-2-2.ip.isnet.net [168.209.201.13]
9 178 ms 177 ms 176 ms ae1-0.lon10.core-backbone.com [195.66.224.238]
10 181 ms 177 ms 177 ms ae2-2077.fra20.core-backbone.com [5.56.18.1]
11 172 ms 173 ms 173 ms core-backbone-100g-fra.hetzner.de [80.255.15.122]
12 173 ms 174 ms 174 ms core1.hetzner.de [213.239.245.9]
13 171 ms 172 ms 171 ms core22.hetzner.de [213.239.245.178]
14 176 ms 177 ms 182 ms ex9k2.rz14.hetzner.de [213.239.229.118]
15 176 ms 176 ms 176 ms static.209.100.4.46.clients.your-server.de [46.4.100.209]

Trace complete.


The webafrica ones were taken after being connected. At this point I literally can't play for more than 5 minutes without timing out on Afrihost in the evenings.
 
Does that include the constant congestion, packet loss, and latency every, single, night?

If you're not having a great experience then we definitely need to look into it and find out what's happening to cause it! :(
 
As requested, comparison between webafrica and afrihost:


Afrihost

Ping statistics for 46.4.100.209:
Packets: Sent = 76, Received = 75, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 315ms, Average = 252ms

Webafrica

Ping statistics for 46.4.100.209:
Packets: Sent = 241, Received = 241, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 211ms, Average = 181ms


to bras.afrihost.com

Afrihost
Ping statistics for 155.239.255.250:
Packets: Sent = 38, Received = 38, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 83ms, Average = 56ms

Webafrica
Ping statistics for 155.239.255.250:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 28ms, Average = 16ms


Traceroute via afrihost

Tracing route to static.209.100.4.46.clients.your-server.de [46.4.100.209]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 76 ms 17 ms 16 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 105 ms 102 ms 101 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 72 ms 80 ms 78 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 15 ms 18 ms 39 ms 41.164.52.40
7 17 ms 16 ms 17 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
8 428 ms 280 ms 255 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
9 289 ms 295 ms 304 ms if-ae-7-2.tcore2.WV6-Madrid.as6453.net [80.231.159.30]
10 247 ms 246 ms 246 ms if-ae-11-2.tcore1.WV6-Madrid.as6453.net [80.231.91.65]
11 246 ms 219 ms 229 ms if-ae-5-2.tcore2.WYN-Marseille.as6453.net [80.231.200.5]
12 278 ms 237 ms 184 ms if-ae-7-2.tcore2.FNM-Frankfurt.as6453.net [80.231.200.78]
13 243 ms 196 ms 248 ms if-ae-4-2.tcore1.FR0-Frankfurt.as6453.net [195.219.87.18]
14 246 ms 236 ms 237 ms 195.219.219.10
15 258 ms 276 ms 306 ms core22.hetzner.de [213.239.245.17]
16 230 ms 237 ms 238 ms ex9k2.rz14.hetzner.de [213.239.229.118]
17 230 ms 244 ms 262 ms static.209.100.4.46.clients.your-server.de [46.4.100.209]

Trace complete.

Via Webafrica
Tracing route to static.209.100.4.46.clients.your-server.de [46.4.100.209]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 26 ms 26 ms 196.38.75.70
4 19 ms 28 ms 16 ms 196.38.75.69
5 19 ms 28 ms 16 ms 196.35.115.128
6 17 ms 16 ms 20 ms mi-za-cpt-p8-te0-7-0-0.ip.isnet.net [168.209.2.13]
7 16 ms 16 ms 16 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
8 172 ms 173 ms 172 ms core1b-dock-ge-0-4-2-2.ip.isnet.net [168.209.201.13]
9 178 ms 177 ms 176 ms ae1-0.lon10.core-backbone.com [195.66.224.238]
10 181 ms 177 ms 177 ms ae2-2077.fra20.core-backbone.com [5.56.18.1]
11 172 ms 173 ms 173 ms core-backbone-100g-fra.hetzner.de [80.255.15.122]
12 173 ms 174 ms 174 ms core1.hetzner.de [213.239.245.9]
13 171 ms 172 ms 171 ms core22.hetzner.de [213.239.245.178]
14 176 ms 177 ms 182 ms ex9k2.rz14.hetzner.de [213.239.229.118]
15 176 ms 176 ms 176 ms static.209.100.4.46.clients.your-server.de [46.4.100.209]

Trace complete.


The webafrica ones were taken after being connected. At this point I literally can't play for more than 5 minutes without timing out on Afrihost in the evenings.

Were you able to test an extended gaming session on your Web Africa account?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X