Afrihost Mobile Feedback

PeterRabbit said:
Hi there

I used a website to do it when I had full signal. At my house signal is low. Wanted the best result. I can do it again
Click to expand...

Rather use an app on your phone like net tools or something similar to do a trace route to 1.1.1.1 and 8.8.8.8 on your phone.
 
@AfriNatic

Afrihost APN Traceroute and Ping to Google:

traceroute www.google.co.za
traceroute to www.google.co.za (172.217.170.3), 64 hops max, 52 byte packets
1 192.168.43.1 (192.168.43.1) 6.270 ms 5.161 ms 3.310 ms
2 * * *
3 * * *
4 * * *
5 100.127.3.16 (100.127.3.16) 60.661 ms 47.129 ms 30.500 ms
6 100.127.3.17 (100.127.3.17) 59.654 ms 48.675 ms 38.094 ms
7 * * *
8 169-1-2-254.ip.afrihost.capetown (169.1.2.254) 67.659 ms 73.570 ms 52.200 ms
9 * * *
10 169-1-21-87.ip.afrihost.co.za (169.1.21.87) 63.776 ms 30.541 ms 58.580 ms
11 100.127.2.182 (100.127.2.182) 48.388 ms 69.772 ms 49.535 ms
12 72.14.216.130 (72.14.216.130) 51.963 ms 46.362 ms 51.695 ms
13 10.252.249.30 (10.252.249.30) 50.989 ms
10.252.235.94 (10.252.235.94) 57.943 ms
10.252.249.30 (10.252.249.30) 128.825 ms
14 216.239.40.198 (216.239.40.198) 52.239 ms
jnb02s02-in-f3.1e100.net (172.217.170.3) 89.114 ms
216.239.40.198 (216.239.40.198) 50.564 ms



PING www.google.co.za (216.58.223.131): 56 data bytes


64 bytes from 216.58.223.131: icmp_seq=0 ttl=111 time=161.202 ms


64 bytes from 216.58.223.131: icmp_seq=1 ttl=111 time=99.333 ms


64 bytes from 216.58.223.131: icmp_seq=2 ttl=111 time=71.414 ms


64 bytes from 216.58.223.131: icmp_seq=3 ttl=111 time=116.365 ms


64 bytes from 216.58.223.131: icmp_seq=4 ttl=111 time=67.513 ms


64 bytes from 216.58.223.131: icmp_seq=5 ttl=111 time=90.099 ms


64 bytes from 216.58.223.131: icmp_seq=6 ttl=111 time=78.025 ms


64 bytes from 216.58.223.131: icmp_seq=7 ttl=111 time=71.965 ms


64 bytes from 216.58.223.131: icmp_seq=8 ttl=111 time=91.589 ms


Request timeout for icmp_seq 9


64 bytes from 216.58.223.131: icmp_seq=10 ttl=111 time=73.253 ms


64 bytes from 216.58.223.131: icmp_seq=11 ttl=111 time=94.916 ms


64 bytes from 216.58.223.131: icmp_seq=12 ttl=111 time=82.281 ms


64 bytes from 216.58.223.131: icmp_seq=13 ttl=111 time=68.195 ms


64 bytes from 216.58.223.131: icmp_seq=14 ttl=111 time=82.410 ms


64 bytes from 216.58.223.131: icmp_seq=15 ttl=111 time=50.268 ms


64 bytes from 216.58.223.131: icmp_seq=16 ttl=111 time=111.287 ms


64 bytes from 216.58.223.131: icmp_seq=17 ttl=111 time=112.467 ms


64 bytes from 216.58.223.131: icmp_seq=18 ttl=111 time=81.712 ms


64 bytes from 216.58.223.131: icmp_seq=19 ttl=111 time=115.892 ms





--- www.google.co.za ping statistics ---


20 packets transmitted, 19 packets received, 5.0% packet loss


round-trip min/avg/max/stddev = 50.268/90.536/161.202/24.432 ms
Click to expand...

MTN APN Traceroute and Ping to Google:

traceroute to www.google.co.za (172.217.170.3), 64 hops max, 52 byte packets
1 192.168.43.1 (192.168.43.1) 8.696 ms 4.218 ms 4.538 ms
2 * * *
3 10.110.38.70 (10.110.38.70) 72.843 ms 67.317 ms 61.668 ms
4 * * *
5 41-208-11-4.mtnns.net (41.208.11.4) 106.925 ms 57.588 ms 31.937 ms
6 41.181.242.105 (41.181.242.105) 57.928 ms 58.059 ms 31.710 ms
7 196.44.29.97 (196.44.29.97) 58.196 ms
196.44.29.89 (196.44.29.89) 57.424 ms 53.436 ms
8 196.44.29.114 (196.44.29.114) 110.154 ms
196.44.29.118 (196.44.29.118) 55.224 ms 63.647 ms
9 196.44.29.138 (196.44.29.138) 52.419 ms
196.44.29.5 (196.44.29.5) 58.861 ms
196.44.29.140 (196.44.29.140) 55.730 ms
10 196.44.29.89 (196.44.29.89) 84.625 ms
196.44.29.97 (196.44.29.97) 64.526 ms
196.44.29.89 (196.44.29.89) 64.554 ms
11 72.14.243.186 (72.14.243.186) 85.686 ms 58.661 ms 70.115 ms
12 10.252.254.94 (10.252.254.94) 56.596 ms
10.252.249.30 (10.252.249.30) 52.972 ms
10.252.235.94 (10.252.235.94) 84.947 ms
13 216.239.40.248 (216.239.40.248) 55.408 ms 68.469 ms
216.239.40.198 (216.239.40.198) 78.845 ms
14 172.253.66.3 (172.253.66.3) 86.731 ms 74.600 ms 52.552 ms
15 jnb02s02-in-f3.1e100.net (172.217.170.3) 65.904 ms 60.904 ms 98.544 ms



PING www.google.co.za (216.58.223.131): 56 data bytes


64 bytes from 216.58.223.131: icmp_seq=0 ttl=104 time=89.738 ms


64 bytes from 216.58.223.131: icmp_seq=1 ttl=104 time=85.508 ms


64 bytes from 216.58.223.131: icmp_seq=2 ttl=104 time=86.888 ms


64 bytes from 216.58.223.131: icmp_seq=3 ttl=104 time=94.309 ms


64 bytes from 216.58.223.131: icmp_seq=4 ttl=104 time=64.851 ms


64 bytes from 216.58.223.131: icmp_seq=5 ttl=104 time=115.269 ms


64 bytes from 216.58.223.131: icmp_seq=6 ttl=104 time=104.767 ms


64 bytes from 216.58.223.131: icmp_seq=7 ttl=104 time=88.313 ms


64 bytes from 216.58.223.131: icmp_seq=8 ttl=104 time=88.035 ms


64 bytes from 216.58.223.131: icmp_seq=9 ttl=104 time=58.847 ms


64 bytes from 216.58.223.131: icmp_seq=10 ttl=104 time=87.564 ms


64 bytes from 216.58.223.131: icmp_seq=11 ttl=104 time=155.992 ms


64 bytes from 216.58.223.131: icmp_seq=12 ttl=104 time=110.536 ms


64 bytes from 216.58.223.131: icmp_seq=13 ttl=104 time=87.154 ms


64 bytes from 216.58.223.131: icmp_seq=14 ttl=104 time=84.953 ms


64 bytes from 216.58.223.131: icmp_seq=15 ttl=104 time=89.630 ms


64 bytes from 216.58.223.131: icmp_seq=16 ttl=104 time=131.923 ms


64 bytes from 216.58.223.131: icmp_seq=17 ttl=104 time=81.340 ms


64 bytes from 216.58.223.131: icmp_seq=18 ttl=104 time=103.292 ms


64 bytes from 216.58.223.131: icmp_seq=19 ttl=104 time=91.357 ms





--- www.google.co.za ping statistics ---


20 packets transmitted, 20 packets received, 0.0% packet loss


round-trip min/avg/max/stddev = 58.847/95.013/155.992/21.023 ms
Click to expand...
 
PeterRabbit said:
Hi there

I used a website to do it when I had full signal. At my house signal is low. Wanted the best result. I can do it again
Click to expand...

Can you send me a dm with the number in question.

I have a list of clients that area experiencing the same issue and I can find you on the list I have compiled.
 
PhireSide said:
@AfriNatic

Afrihost APN Traceroute and Ping to Google:



MTN APN Traceroute and Ping to Google:
Click to expand...

The issue is still on going.

I add all the tests done to the spreadsheet we have and we are still working with MTN on the issue.

It's not resolved yet even after the routing changes made by MTN recently.
 
AfriNatic said:
The issue is still on going.

I add all the tests done to the spreadsheet we have and we are still working with MTN on the issue.

It's not resolved yet even after the routing changes made by MTN recently.
Click to expand...
This sounds like a very bad problem to have occurred for so long. Right now many of us are buying data on MTN in order to be able to use our phones. So buying data twice, through Afrihost and mtn.

I know you guys are working hard but it's a pretty significant problem and perhaps Afrihost needs more people on the job to help fix it.

Also, thanks very much for keeping us updated, let me know if there are more tracers that I could do to help.
 
PeterRabbit said:
This sounds like a very bad problem to have occurred for so long. Right now many of us are buying data on MTN in order to be able to use our phones. So buying data twice, through Afrihost and mtn.

I know you guys are working hard but it's a pretty significant problem and perhaps Afrihost needs more people on the job to help fix it.

Also, thanks very much for keeping us updated, let me know if there are more tracers that I could do to help.
Click to expand...

The issue is with MTN to investigate what is causing the intermittency on our APN. As it's a service we buy from MTN we need to allow them the time to work on it. I totally understand your frustration and that it's leaving you out of pocket and I will speak to my manager to see if there is something we can do about that.

Once i have feedback from Noc about the APN I will revert back.
 
Access via afrihost APN feels way better today...getting a normal data connection again without any interruptions.
 
18B00450-1EF2-4622-B75E-D202B2157F1B.jpeg952B87D4-7138-42D8-AFBF-333B99A0F5FB.jpeg
Seems to be getting better but I would have been better to run three tests of each to be sure, just didn’t have time. Jitter on afrihost still high and was noticeably slower when browsing.
 
I agree, it's definitely getting better, yesterday I did a few speedtests and there was no packet loss, this is a huge improvement from 50%.
 
I got my sim for the LTE fixed broadband, used it for about 8 hours and it got disabled.
Got some nonsense email that I'm using a "non-approved" device - which conveniently seems out of stock everywhere except Afrihost. And some nonsense story about MTN's network only allows those devices to ensure quality. Cause you know, those evil Dlink LTE/LTE-A devices hunt down and kill all MTN's airwaves...

But literally anything can use MTN's network on 3G,4G or 5G. What a load of wash. I cancelled the Afrihost service and switched to a normal MTN LTE sim.
 
@AfriNatic

I loaded R50 airtime on Wednesday and its already finished, when buying the airtime it says it will give me ~50 Min of talk time.

I got only about 22.

Is this normal?

1629460532055.png
 
Rickster said:
It doesnt say but im sure it's MTN Zone.
Click to expand...

Okay with MTN Zone the call rate is R2.50 per minute minus any discounts. That means that the max you will get is min or so.

Please consider changing your price plan to everyday per second or make use of some of the MTN voice promos as they can make a R50 airtime stretch quite a bit.
 
Uhm is this normal?

I noticed today (0730 when I checked) that when the power dropped Afrihost APN stopped working.. the default MTN internet APN still works and is how I am posting this.

Is the APN connection dead ? I’m in Cpt.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X