electrofreeze
Expert Member
latency goes up when capacity is not enough
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Thanks. Interesting that my 8am comparison was with an ISP package that targeted the gaming and online streaming (video) demographic. These people are obviously not highly active at 8am, hence the good result from that particular ISP offering. My AH is a business package. This could be a disadvantage because all business users "peak" at the same time (pardon the expression).
I still have some confidence that AH will get this optimisation right. Bring it on.
Afriman, please see above.
Afrihost
Traceroute output:
1 * * *
2 41.181.221.213 (41.181.221.213) 37.720 ms 67.511 ms 69.031 ms
3 41.181.221.214 (41.181.221.214) 42.091 ms 43.223 ms 42.767 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 37.931 ms 37.738 ms 36.512 ms
5 rb-cr-1.za--rb-dca-2.mtnns.net (196.44.31.122) 43.356 ms 50.371 ms 43.328 ms
6 196.44.31.97 (196.44.31.97) 37.931 ms 37.798 ms
jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221) 37.964 ms
7 196.31.220.10 (196.31.220.10) 36.923 ms 37.572 ms 37.641 ms
8 196.31.220.21 (196.31.220.21) 43.072 ms 44.918 ms 58.265 ms
9 196.31.63.202 (196.31.63.202) 43.060 ms 43.521 ms 42.765 ms
10 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 43.361 ms 46.048 ms 43.080 ms
11 cms-gm.afrihost.com (197.242.144.102) 43.670 ms 42.888 ms 43.080 ms
WebAfrica
Traceroute output:
1 * * *
2 196.38.74.246 (196.38.74.246) 8.656 ms 8.613 ms 8.007 ms
3 cdsl1-umh-gi0-0-0-3102.ip.isnet.net (196.38.74.245) 8.995 ms 8.366 ms 8.813 ms
4 196.26.210.200 (196.26.210.200) 9.298 ms 9.299 ms 9.302 ms
5 mi-za-umh-p8-ten-0-0-0-1.ip.isnet.net (168.209.93.240) 10.309 ms 10.400 ms 10.321 ms
6 mi-za-umh-p7-ten-0-0-1-1.ip.isnet.net (168.209.93.239) 13.280 ms 13.670 ms 13.529 ms
7 mi-za-bry-p7-lo0.ip.isnet.net (168.209.255.208) 13.380 ms 13.757 ms 13.645 ms
8 core2a-bry-gi1-0-0.ip.isnet.net (168.209.218.2) 13.166 ms 13.017 ms 13.162 ms
9 bry.it.is.co.za (196.14.64.36) 13.389 ms 13.277 ms 13.151 ms
latency goes up when capacity is not enough
Is there any problem with the news server atm? I'm getting connections but nothing is downloading.
I have changed anything in SABnzbd so can't think that it is on my side.
Can't see any issues from my end.
Are other downloads also slow?
Everything else is fine, just the Linux Distro nzbs that are not working.

traceroute to 199.189.118.227 (199.189.118.227), 64 hops max, 52 byte packets
1 netgear.muffin.lan (172.16.0.1) 875.542 ms 3.567 ms 1.078 ms
2 105-236-15-1-esr-lo.mtnbusiness.co.za (105.236.15.1) 7.247 ms 8.104 ms 7.804 ms
3 41.181.221.246 (41.181.221.246) 8.936 ms 56.887 ms 24.222 ms
4 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 9.291 ms 9.573 ms 33.200 ms
5 jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114) 9.609 ms 8.868 ms 9.346 ms
6 41.181.180.10 (41.181.180.10) 189.726 ms 199.667 ms 190.049 ms
7 ls-cr-2.uk--rb-cr-1.za-g.mtnns.net (196.44.31.114) 206.116 ms 206.181 ms 245.707 ms
8 ls-pr-1.uk--ls-cr-2.uk-a.mtn.net (209.212.111.201) 206.006 ms 205.751 ms 205.022 ms
9 tengigabitethernet8-2.ar6.lon3.gblx.net (208.48.238.185) 189.528 ms 189.210 ms 189.194 ms
10 jfk-brdr-04.inet.qwest.net (63.235.40.57) 357.103 ms 306.781 ms 307.224 ms
11 * * *
12 65.114.177.38 (65.114.177.38) 349.511 ms
63-158-61-170.dia.static.qwest.net (63.158.61.170) 613.684 ms 335.065 ms
13 65.114.177.38 (65.114.177.38) 585.481 ms !X 486.983 ms !X *
traceroute to 196.38.114.236 (196.38.114.236), 64 hops max, 52 byte packets
1 netgear.muffin.lan (172.16.0.1) 1.342 ms 1.075 ms 1.142 ms
2 105-236-15-1-esr-lo.mtnbusiness.co.za (105.236.15.1) 7.073 ms 7.421 ms 7.644 ms
3 ipc-recieve-jh-3a.za.mtnbusiness.net (41.181.178.29) 8.943 ms 35.761 ms 9.435 ms
4 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 9.456 ms 9.894 ms 8.842 ms
5 jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114) 10.475 ms 9.307 ms
jh-dca-2.za--qux-q.za.mtnbusiness.net (196.31.180.4) 9.263 ms
6 41.181.180.10 (41.181.180.10) 11.206 ms
jh-cr-2.za--jh-dca-2.za-a.mtnns.net (196.44.0.224) 11.153 ms
41.181.180.10 (41.181.180.10) 10.470 ms
7 196.44.0.72 (196.44.0.72) 9.671 ms 9.766 ms
jh-pr-1.za--jh-cr-2.za.mtnns.net (196.44.0.222) 11.986 ms
8 41-208-29-125.mtnns.net (41.208.29.125) 10.644 ms 10.858 ms 10.143 ms
9 168.209.1.140 (168.209.1.140) 11.691 ms
core1a-pkl-te-1-2.ip.isnet.net (168.209.1.139) 12.220 ms 11.187 ms
10 core1a-pkl-te1-2.isnet.net (168.209.100.238) 12.214 ms
core1a-bry-te0-0-0-1.ip.isnet.net (168.209.100.78) 28.876 ms
core1a-pkl-te1-2.isnet.net (168.209.100.238) 13.791 ms
I'm limited to 5.6MB as well on a 20MB business account.
lol at their shaping policies.
Shaping shouldn't lower the overall speed - only how certain things perform. Throttling is the overall lowing of your speed. In this case it's probably just contention with other users.
You mean insufficient ipc? This cannot be.
Shaping shouldn't lower the overall speed - only how certain things perform. Throttling is the overall lowing of your speed. In this case it's probably just contention with other users.
Hi Bryn26
I think that it is clear from your posts here that you are an Afrihost employee.
As for your comment, no. There is no contention when your speedtest is a flatline at 5.6MB. Contention would have spikes.
Seriously, just admit that Afrihost has a problem and things would be better.