Afrihost Mobile Feedback Thread

Status
Not open for further replies.
AfriFella said:
Morning guys! I understand that there has been some frustration around your Mobile Connections, but, this is still an Afrihost thread and if could keep discussions primarily around Afrihost products, that would be great. :)
Click to expand...

First of all the issues in the last month is unacceptable, I had to switch to cellc just to get my work done :(.


Do you think the issues we been having is fair ? Do you think its fair that way PAY afrihost for a service and not get what we pay for or get told on some issues we have to talk to MTN.? I don't pay mtn a cent.

So that is why I discussed alternative options because your AFRIMOBILE was not working as it should and it got to the point where I can't do my work and it effects my, other peoples income
 
airborne said:
Spot on, also I don't like having to say this, they seem like helpful guys but Afrihost reps on the forum largely are just doing lip service in regard to support on their mobile products. I was offline for 4 days, they did zip despite me pming both reps. Seems to be the case for many others, you just have to sweat it out till the problem mysteriously goes away.

From the way I see it Afrihost is out of their competency with their mobile offering, they can't actively support the product other than relaying the complaints to their Mtn partners.

Prime example of this is no one at Afrihost actually knows or can explain what has been affecting the mobile network.
Click to expand...
You would think they would start the thread by explaining what happened but no...
 
Radio silence from Afrihost again after everyone's response to the post asking (very nicely, it must be said) that we don't mention alternatives to MTN.

Come on Afrihost, let's have some real answers now. You guys do a really good job of customer service, so I'm guessing that the problem is a lack of feedback or effort from MTN to you?

Else we'll carry on talking about the other guys... :)
 
Stevewarren said:
Getting 80% packet loss now. Just tell me you are working on it or just acknowledge the problem. I'm sick of hearing that it's been fixed and we have refreshed your number or tho fill out a coverage form to send to MTN. I have sent you more than enough test results proving that it's not a coverage issue.
Click to expand...

Sorry to hear :(
I'm taking a look at your PM now and will revert with feedback there.
 
airborne said:
Spot on, also I don't like having to say this, they seem like helpful guys but Afrihost reps on the forum largely are just doing lip service in regard to support on their mobile products. I was offline for 4 days, they did zip despite me pming both reps. Seems to be the case for many others, you just have to sweat it out till the problem mysteriously goes away.

From the way I see it Afrihost is out of their competency with their mobile offering, they can't actively support the product other than relaying the complaints to their Mtn partners.

Prime example of this is no one at Afrihost actually knows or can explain what has been affecting the mobile network.
Click to expand...

I think there are a lot of assumption here around how we work and what was done on your specific query.
Sure, there have been issues - but saying we're only here to copy paste and not do much couldn't be further from the truth.

PM me if you'd like to continue the conversation.
 
DTBA said:
First of all the issues in the last month is unacceptable, I had to switch to cellc just to get my work done :(.


Do you think the issues we been having is fair ? Do you think its fair that way PAY afrihost for a service and not get what we pay for or get told on some issues we have to talk to MTN.? I don't pay mtn a cent.

So that is why I discussed alternative options because your AFRIMOBILE was not working as it should and it got to the point where I can't do my work and it effects my, other peoples income
Click to expand...

Fully understand your frustrations, there have been long standing issues in the area - of which both MTN and ourselves have worked on to be resolved.

Backing up what AfriFella brought up though, this thread is here for feedback - any other conversation needs to happen outside of the thread so we can better log the requests and support you guys properly.
 
lotus123 said:
Radio silence from Afrihost again after everyone's response to the post asking (very nicely, it must be said) that we don't mention alternatives to MTN.

Come on Afrihost, let's have some real answers now. You guys do a really good job of customer service, so I'm guessing that the problem is a lack of feedback or effort from MTN to you?

Else we'll carry on talking about the other guys... :)
Click to expand...

We're here :)
Monday's are always pretty busy for the team, we've got a lot of weekend catch-up, the weeks planning etc etc.

The technical issues from last week are resolved - the cause was listed as a mis-config on some hardware, which was attended to and resolved.
 
Afriguy just told me he can't see the difference between these.

Afrihost APN ping test

C:\Users\Steve>ping -n 100 -l 1000 google.com

Pinging google.com [66.8.14.221] with 1000 bytes of data:
Reply from 66.8.14.221: bytes=1000 time=672ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=147ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 66.8.14.221: bytes=1000 time=704ms TTL=52
Request timed out.
Reply from 66.8.14.221: bytes=1000 time=684ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=150ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=140ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=157ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=145ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=137ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=148ms TTL=52
Reply from 66.8.14.221: bytes=1000 time=144ms TTL=52

Ping statistics for 66.8.14.221:
Packets: Sent = 100, Received = 11, Lost = 89 (89% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 704ms, Average = 293ms


MTN internet APN ping test

C:\Users\Steve>ping -n 100 -l 1000 google.com

Pinging google.com [66.8.14.219] with 1000 bytes of data:
Request timed out.
Request timed out.
Reply from 66.8.14.219: bytes=1000 time=724ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=133ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=132ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=149ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=137ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=151ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=143ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=96ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=134ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=152ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=134ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=144ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=152ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=147ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=146ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=142ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=136ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=141ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=155ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=133ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=139ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=139ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=136ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=141ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=137ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=1863ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=207ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=123ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=141ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=132ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=116ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=157ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=134ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=147ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=142ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=124ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=136ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=156ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=147ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=156ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=125ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=136ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=152ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=125ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=172ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=137ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=145ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=144ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=132ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=143ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=140ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=142ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=139ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=146ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=143ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=126ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=138ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=131ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=132ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=128ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=142ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=149ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=132ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=138ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=137ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=160ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=137ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=133ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=149ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=140ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=126ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=135ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=146ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=96ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=140ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=155ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=139ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=129ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=136ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=133ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=130ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=121ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=127ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=133ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=142ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=148ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=145ms TTL=50
Reply from 66.8.14.219: bytes=1000 time=140ms TTL=50

Ping statistics for 66.8.14.219:
Packets: Sent = 100, Received = 98, Lost = 2 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 1863ms, Average = 162ms
 
Trace Route tests

Afrihost APN


C:\Users\Steve>tracert google.com

Tracing route to google.com [66.8.14.221]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 538 ms 258 ms 279 ms 192.168.75.18
4 * * * Request timed out.
5 * * * Request timed out.
6 273 ms 318 ms 318 ms ct-cr-3--tb-dca-3.za.mtnbusiness.net [196.44.29.188]
7 * * * Request timed out.
8 1053 ms 317 ms 318 ms tb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.135]
9 233 ms 258 ms 278 ms qston-cpt-1.mtnns.net [196.44.18.3]
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 * 624 ms * 66.8.14.221
25 * 1483 ms 288 ms 66.8.14.221

Trace complete.

MTN internet APN

C:\Users\Steve>tracert google.com

Tracing route to google.com [66.8.14.222]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 722 ms 309 ms 277 ms 10.110.38.70
4 267 ms 318 ms 318 ms 10.90.210.101
5 266 ms 299 ms 317 ms 10.210.32.92
6 * 267 ms 448 ms 10.210.32.83
7 248 ms 299 ms 267 ms 41-208-11-141.mtnns.net [41.208.11.141]
8 254 ms 309 ms 278 ms 41.181.54.65
9 264 ms 318 ms 309 ms 41.181.54.64
10 268 ms 309 ms 317 ms ct-cr-3--tb-dca-3.za.mtnbusiness.net [196.44.29.188]
11 281 ms 298 ms 308 ms 196.44.29.144
12 312 ms 299 ms 288 ms tb-cr-2.za--ct-cr-1.za-a.mtnns.net [196.44.31.107]
13 240 ms 298 ms 298 ms unc-cpt-2.mtnns.net [196.44.18.9]
14 270 ms 309 ms 277 ms 66.8.14.222

Trace complete.

He can't tell the difference.

Same device in the same location only difference is APN setting. multiple tests done over 30 minutes to an hour.
 
Stevewarren said:
Trace Route tests

-snip

He can't tell the difference.

Same device in the same location only difference is APN setting. multiple tests done over 30 minutes to an hour.
Click to expand...

Both tests show very high latency and are equally bad.
It is impossible that our APN routes differently to MTN's as it uses exactly the same infrastructure - I've confirmed this in our PM.
 
Last edited:
AfriGuy said:
Both tests show very high latency and are equally bad.
It is impossible that our APN routes differently to MTN's as it uses exactly the same infrastructure - I've confirmed this in our PM.
Click to expand...

Latency is high because of the little data used in the tests so the modem jumps between 3g and hspa+ it would have better latency if I run something in the background but I didn't want to corrupt the results. Its about the lost packets.
 
Stevewarren said:
Latency is high because of the little data used in the tests so the modem jumps between 3g and hspa+ it would have better latency if I run something in the background but I didn't want to corrupt the results. Its about the lost packets.
Click to expand...

I've replied to your PM addressing this.
 
AfriGuy said:
Both tests show very high latency and are equally bad.
It is impossible that our APN routes differently to MTN's as it uses exactly the same infrastructure - I've confirmed this in our PM.
Click to expand...

it does... I can proof this I have tested this A mtn does not route the same as a the afrihost sim
 
AfriGuy said:
We're here :)
Monday's are always pretty busy for the team, we've got a lot of weekend catch-up, the weeks planning etc etc.

The technical issues from last week are resolved - the cause was listed as a mis-config on some hardware, which was attended to and resolved.
Click to expand...

Nice to know, but apparently not all problems are resolved yet. Since Friday I've been seeing uploads in the normal 1.5 - 2.5mbps range, but downloads are down at 0.5mbps (compared to 4-6mbps).

And based on past experience, I don't have the energy or time to engage with your team on trying to resolve this. I know that sounds self-defeating, but based on what happened before it became clear to me that nobody had a clear approach to identifying and fixing the cause. I had people out here from Atio and MTN and all I heard was "we'll have to do more tests and get back to you". Eventually (6 months later) the problem kind of resolved itself, but now it's back.
 
lotus123 said:
Nice to know, but apparently not all problems are resolved yet. Since Friday I've been seeing uploads in the normal 1.5 - 2.5mbps range, but downloads are down at 0.5mbps (compared to 4-6mbps).

And based on past experience, I don't have the energy or time to engage with your team on trying to resolve this. I know that sounds self-defeating, but based on what happened before it became clear to me that nobody had a clear approach to identifying and fixing the cause. I had people out here from Atio and MTN and all I heard was "we'll have to do more tests and get back to you". Eventually (6 months later) the problem kind of resolved itself, but now it's back.
Click to expand...

Sounds like an isolated issue - happy to look at this for you though :)
Have you tested throughput in different areas?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X