Afrihost Business Uncapped Feedback

Status
Not open for further replies.
yeah that's my problem too. Everything works fine, streaming is broken.

Indeed it seems wide-spread througout Afrihost :/ Is MTN not perhaps shaping all video-related content on their side for some reason? Because I'm sure Afrihost wouldn't shape it on ALL customers.
 
Indeed it seems wide-spread througout Afrihost :/ Is MTN not perhaps shaping all video-related content on their side for some reason? Because I'm sure Afrihost wouldn't shape it on ALL customers.

No, we wouldn't agree to anything like that. While we are shaping downloads and torrents, as our AUP allows us to, to shape streaming would be a departure from what we promise our clients.

MTN don't influence the shaping on our network, they provide capacity to a certain point, and then we shape and provision bandwidth on the network.
 
No, we wouldn't agree to anything like that. While we are shaping downloads and torrents, as our AUP allows us to, to shape streaming would be a departure from what we promise our clients.

MTN don't influence the shaping on our network, they provide capacity to a certain point, and then we shape and provision bandwidth on the network.

But on our business accounts our streaming should be sweet any time of the day or night? I don't know if there is anything we can do to test it out for you? Streaming sucks, and I fire up NZBs and get 1.2MB/s instantly. Speedtest gives 10Mb connection.

Maybe I can try do some hardcore streaming tonight and then if it's crappy PM you the details on Monday, would you be able to look back on my account and see what was happening at the time in terms of performance?
 
But on our business accounts our streaming should be sweet any time of the day or night? I don't know if there is anything we can do to test it out for you? Streaming sucks, and I fire up NZBs and get 1.2MB/s instantly. Speedtest gives 10Mb connection.

Maybe I can try do some hardcore streaming tonight and then if it's crappy PM you the details on Monday, would you be able to look back on my account and see what was happening at the time in terms of performance?

Correct, the Business Uncapped accounts aren't shaped at all.
Download content from an NZB can produce pretty good speeds - multiple connections are made and latency doesn't really matter. Streaming runs a bit differently.

Run some further tests and PM AfriMan/ myself and we'll be sure to get things sorted!
 
My downloads have been good all month, lets hope the streaming on Supersport is better later this evening and tomorrow. Don't want to miss most of the rugby due to streaming
 
Hi guys, new to Business Uncapped - after a stressful evening of utter confusion as per usual the Legend (AfriGuy) has sorted out. Btw I'm on 4meg uncapped and so far it's brutal (in a good way).
 
@Afriguy - I am really not happy with the response I received on ticket LPG-306-41392:

Afrihost said:
Kindly note that we have tested everything on the account and checked the exchange congestion and see that there are only 10% of ports available during
normal hours. When the exchange gets to a peak period which seems to be from 5:30pm to 12am, there available ports are all use up and causes
latency on the network. There isn't anything that we can do to get the Telkom exchange resolved, as the line is with Telkom and it is their hardware.

The connection on the exchange needs to be escalated to Telkom and they either need to upgrade the current exchange or
put in a new exchange.

Telkom has confirmed that there is no congestion on the exchange and the above statement makes zero sense, as even right now (Saturday, 6am) there is high latency:

Code:
traceroute to 206.127.159.243 (206.127.159.243), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  4.144 ms  1.068 ms  1.212 ms
 2  105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129)  10.335 ms  9.902 ms  10.145 ms
 3  ipc-recieve-jh-2a.za.mtnbusiness.net (41.181.178.17)  11.618 ms  11.530 ms  10.811 ms
 4  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  11.785 ms  10.890 ms  11.604 ms
 5  jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114)  11.325 ms  11.694 ms  11.044 ms
 6  am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141)  204.667 ms  204.599 ms  336.381 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  205.115 ms  204.819 ms  217.041 ms
 8  4.69.162.141 (4.69.162.141)  211.665 ms
    4.69.162.137 (4.69.162.137)  226.191 ms  233.253 ms
 9  ae-57-112.ebr1.amsterdam1.level3.net (4.69.153.189)  225.291 ms  240.123 ms
    ae-56-111.ebr1.amsterdam1.level3.net (4.69.153.185)  232.271 ms
10  ae-45-45.ebr2.dusseldorf1.level3.net (4.69.143.198)  247.884 ms  233.748 ms
    ae-46-46.ebr2.dusseldorf1.level3.net (4.69.143.202)  410.244 ms
 
Afriman,

I am down on my knee's please please introduce Static IP on Capped DSL accounts :love:

Please I only need about 20GB a month, don't need uncapped for my Static IP :cry:
 
Afriman,

I am down on my knee's please please introduce Static IP on Capped DSL accounts :love:

Please I only need about 20GB a month, don't need uncapped for my Static IP :cry:

If the uptake is good enough on Business, there is a chance. But I really can't promise if or when. Our Business accounts are really affordable though - take the plunge ;)
 
@Afriguy - I am really not happy with the response I received on ticket LPG-306-41392:



Telkom has confirmed that there is no congestion on the exchange and the above statement makes zero sense, as even right now (Saturday, 6am) there is high latency:

Code:
traceroute to 206.127.159.243 (206.127.159.243), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  4.144 ms  1.068 ms  1.212 ms
 2  105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129)  10.335 ms  9.902 ms  10.145 ms
 3  ipc-recieve-jh-2a.za.mtnbusiness.net (41.181.178.17)  11.618 ms  11.530 ms  10.811 ms
 4  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  11.785 ms  10.890 ms  11.604 ms
 5  jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114)  11.325 ms  11.694 ms  11.044 ms
 6  am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141)  204.667 ms  204.599 ms  336.381 ms
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  205.115 ms  204.819 ms  217.041 ms
 8  4.69.162.141 (4.69.162.141)  211.665 ms
    4.69.162.137 (4.69.162.137)  226.191 ms  233.253 ms
 9  ae-57-112.ebr1.amsterdam1.level3.net (4.69.153.189)  225.291 ms  240.123 ms
    ae-56-111.ebr1.amsterdam1.level3.net (4.69.153.185)  232.271 ms
10  ae-45-45.ebr2.dusseldorf1.level3.net (4.69.143.198)  247.884 ms  233.748 ms
    ae-46-46.ebr2.dusseldorf1.level3.net (4.69.143.202)  410.244 ms

To be honest, I'm not really sure what is meant here, it seems a little unclear. However Darryl is our support manager and is very experienced and proficient technically. I think perhaps we need to clarify what he meant and go from there. Will drop him a mail and get a little more clarity so we can figure out how to proceed.
 
Hi guys, new to Business Uncapped - after a stressful evening of utter confusion as per usual the Legend (AfriGuy) has sorted out. Btw I'm on 4meg uncapped and so far it's brutal (in a good way).

Awesome, AfriGuy is a legend indeed. Will have to watch my back - might become redundant soon :)
 
To be honest, I'm not really sure what is meant here, it seems a little unclear. However Darryl is our support manager and is very experienced and proficient technically. I think perhaps we need to clarify what he meant and go from there. Will drop him a mail and get a little more clarity so we can figure out how to proceed.

I honestly don't think it is a exchange congestion issue. I have just tested the same with a Webafrica trial account:
2997342863.png2997343574.png2997344760.png

compared with Afrihost (which is internationally slower in all cases):
2997352177.png2997353710.png2997355268.png

Compare the traceroutes (Afrihost):
Code:
GNaschenweng@GNaschenweng-2 ~]$ traceroute 206.127.159.224
traceroute to 206.127.159.224 (206.127.159.224), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  3.995 ms  1.046 ms  1.276 ms
 2  105-236-6-129-esr-lo.mtnbusiness.co.za (105.236.6.129)  8.095 ms  8.267 ms  7.424 ms
 3  ipc-recieve-jh-1a.za.mtnbusiness.net (41.181.178.5)  10.476 ms  10.495 ms  9.745 ms
 4  qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115)  10.223 ms  10.370 ms  9.950 ms
 5  jh-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.114)  23.381 ms  11.417 ms  10.073 ms
 6  am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141)  203.038 ms * *
 7  xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89)  501.374 ms  270.490 ms  340.870 ms
 8  4.69.162.129 (4.69.162.129)  207.041 ms  408.805 ms
    4.69.162.137 (4.69.162.137)  307.303 ms
 9  ae-59-114.ebr1.amsterdam1.level3.net (4.69.153.197)  249.796 ms  225.176 ms
    ae-57-112.ebr1.amsterdam1.level3.net (4.69.153.189)  509.925 ms
10  ae-47-47.ebr2.dusseldorf1.level3.net (4.69.143.206)  306.806 ms
    ae-46-46.ebr2.dusseldorf1.level3.net (4.69.143.202)  218.179 ms
    ae-47-47.ebr2.dusseldorf1.level3.net (4.69.143.206)  393.862 ms
11  ae-21-21.ebr1.dusseldorf1.level3.net (4.69.143.181)  308.620 ms  208.400 ms
    ae-23-23.ebr1.dusseldorf1.level3.net (4.69.143.189)  224.868 ms
12  ae-47-47.ebr3.frankfurt1.level3.net (4.69.143.174)  1383.381 ms
    ae-46-46.ebr3.frankfurt1.level3.net (4.69.143.170)  1251.386 ms  515.025 ms
13  ae-83-83.csw3.frankfurt1.level3.net (4.69.163.10)  1017.898 ms
    ae-93-93.csw4.frankfurt1.level3.net (4.69.163.14)  870.523 ms *
14  ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  278.371 ms
    ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10)  208.831 ms
    ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  229.075 ms
15  195.16.161.58 (195.16.161.58)  371.871 ms  372.071 ms  373.299 ms
16  206-127-157-86.plaync.com (206.127.157.86)  363.954 ms  359.068 ms  361.147 ms
17  206-127-157-102.plaync.com (206.127.157.102)  358.350 ms  350.657 ms  353.073 ms
18  206-127-157-102.plaync.com (206.127.157.102)  351.845 ms !X *  354.985 ms !X

vs Webafrica:
Code:
GNaschenweng@GNaschenweng-2 ~]$ traceroute 206.127.159.224
traceroute to 206.127.159.224 (206.127.159.224), 64 hops max, 52 byte packets
 1  netgear.muffin.lan (172.16.0.1)  4.035 ms  1.093 ms  1.250 ms
 2  196-210-154-1.dynamic.isadsl.co.za (196.210.154.1)  7.875 ms  7.792 ms  7.413 ms
 3  196.38.72.229 (196.38.72.229)  10.324 ms  9.348 ms  9.850 ms
 4  cdsl2-rba-vl150.ip.isnet.net (196.38.73.9)  9.724 ms  10.449 ms  9.577 ms
 5  core2b-pkl-te0-0-0-0.ip.isnet.net (196.26.0.63)  12.442 ms  14.926 ms  12.092 ms
 6  core2b-dock-tenge-0-3-0-0-126.ip.isnet.net (168.209.201.81)  191.452 ms  191.481 ms  191.808 ms
 7  195.50.124.33 (195.50.124.33)  550.703 ms  193.930 ms  193.215 ms
 8  vl-3601-ve-225.csw2.london1.level3.net (4.69.166.145)  213.960 ms  320.928 ms
    vl-3604-ve-228.csw2.london1.level3.net (4.69.166.157)  307.143 ms
 9  ae-59-224.ebr2.london1.level3.net (4.69.153.141)  228.441 ms  204.399 ms
    ae-57-222.ebr2.london1.level3.net (4.69.153.133)  203.316 ms
10  ae-24-24.ebr2.frankfurt1.level3.net (4.69.148.198)  198.583 ms  198.878 ms
    ae-23-23.ebr2.frankfurt1.level3.net (4.69.148.194)  207.881 ms
11  ae-82-82.csw3.frankfurt1.level3.net (4.69.140.26)  195.998 ms
    ae-92-92.csw4.frankfurt1.level3.net (4.69.140.30)  203.863 ms
    ae-62-62.csw1.frankfurt1.level3.net (4.69.140.18)  212.394 ms
12  ae-3-80.edge6.frankfurt1.level3.net (4.69.154.138)  198.605 ms
    ae-4-90.edge6.frankfurt1.level3.net (4.69.154.202)  192.899 ms
    ae-1-60.edge6.frankfurt1.level3.net (4.69.154.10)  204.339 ms
13  195.16.161.58 (195.16.161.58)  193.611 ms  193.940 ms  193.818 ms
14  206-127-157-86.plaync.com (206.127.157.86)  198.219 ms  197.722 ms  198.176 ms
15  206-127-157-102.plaync.com (206.127.157.102)  218.627 ms  451.882 ms  306.769 ms
16  * * *
17  206-127-157-102.plaync.com (206.127.157.102)  355.143 ms !X * *
18  206-127-157-102.plaync.com (206.127.157.102)  214.755 ms !X * *
19  * * *
20  * * 206-127-157-102.plaync.com (206.127.157.102)  355.199 ms !X
21  * 206-127-157-102.plaync.com (206.127.157.102)  354.549 ms !X *
22  206-127-157-102.plaync.com (206.127.157.102)  353.520 ms !X *  356.033 ms !X
 
Had a hick up this morning with the exchange but the crisis has been contained!
 
Account has been absolute crap this weekend. Downloads are ok as long as I can throw dozens of connections at them, but browsing and especially streaming has been atrocious. What's the deal?
 
Account has been absolute crap this weekend. Downloads are ok as long as I can throw dozens of connections at them, but browsing and especially streaming has been atrocious. What's the deal?

Have you tried the line fix tool in the control panel?
 
Nothing wrong with the line, been tested. It's just this weekend, could be a WCape issue again.
 
To be honest, I'm not really sure what is meant here, it seems a little unclear. However Darryl is our support manager and is very experienced and proficient technically. I think perhaps we need to clarify what he meant and go from there. Will drop him a mail and get a little more clarity so we can figure out how to proceed.

Thanks - got feedback from TelkomZA and updated ticket LPG-306-41392 as the exchange previously referred to by your engineers is not congested:

TelkomZA said:
Morning

Had a look at the supplied results and previous feedback supplied, confirmed with accounts and the ADSL service was previously Wholesale but has been moved back to Telkom and is currently managed by us, unfortunately it is not an option to move you for you are connected to a UMC (Mini DSLam)
The DSLam is however not congested, it is connected via a STM1 (155meg) link running at 18% utilization during peak times, I have no idea what your ISP is referring to by "there available ports are all use up and causes
latency on the network." I will however gladly speak to the person that gave you the information if you can supply the contact details for it makes absolutely no sense.

If you look at the supplied trace route you will see that the second hop latency is +- 10ms, once an exchange is congested this hop will increase and presently there is no indication that this is the case.

From my opinion the latency is only increasing dramatically on hop :
15 195.16.161.58 (195.16.161.58) 373.754 ms 375.520 ms 477.463 ms

So would suspect your ISP`s upstream provider.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X