Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Well this whole day on most of them. Especially the 60fps streams and high quality streams.
When I switched over from AH to Vox, there wasn't any problem at all. This problem didn't just occur today, but a couple of days now and then.
 
Well this whole day on most of them. Especially the 60fps streams and high quality streams.
When I switched over from AH to Vox, there wasn't any problem at all. This problem didn't just occur today, but a couple of days now and then.

Okay thanks, I've asked our Team to check on Twitch.tv specifically, you should hopefully see an improvement.

EDIT: Have you been having issues with any other services? Such as your downloads or streaming to other services?
 
Last edited:
After reporting this on the 5th April: 'Internet been terrible the whole long weekend. Irrespective of P2P or normal browsing on social media. I pay for a 4mbps capped product and it currently syncing at 512kbps according to AH's web tool. And speedtest is 2.17 mbps.'

No change today either running at a mighty 2.6mpbs at 18h05 in the evening. Would appreciate some sort of response/excuse/technical spin as to why I pay for a 4mbps line and never see performance close to it!
2852615027.png


Speed test attached.
 
After reporting this on the 5th April: 'Internet been terrible the whole long weekend. Irrespective of P2P or normal browsing on social media. I pay for a 4mbps capped product and it currently syncing at 512kbps according to AH's web tool. And speedtest is 2.17 mbps.'

No change today either running at a mighty 2.6mpbs at 18h05 in the evening. Would appreciate some sort of response/excuse/technical spin as to why I pay for a 4mbps line and never see performance close to it!
2852615027.png


Speed test attached.

Could you also post a tracert?
 
After reporting this on the 5th April: 'Internet been terrible the whole long weekend. Irrespective of P2P or normal browsing on social media. I pay for a 4mbps capped product and it currently syncing at 512kbps according to AH's web tool. And speedtest is 2.17 mbps.'

No change today either running at a mighty 2.6mpbs at 18h05 in the evening. Would appreciate some sort of response/excuse/technical spin as to why I pay for a 4mbps line and never see performance close to it!
2852615027.png


Speed test attached.

Your sync profile seems way off, could you perhaps send me a PM with your line number please?
 
Could you also post a tracert?

Sure thing. Not that tech savvy so not sure if i did this correctly:


D:\Users>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 26 ms 1 ms 1 ms 192.168.0.1
2 11 ms 10 ms 11 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 12 ms 11 ms 14 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 42 ms 13 ms 16 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 13 ms 15 ms 12 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 37 ms 25 ms 20 ms 41.181.180.10
7 34 ms 13 ms 32 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 39 ms 30 ms 38 ms 41.181.139.99
9 390 ms 403 ms 14 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
10 32 ms 14 ms 14 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
11 17 ms 18 ms 16 ms 196.43.39.162
12 387 ms 408 ms 920 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
13 17 ms 18 ms 23 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
14 * 152 ms 408 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.
 
Sure thing. Not that tech savvy so not sure if i did this correctly:


D:\Users>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 26 ms 1 ms 1 ms 192.168.0.1
2 11 ms 10 ms 11 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 12 ms 11 ms 14 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 42 ms 13 ms 16 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 13 ms 15 ms 12 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 37 ms 25 ms 20 ms 41.181.180.10
7 34 ms 13 ms 32 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 39 ms 30 ms 38 ms 41.181.139.99
9 390 ms 403 ms 14 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
10 32 ms 14 ms 14 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
11 17 ms 18 ms 16 ms 196.43.39.162
12 387 ms 408 ms 920 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
13 17 ms 18 ms 23 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
14 * 152 ms 408 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

Those last hops on the Telkom network seem extreme. Could you try to mybroadband.co.za instead?
 
Those last hops on the Telkom network seem extreme. Could you try to mybroadband.co.za instead?

D:\Users>tracert mybroadband.co.za

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

1 416 ms 395 ms 430 ms 192.168.0.1
2 726 ms 407 ms 819 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 225 ms 409 ms 114 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 178 ms 161 ms 100 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 95 ms 90 ms 90 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
6 61 ms 73 ms 36 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 55 ms 26 ms 18 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

8 * * * Request timed out.
9 54 ms 46 ms 82 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
10 72 ms 60 ms 78 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 60 ms 77 ms 50 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 65 ms 41 ms 50 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 64 ms 62 ms 67 ms 197.242.89.170

Trace complete.

D:\Users>
 
D:\Users>tracert mybroadband.co.za

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

Code:
1   416 ms   395 ms   430 ms  192.168.0.1
  2   726 ms   407 ms   819 ms  105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
  3   225 ms   409 ms   114 ms  ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29

That first hop is terrible. Could you post your line stats from your router? Do these issues with the connection only happen during specific times, e.g. 6pm to 8pm or always?
Also, you can remove the top and bottom, only need the hops. You can use [code'] and [/code] to make it look like I did in the quote, just remove the '.

Could you also try running another two tracerts, to:
Afrihost.com and saix.net
 
Last edited:
D:\Users>tracert mybroadband.co.za

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

1 416 ms 395 ms 430 ms 192.168.0.1
2 726 ms 407 ms 819 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 225 ms 409 ms 114 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 178 ms 161 ms 100 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 95 ms 90 ms 90 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
6 61 ms 73 ms 36 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 55 ms 26 ms 18 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

8 * * * Request timed out.
9 54 ms 46 ms 82 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
10 72 ms 60 ms 78 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 60 ms 77 ms 50 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 65 ms 41 ms 50 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 64 ms 62 ms 67 ms 197.242.89.170

Trace complete.

D:\Users>

Woah dude.... try a wired connection. The latency to your router is probably causing the issues :(
 
That first hop is terrible. Could you post your line stats from your router? Do these issues with the connection only happen during specific times, e.g. 6pm to 8pm or always?
Also, you can remove the top and bottom, only need the hops. You can use [code'] and [/code] to make it look like I did in the quote, just remove the '.

Could you also try running another two tracerts, to:
Afrihost.com and saix.net

Nope unfortunately this has been the case for a while now and its the same on a Sunday off peak as in peak during a weekday. The speed is inconsistent. And downloads are much slower than before. I've never exceeded 38GB usage in a month so in no way am I abusing anything either.

System Up Time 02:03:58
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoE 521419 609483 0 6398 70424 02:03:20
LAN 10M/100M 6534 0 0 142 0 02:03:54
WLAN 11M/54M/130M 569972 535608 0 72520 7640 02:03:28

ADSL Link Downstream Upstream
Connection Speed 3072 kbps 512 kbps
Line Attenuation 41.0 db 24.0 db
Noise Margin 10.8 db 12.0 db


Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 25 ms 404 ms 908 ms 192.168.0.1
2 18 ms 11 ms 28 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 17 ms * 408 ms 41.181.221.250
4 23 ms 20 ms 22 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 23 ms 15 ms 26 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 17 ms 33 ms 36 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 28 ms 25 ms 18 ms 196.44.31.99
8 15 ms * 246 ms 196.30.1.39
9 39 ms 25 ms 15 ms 196.31.220.23
10 107 ms 415 ms 406 ms 196.31.63.206
11 14 ms 20 ms 21 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 97 ms 22 ms 16 ms cms-gm.afrihost.com [197.242.144.102]

Tracing route to saix.net [196.25.1.204]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.0.1
2 46 ms 819 ms 16 ms 105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.
1]
3 15 ms 13 ms 46 ms 41.181.221.250
4 14 ms 12 ms 15 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 13 ms 12 ms 13 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 20 ms 52 ms 15 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.22
4]
7 24 ms 21 ms 19 ms rb-cr-1.za--jh-cr-2.za-b.mtnns.net [196.44.31.17
0]
8 17 ms 40 ms 22 ms 41.181.139.109
9 82 ms 819 ms 309 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
10 130 ms 42 ms 15 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
11 37 ms 38 ms 43 ms wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [1
96.43.11.22]
12 * wblv-ip-essr-1-atm-2-0-0-1.telkom-ipnet.co.za [196.43.11.22] repo
rts: Destination net unreachable.
 
OK cool. will give that a go. Will changing the router help solve for wireless connection?

I wouldn't replace the router just yet :)
But from the traceroutes if may be a WiFi problem or something on the local network that's transmitting lots of data, saturating the network. Try isolating a few things, and it'll definitely be worth trying with an ethernet connection.

Keep me posted dude.
 
I wouldn't replace the router just yet :)
But from the traceroutes if may be a WiFi problem or something on the local network that's transmitting lots of data, saturating the network. Try isolating a few things, and it'll definitely be worth trying with an ethernet connection.

Keep me posted dude.

Sadly no improvement with ethernet cable. In fact it seems slower.
 
Ideally I will need you to please run a speedtest on Speedtest.net. Then once that is done, you need to please run a traceroute to Afrihost.com and Google.com. To do that, you will just go to your Start menu, in your Search Programs and Files menu you will type in CMD and press enter. Once Command Prompt is open, you will just type in tracert Afrihost.com.

You can just copy and paste the results into this Thread.


Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 10 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 21 ms * 20 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 16 ms 15 ms 15 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 21 ms 22 ms 22 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 37 ms 39 ms 42 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 44 ms * 40 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.25
5]
8 72 ms 65 ms 63 ms 196.44.31.99
9 40 ms 41 ms 43 ms 196.31.220.6
10 39 ms 38 ms 41 ms 196.31.220.23
11 45 ms 43 ms 42 ms 196.31.63.206
12 40 ms 43 ms 102 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 61 ms 36 ms 36 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Nichol>tracert google.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 11 ms 11 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 39 ms 15 ms 48 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 19 ms 21 ms 41 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 13 ms 13 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 65 ms 71 ms 78 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 43 ms 42 ms 42 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 62 ms 65 ms 65 ms 41.181.139.99
9 58 ms 58 ms 57 ms 72.14.194.74
10 * 36 ms 37 ms 72.14.237.239
11 66 ms 61 ms 60 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.
 
Last edited:
Sadly no improvement with ethernet cable. In fact it seems slower.

When I looked at your test, I would also look at background services like updates, torrents or anything that could affect your ping to the router. Also, when you test over LAN, make sure you kill WiFi so that it's only you on the network.
 


Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 11 ms 10 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 21 ms * 20 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 16 ms 15 ms 15 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 21 ms 22 ms 22 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 37 ms 39 ms 42 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 44 ms * 40 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.25
5]
8 72 ms 65 ms 63 ms 196.44.31.99
9 40 ms 41 ms 43 ms 196.31.220.6
10 39 ms 38 ms 41 ms 196.31.220.23
11 45 ms 43 ms 42 ms 196.31.63.206
12 40 ms 43 ms 102 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 61 ms 36 ms 36 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

C:\Users\Nichol>tracert google.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 11 ms 11 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 39 ms 15 ms 48 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

4 19 ms 21 ms 41 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 13 ms 13 ms 13 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 65 ms 71 ms 78 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

7 43 ms 42 ms 42 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 62 ms 65 ms 65 ms 41.181.139.99
9 58 ms 58 ms 57 ms 72.14.194.74
10 * 36 ms 37 ms 72.14.237.239
11 66 ms 61 ms 60 ms jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.

It looks like latency did spike a few times in general last night over the network. Somewhere just after 9pm and again after 10pm, if my readings of the report are correct. We'll be looking at this specifically as we make the major changes to the network I've mentioned over the next few days.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X