Afrihost MTN Fixed LTE-A Thread

I don't have my fixed lte-A sim with me sent it off to @Yuu

What's up with international speeds? Slow how is the latency and what does a tracert look like.
Oh my bad. Sorry - thought you still had it.

This was from last night:
20200221_183653.jpg

Haven't run a trace route. Will try that tonight when international goes South.
 
Yeah. My local is fine.
Testing my MTN contract sim to the same tower is 100%.
So not tower related or device related.
Definitely something up with AH (I think).

EDIT:
And so it begins:
05aeb33eee748d2466658f3b28c7121c.jpg

One to Amsterdam:
c1226868de4b1da00c5e25e1b06ed290.jpg


Tracing route to www.vodafoneaws.co.uk [85.205.252.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 17 ms 25 ms 25 ms 100.127.255.66
4 25 ms 23 ms 20 ms 196.44.29.100
5 20 ms 17 ms 20 ms 196.44.29.89
6 113 ms 124 ms 37 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 44 ms 37 ms 38 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 45 ms 38 ms 36 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 40 ms 38 ms 39 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.199.141]
10 231 ms 252 ms 303 ms 10.189.30.2
11 240 ms 304 ms 409 ms be5956.rcr21.b023101-0.lon01.atlas.cogentco.com [149.11.248.209]
12 314 ms 307 ms 200 ms be12499.ccr21.lon01.atlas.cogentco.com [154.54.60.241]
13 317 ms 305 ms 303 ms ae14-xcr1.lns.cw.net [195.2.22.21]
14 306 ms 409 ms 303 ms ae1-xcr1.ltw.cw.net [195.2.24.125]
15 401 ms 277 ms 228 ms ae11-ucr1.dub.cw.net [195.2.3.130]
16 222 ms 215 ms 288 ms vf-ie-gw.ucr1.dub.cw.net [195.89.101.74]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.


Tracing route to e15314.e22.akamaiedge.net [104.75.221.25] (www.amazon.co.uk)
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 46 ms 23 ms 19 ms 100.127.255.66
4 42 ms 19 ms 21 ms 196.44.29.68
5 19 ms 24 ms 22 ms 196.44.29.97
6 25 ms 29 ms 22 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 39 ms 19 ms 19 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 42 ms 20 ms 21 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 375 ms 200 ms 201 ms akamai.ixp.joburg [196.60.8.212]
10 32 ms 16 ms 19 ms a104-75-221-25.deploy.static.akamaitechnologies.com [104.75.221.25]

Trace complete.

Tracing route to www.nforce.com [37.143.33.51]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 28 ms 37 ms 27 ms 100.127.255.66
4 44 ms 19 ms 26 ms 196.44.29.100
5 52 ms 19 ms 23 ms 196.44.29.89
6 45 ms 22 ms 20 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 46 ms 20 ms 22 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 44 ms 21 ms 20 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 50 ms 20 ms 21 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.199.141]
10 285 ms 303 ms 510 ms 10.189.30.2
11 * * * Request timed out.
12 303 ms 302 ms 510 ms 185.107.116.4
13 357 ms 247 ms 304 ms www.nforce.com [37.143.33.51]

Trace complete.

Local:
c02735bcf1320751b900b0706a16f00d.jpg

Ping is a bit high. Usually on 17 ms for local.

And here is the speedtest using my MTN contract sim connected to the same tower, router and UK server:
a98369f613a17ac8cc69da6230a313d8.jpg

^^^ Sorry about the volume control.

@cavedog

EDIT: And just getting worse:
4329e36f9c3525d56ffbda5f4e42ec95.jpg


So frustrating.

Another test on my contract MTN sim (same tower, same router, same server):
c9fa8905893242cc4be9f5772695b347.jpg


Afrihost sort your network out!!

@AfriMan @AfriGuy @AfriFella @AfriNatic @Afrihost-Gian
 
Last edited:
International on Afrihost Pure LTE very slow tonight ...

Local seems to be fine though ...
 
International on Afrihost Pure LTE very slow tonight ...

Local seems to be fine though ...
Thanks Jake.
I am glad that it has now been confirmed to be an issue for others as well.
I appreciate your assistance.
AH - sort your network out!!!

@AfriMan @AfriGuy @AfriFella @AfriNatic @Afrihost-Gian
 
Yeah. My local is fine.
Testing my MTN contract sim to the same tower is 100%.
So not tower related or device related.
Definitely something up with AH (I think).

EDIT:
And so it begins:
05aeb33eee748d2466658f3b28c7121c.jpg

One to Amsterdam:
c1226868de4b1da00c5e25e1b06ed290.jpg


Tracing route to www.vodafoneaws.co.uk [85.205.252.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 17 ms 25 ms 25 ms 100.127.255.66
4 25 ms 23 ms 20 ms 196.44.29.100
5 20 ms 17 ms 20 ms 196.44.29.89
6 113 ms 124 ms 37 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 44 ms 37 ms 38 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 45 ms 38 ms 36 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 40 ms 38 ms 39 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.199.141]
10 231 ms 252 ms 303 ms 10.189.30.2
11 240 ms 304 ms 409 ms be5956.rcr21.b023101-0.lon01.atlas.cogentco.com [149.11.248.209]
12 314 ms 307 ms 200 ms be12499.ccr21.lon01.atlas.cogentco.com [154.54.60.241]
13 317 ms 305 ms 303 ms ae14-xcr1.lns.cw.net [195.2.22.21]
14 306 ms 409 ms 303 ms ae1-xcr1.ltw.cw.net [195.2.24.125]
15 401 ms 277 ms 228 ms ae11-ucr1.dub.cw.net [195.2.3.130]
16 222 ms 215 ms 288 ms vf-ie-gw.ucr1.dub.cw.net [195.89.101.74]
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.


Tracing route to e15314.e22.akamaiedge.net [104.75.221.25] (www.amazon.co.uk)
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 46 ms 23 ms 19 ms 100.127.255.66
4 42 ms 19 ms 21 ms 196.44.29.68
5 19 ms 24 ms 22 ms 196.44.29.97
6 25 ms 29 ms 22 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 39 ms 19 ms 19 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 42 ms 20 ms 21 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 375 ms 200 ms 201 ms akamai.ixp.joburg [196.60.8.212]
10 32 ms 16 ms 19 ms a104-75-221-25.deploy.static.akamaitechnologies.com [104.75.221.25]

Trace complete.

Tracing route to www.nforce.com [37.143.33.51]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms homerouter.cpe [192.168.8.1]
2 * * * Request timed out.
3 28 ms 37 ms 27 ms 100.127.255.66
4 44 ms 19 ms 26 ms 196.44.29.100
5 52 ms 19 ms 23 ms 196.44.29.89
6 45 ms 22 ms 20 ms 169-1-21-35.ip.afrihost.co.za [169.1.21.35]
7 46 ms 20 ms 22 ms 169-1-21-80.ip.afrihost.co.za [169.1.21.80]
8 44 ms 21 ms 20 ms 169-1-21-81.ip.afrihost.co.za [169.1.21.81]
9 50 ms 20 ms 21 ms rndf-ip-ll-1-wan.telkom-ipnet.co.za [196.25.199.141]
10 285 ms 303 ms 510 ms 10.189.30.2
11 * * * Request timed out.
12 303 ms 302 ms 510 ms 185.107.116.4
13 357 ms 247 ms 304 ms www.nforce.com [37.143.33.51]

Trace complete.

Local:
c02735bcf1320751b900b0706a16f00d.jpg

Ping is a bit high. Usually on 17 ms for local.

And here is the speedtest using my MTN contract sim connected to the same tower, router and UK server:
a98369f613a17ac8cc69da6230a313d8.jpg

^^^ Sorry about the volume control.

@cavedog

EDIT: And just getting worse:
4329e36f9c3525d56ffbda5f4e42ec95.jpg


So frustrating.

Another test on my contract MTN sim (same tower, same router, same server):
c9fa8905893242cc4be9f5772695b347.jpg


Afrihost sort your network out!!

@AfriMan @AfriGuy @AfriFella @AfriNatic @Afrihost-Gian


So I'm comparing the routing to my fibre and it follows a similar route except for the start which is understandable because the traffic that MTN hands over to Afrihost and the traffic Openserve hands to Afrihost will be different routers. You seem to have high latency on the very same IPs that I have low latency. I'm stumped why that is though. If it was an MTN issue then there would have been higher latency earlier in the trace unless you can run an extended MTR to see how the jitter is on those IPs at the start of the route.

Slow international usually indicate packateloss but not on LTE and not by the looks of your trace route.

Here is my trace on Fibre

afrihost_pure_fibre.png
 
Thanks @cavedog.
I will try to do an MTR asap.
Definitely an AH issue, imho.
I tested my regular contract MTN sim during the same time period and it performed decently.
Same tower, router, server everything.
Also @Jake45 also seeing the same thing.
 
I know this is something you might not want to hear but with Supersonic the traffic will go via the MTN Business network. I just don't understand why you have high latency and slow speeds when my connection follows the same route and it doesn't suffer from increased latency.

9063585042.png
 
I must be honest - really am considering going back to Supersonic. But their data doesn't roll over. That was the huge fight last time. But it doesn't help having roll over data if I can't use it. Lately the data has just been wasted on speedtests to compare local to international.
EDIT: And AH have not even acknowledged my requests for assistance since around 10 Feb 2020.
This after numerous tags and PM's. Pathetic really.
 
Last edited:
I know this is something you might not want to hear but with Supersonic the traffic will go via the MTN Business network. I just don't understand why you have high latency and slow speeds when my connection follows the same route and it doesn't suffer from increased latency.

9063585042.png
Which server is that in London? Would also like to compare. Or is that the Vodafone UK one?
 
Don't think it can get any worse:
144a7f0b26ea6f50e3d88f99d3945405.jpg

Wow...

EDIT:
This is what it is supposed to look like (done this morning, 22 Feb 2020 @ 6:46 am):
d186e4e1b70479ac9d000bbfa25afa2d.jpg

Reeks of congestion/prioritisation during peak times.
 
Last edited:
yes adsl with AH - london speedtest works fine, MTN fixed with AH - doesn't even connect.
 
Thank you all for your confirmation.
I understand that networks have issues, but the radio silence from AH is the final straw. This after numerous posts, tags and PM's. Really bad show.
 
AH, don't bother. I have canceled the service.

Tonight the speeds do seem to be particularly bad. It's possible that the service might improve after a few days. Were you able to cancel before the February cutoff date? I'm not sure whether that is the 15th or 22nd etc. Otherwise you will have to stick it out for another month!
 
My international pings are not wonderful but expected at around 190-250ms avg even during peak times.

I do notice it when gaming on World of Warships though during peak times...there's often massive stuttering and jitter which usually means i get my ask kicked before the screen has chance to refresh and I see my burning ship listing to starboard and busy sinking :D

So now I generally play after midnight and before 8am when response is more reasonable.

p.s tonight is particularly bad...again...weekend...Sat night...1 billion kids playing on steam.
 
Tonight the speeds do seem to be particularly bad. It's possible that the service might improve after a few days. Were you able to cancel before the February cutoff date? I'm not sure whether that is the 15th or 22nd etc. Otherwise you will have to stick it out for another month!
Unfortunately not. 15th is the cut off. So still have to pay for March.
I have had these issues since around 10 Feb 2020. So it has been more than a few days for me. Lol.
The (lack of) support is what killed it for me.
 
My international pings are not wonderful but expected at around 190-250ms avg even during peak times.

I do notice it when gaming on World of Warships though during peak times...there's often massive stuttering and jitter which usually means i get my ask kicked before the screen has chance to refresh and I see my burning ship listing to starboard and busy sinking :D

So now I generally play after midnight and before 8am when response is more reasonable.

p.s tonight is particularly bad...again...weekend...Sat night...1 billion kids playing on steam.
Thank goodness I don't use it for gaming. I think I would rage quit.
 
Top
Sign up to the MyBroadband newsletter
X