What is going on here?

B

Bobbin

Honorary Master
Joined
Oct 22, 2009
Messages
10,395
Reaction score
2,360
Location
Johannesburg
Just got LTE activated in the last 24 hours on my new Afrihost/MTN SIM and Huawei E5372.

This is the sort of latency I'm getting on 4G:

Pinging www.myadsl.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=462ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1072ms TTL=51
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1066ms TTL=51
Reply from 197.242.89.170: bytes=32 time=46ms TTL=51
Reply from 197.242.89.170: bytes=32 time=486ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1066ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=853ms TTL=51
Reply from 197.242.89.170: bytes=32 time=63ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1060ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1073ms TTL=51
Reply from 197.242.89.170: bytes=32 time=310ms TTL=51
Reply from 197.242.89.170: bytes=32 time=54ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1079ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1070ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1076ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=570ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1071ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1058ms TTL=51
Reply from 197.242.89.170: bytes=32 time=43ms TTL=51
Reply from 197.242.89.170: bytes=32 time=441ms TTL=51
Reply from 197.242.89.170: bytes=32 time=752ms TTL=51
Reply from 197.242.89.170: bytes=32 time=49ms TTL=51
Reply from 197.242.89.170: bytes=32 time=469ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1081ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51

Notice a pattern? It's constantly going high-low-high-low. What is up with that?

I'm also detecting moments of non-responsiveness when browsing to sudden surges of fast loading to non-responsiveness again.

I am in the Lonehill area - specifically where Lonehill and Beverley meet.

Is there some sort of issue? Afrihost website says mobile status is all good.
 
Smells vaguely like a MTU / fragmentation issue.

Try

ping mybroadband.co.za -f -l 250

Post a speedtest and tracert while your at it as well
 
Your tower is congested

130px-AwesomeFace-P.png
 
Rickster said:
Your tower is congested

130px-AwesomeFace-P.png
Click to expand...
Not a chance in hell you're pushing <50ms through a congested tower....and definitely not in a semi-predictable pattern.

Don't know whats going on but I doubt its that. A trace will help pin point it a bit imo
 
HavocXphere said:
Smells vaguely like a MTU / fragmentation issue.

Try

ping mybroadband.co.za -f -l 250

Post a speedtest and tracert while your at it as well
Click to expand...

Thanks. Here you go. Seems to do exactly the same on the 250 byte ping test :(

Pinging mybroadband.co.za [197.242.89.170] with 250 bytes of data:
Reply from 197.242.89.170: bytes=250 time=479ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1068ms TTL=50
Reply from 197.242.89.170: bytes=250 time=47ms TTL=50
Reply from 197.242.89.170: bytes=250 time=355ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1042ms TTL=50
Reply from 197.242.89.170: bytes=250 time=58ms TTL=50
Reply from 197.242.89.170: bytes=250 time=292ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1027ms TTL=50
Reply from 197.242.89.170: bytes=250 time=57ms TTL=50
Reply from 197.242.89.170: bytes=250 time=590ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1040ms TTL=50
Reply from 197.242.89.170: bytes=250 time=53ms TTL=50
Reply from 197.242.89.170: bytes=250 time=835ms TTL=50
Reply from 197.242.89.170: bytes=250 time=73ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1031ms TTL=50
Reply from 197.242.89.170: bytes=250 time=45ms TTL=50
Reply from 197.242.89.170: bytes=250 time=709ms TTL=50
Reply from 197.242.89.170: bytes=250 time=51ms TTL=50
Reply from 197.242.89.170: bytes=250 time=841ms TTL=50
Reply from 197.242.89.170: bytes=250 time=54ms TTL=50
Reply from 197.242.89.170: bytes=250 time=916ms TTL=50
Reply from 197.242.89.170: bytes=250 time=51ms TTL=50
Reply from 197.242.89.170: bytes=250 time=496ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1029ms TTL=50
Reply from 197.242.89.170: bytes=250 time=53ms TTL=50
Reply from 197.242.89.170: bytes=250 time=883ms TTL=50
Reply from 197.242.89.170: bytes=250 time=59ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1012ms TTL=50
Reply from 197.242.89.170: bytes=250 time=52ms TTL=50
Reply from 197.242.89.170: bytes=250 time=58ms TTL=50
Reply from 197.242.89.170: bytes=250 time=1058ms TTL=50
Reply from 197.242.89.170: bytes=250 time=50ms TTL=50



1 1 ms <1 ms 1 ms www.huaweimobilewifi.com [192.168.8.1]
2 * * * Request timed out.
3 1052 ms 27 ms 29 ms 41.181.242.119
4 1036 ms 36 ms 40 ms 10.90.204.162
5 23 ms 37 ms 39 ms 41.181.242.105
6 776 ms 21 ms 29 ms 41.181.242.104
7 31 ms 29 ms 37 ms qux--rb-dca-2.za-f.za.mtnbusiness.net [41.181.24
8.233]
8 18 ms 30 ms 27 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.181.248
.232]
9 32 ms 28 ms 18 ms rb-dca-2.za--rb-cr-1.mtnns.net [196.44.31.122]
10 624 ms 29 ms 29 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
11 830 ms 40 ms 33 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

12 * * * Request timed out.
13 1070 ms 57 ms 60 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
14 486 ms 48 ms 58 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
15 1077 ms 47 ms 56 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
16 1065 ms 57 ms 58 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
17 1084 ms 56 ms 56 ms 197.242.89.170

Trace complete.
 
A more legible traceroute

Tracing route to www.myadsl.co.za [197.242.89.170]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms www.huaweimobilewifi.com [192.168.8.1]
2 * * * Request timed out.
3 1069 ms 31 ms 36 ms 41.181.242.119
4 991 ms 44 ms 45 ms 10.90.204.162
5 30 ms 30 ms 36 ms 41.181.242.105
6 1053 ms 27 ms 22 ms 41.181.242.104
7 1055 ms 23 ms 25 ms qux--rb-dca-2.za-f.za.mtnbusiness.net [41.181.248.233]
8 1020 ms 27 ms 39 ms rb-dca-2.za-qux-f.za.mtnbusiness.net [41.181.248.232]
9 528 ms 27 ms 24 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
10 792 ms 33 ms 30 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
11 1066 ms 33 ms 28 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
12 * * * Request timed out.
13 601 ms 49 ms 51 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.151]
14 290 ms 51 ms 59 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1.africainx.net [41.66.132.246]
15 324 ms 48 ms 46 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
16 542 ms 60 ms 68 ms row-access-switch1-row3-4.jnb1.host-h.net [197.189.193.36]
17 506 ms 56 ms 64 ms 197.242.89.170

Trace complete.
 
Screwed on the MTN network there. Nothing you can do about it your side.

No idea whats going on tbh. It does have a hint of congestion about it but its a little like saying "all cars are moving at stop-go pace, except every third is moving at 120kmh". I suppose its possible if MTN dreamed up some really messed up algorithm...

Its definitely not the entire MTN network though...if it were then mybb would be on fire.

Either way...not something you can fix your side imo. Maybe point Afriman to this thread and ask him whats going on?
 
HavocXphere said:
Screwed on the MTN network there. Nothing you can do about it your side.

No idea whats going on tbh. It does have a hint of congestion about it but its a little like saying "all cars are moving at stop-go pace, except every third is moving at 120kmh". I suppose its possible if MTN dreamed up some really messed up algorithm...

Its definitely not the entire MTN network though...if it were then mybb would be on fire.

Either way...not something you can fix your side imo. Maybe point Afriman to this thread and ask him whats going on?
Click to expand...

Thanks will do :) will give it until tomorrow first and see. Will also test the modem in a different area tomorrow at work though not sure if that would make a difference.
 
Not only am I constantly double posting because of this problem, seems I double threaded too :D Didn't know one could do that.

Mod, please merge or remove the other if possible? Before I break the Internet :p
 
Getting exactly the same result in Melrose Arch area...

I'm wondering if I have a faulty modem seeing as I am the only person in SA reporting this. Going to log a call with Afrihost support.

Pinging www.myadsl.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=345ms TTL=51
Request timed out.
Reply from 197.242.89.170: bytes=32 time=760ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1049ms TTL=51
Reply from 197.242.89.170: bytes=32 time=51ms TTL=51
Reply from 197.242.89.170: bytes=32 time=665ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1204ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=329ms TTL=51
Reply from 197.242.89.170: bytes=32 time=604ms TTL=51
Reply from 197.242.89.170: bytes=32 time=994ms TTL=51
Reply from 197.242.89.170: bytes=32 time=99ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1099ms TTL=51
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1065ms TTL=51
Reply from 197.242.89.170: bytes=32 time=46ms TTL=51
Reply from 197.242.89.170: bytes=32 time=381ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1057ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=929ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1050ms TTL=51
Reply from 197.242.89.170: bytes=32 time=34ms TTL=51
Reply from 197.242.89.170: bytes=32 time=854ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=863ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1073ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=985ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=695ms TTL=51
 
Getting exactly the same result in Melrose Arch area...

I'm wondering if I have a faulty modem seeing as I am the only person in SA reporting this. Going to log a call with Afrihost support.

Pinging www.myadsl.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=345ms TTL=51
Request timed out.
Reply from 197.242.89.170: bytes=32 time=760ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1049ms TTL=51
Reply from 197.242.89.170: bytes=32 time=51ms TTL=51
Reply from 197.242.89.170: bytes=32 time=665ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1204ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=329ms TTL=51
Reply from 197.242.89.170: bytes=32 time=604ms TTL=51
Reply from 197.242.89.170: bytes=32 time=994ms TTL=51
Reply from 197.242.89.170: bytes=32 time=99ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1099ms TTL=51
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1065ms TTL=51
Reply from 197.242.89.170: bytes=32 time=46ms TTL=51
Reply from 197.242.89.170: bytes=32 time=381ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1057ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=929ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1050ms TTL=51
Reply from 197.242.89.170: bytes=32 time=34ms TTL=51
Reply from 197.242.89.170: bytes=32 time=854ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=863ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1073ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=985ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=695ms TTL=51
 
So this is a Vodacom SIM in the Huawei modem on 4G with very low signal, so it's obviously MTN/Afrihost network then. But WTF am I the only one reporting this??:

Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=46ms TTL=51
Reply from 197.242.89.170: bytes=32 time=53ms TTL=51
Reply from 197.242.89.170: bytes=32 time=55ms TTL=51
Reply from 197.242.89.170: bytes=32 time=49ms TTL=51
Reply from 197.242.89.170: bytes=32 time=58ms TTL=51
Reply from 197.242.89.170: bytes=32 time=58ms TTL=51
Reply from 197.242.89.170: bytes=32 time=43ms TTL=51
Reply from 197.242.89.170: bytes=32 time=43ms TTL=51
Reply from 197.242.89.170: bytes=32 time=60ms TTL=51
Reply from 197.242.89.170: bytes=32 time=42ms TTL=51
Reply from 197.242.89.170: bytes=32 time=59ms TTL=51
Reply from 197.242.89.170: bytes=32 time=67ms TTL=51
Reply from 197.242.89.170: bytes=32 time=35ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=49ms TTL=51
Reply from 197.242.89.170: bytes=32 time=39ms TTL=51
Reply from 197.242.89.170: bytes=32 time=57ms TTL=51
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=57ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=55ms TTL=51
Reply from 197.242.89.170: bytes=32 time=53ms TTL=51
Reply from 197.242.89.170: bytes=32 time=81ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
 
Bobbin said:
Just got LTE activated in the last 24 hours on my new Afrihost/MTN SIM and Huawei E5372.

This is the sort of latency I'm getting on 4G:

Pinging www.myadsl.co.za [197.242.89.170] with 32 bytes of data:
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=462ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1072ms TTL=51
Reply from 197.242.89.170: bytes=32 time=45ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1066ms TTL=51
Reply from 197.242.89.170: bytes=32 time=46ms TTL=51
Reply from 197.242.89.170: bytes=32 time=486ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1066ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=853ms TTL=51
Reply from 197.242.89.170: bytes=32 time=63ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1060ms TTL=51
Reply from 197.242.89.170: bytes=32 time=48ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1073ms TTL=51
Reply from 197.242.89.170: bytes=32 time=310ms TTL=51
Reply from 197.242.89.170: bytes=32 time=54ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1079ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1070ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1076ms TTL=51
Reply from 197.242.89.170: bytes=32 time=44ms TTL=51
Reply from 197.242.89.170: bytes=32 time=570ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1071ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1058ms TTL=51
Reply from 197.242.89.170: bytes=32 time=43ms TTL=51
Reply from 197.242.89.170: bytes=32 time=441ms TTL=51
Reply from 197.242.89.170: bytes=32 time=752ms TTL=51
Reply from 197.242.89.170: bytes=32 time=49ms TTL=51
Reply from 197.242.89.170: bytes=32 time=469ms TTL=51
Reply from 197.242.89.170: bytes=32 time=1081ms TTL=51
Reply from 197.242.89.170: bytes=32 time=47ms TTL=51

Notice a pattern? It's constantly going high-low-high-low. What is up with that?

I'm also detecting moments of non-responsiveness when browsing to sudden surges of fast loading to non-responsiveness again.

I am in the Lonehill area - specifically where Lonehill and Beverley meet.

Is there some sort of issue? Afrihost website says mobile status is all good.
Click to expand...

This is pretty unusual. Usually ping on LTE is definitely lower and also more consistent.

Could you be switching between LTE and 3G signal perhaps? I think the best route would be to submit a coverage query to MTN so they can see if there are any local tower or network issues in the area.

https://www.mtn.co.za/_LAYOUTS/MTN.SP2010.FormsData/Networkcoveragequery.aspx (this is the coverage form).

Just drop me a PM with the reference you get back :)
 
AfriMan said:
This is pretty unusual. Usually ping on LTE is definitely lower and also more consistent.

Could you be switching between LTE and 3G signal perhaps? I think the best route would be to submit a coverage query to MTN so they can see if there are any local tower or network issues in the area.

https://www.mtn.co.za/_LAYOUTS/MTN.SP2010.FormsData/Networkcoveragequery.aspx (this is the coverage form).

Just drop me a PM with the reference you get back :)
Click to expand...

Thanks for reply. Well I'm getting this exact result both in Fourways/Lonehill and Melrose Arch - 22km apart. Both areas on the coverage map show I am well within LTE coverage (Plus the areas are highly developed) and I am forcing the modem to use 4G only on Afrihost APN. So I don't think a coverage query would achieve anything :/

Will log a support ticket on Afrihost for some assist. Maybe I'm just doing something wrong.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X