Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
These speeds are very up and down, have they been run across different ISP accounts for comparison?

On almost every occasion I have had bad speeds, Telkom guest account on SAIX shows 5+MB.
I don't have any other ISP accounts to test on.

Edited to add:

Case in point -

Telkom guest login:
ScreenShot106.jpg

AH:
ScreenShot107.jpg
 
Last edited:
Speeds are horrible again tonight. WTH is going on over there? IPC upgrade not holding up already??

3863615185.png


Code:
C:\>tracert www.afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     7 ms     6 ms     6 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.1]
  3    32 ms    28 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4    64 ms    78 ms    12 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    10 ms     8 ms     9 ms  jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
  6    10 ms    11 ms     8 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7    55 ms    17 ms    43 ms  196.44.31.99
  8    13 ms    12 ms    26 ms  196.30.1.39
  9    23 ms   264 ms    15 ms  196.31.220.21
 10    21 ms    20 ms    11 ms  196.31.63.202
 11    16 ms    13 ms    21 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 12    11 ms    20 ms    64 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Some BF4 pings.. Disgusting!!

BF4.jpg
 
Last edited:
No offence but really slow
On business account 4mb uncapped

on speedtest =

0.70mbps download
0.40mbps upload

used an alternative mweb account on the same line =

3.25mbps download
0.41mbps upload
 
You guys are seriously ****ing with my loyalty.

Packet loss, packet loss everywhere, can't browse **** without having to reload multiple times. Didn't have it before today. Also note normally this specific ping is at least 20ms lower, i.e. 205-210ms, and not nearly this inconsistent:

Pinging www.racedepartment.com [31.204.128.181] with 32 bytes of data:
Request timed out.
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Reply from 31.204.128.181: bytes=32 time=226ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Reply from 31.204.128.181: bytes=32 time=231ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Request timed out.
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=226ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=244ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Reply from 31.204.128.181: bytes=32 time=230ms TTL=52
Reply from 31.204.128.181: bytes=32 time=234ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Reply from 31.204.128.181: bytes=32 time=235ms TTL=52
Reply from 31.204.128.181: bytes=32 time=233ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=292ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=232ms TTL=52
Reply from 31.204.128.181: bytes=32 time=233ms TTL=52
Request timed out.
Reply from 31.204.128.181: bytes=32 time=226ms TTL=52
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Request timed out.
Reply from 31.204.128.181: bytes=32 time=231ms TTL=52
Reply from 31.204.128.181: bytes=32 time=235ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Request timed out.
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=230ms TTL=52
Reply from 31.204.128.181: bytes=32 time=237ms TTL=52
Reply from 31.204.128.181: bytes=32 time=230ms TTL=52
Request timed out.
Reply from 31.204.128.181: bytes=32 time=226ms TTL=52
Reply from 31.204.128.181: bytes=32 time=236ms TTL=52
Reply from 31.204.128.181: bytes=32 time=236ms TTL=52
Reply from 31.204.128.181: bytes=32 time=231ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52
Reply from 31.204.128.181: bytes=32 time=230ms TTL=52
Reply from 31.204.128.181: bytes=32 time=228ms TTL=52
Reply from 31.204.128.181: bytes=32 time=229ms TTL=52
Reply from 31.204.128.181: bytes=32 time=233ms TTL=52
Reply from 31.204.128.181: bytes=32 time=227ms TTL=52

Ping statistics for 31.204.128.181:
Packets: Sent = 63, Received = 57, Lost = 6 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 226ms, Maximum = 292ms, Average = 230ms

What is happening now? Let me guess, we should just wait until the extra capacity goes live. Really.
 
Traceroute to supplement my earlier post:

Tracing route to www.racedepartment.com [31.204.128.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 12 ms 11 ms 11 ms 105-236-249-1-esr-lo.mtnbusiness.co.za [105.236.249.1]
3 55 ms 14 ms 13 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178.65]
4 62 ms 15 ms 15 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 19 ms 19 ms 15 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
6 15 ms 14 ms 15 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 213 ms 212 ms 212 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]
8 211 ms 211 ms 211 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 212 ms 212 ms 215 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 221 ms 222 ms * 10ge.linx-jnpr.th-n.i3d.net [195.66.225.146]
11 239 ms 226 ms 226 ms 20ge.cr1-lr0.smartdc.rtd.i3d.net [109.200.218.173]
12 232 ms 263 ms 238 ms 80ge.br3-cr1.smartdc.rtd.i3d.net [188.122.95.85]
13 227 ms * 228 ms racedepartment.com [31.204.128.181]

Trace complete.
 
It's p0Ʃs slow tonight - even browsing is painful!

EDIT - I'm in the north

EDIT 2 - 4096 Business Uncapped

3863768941.png
 
Last edited:
I know the wait is always a frustrating one, but remember that the North & East have seen upgrades already - so that's a good sign.
It all depends on when the upgrades are available, the South has seen upgrades plenty times before everyone else.

Nonsense... not only is the South ALWAYS the last to be upgraded, but we only got 20% of the order earlier this year. At that time, we were AGAIN promised massive throughput improvement for 2 months, only for the upgrade to not even make one bit of difference. Secondly, we were then promised the remainder of the ordered IPC "as and when it became available" - this too DID NOT HAPPEN.

AH, you guys are AGAIN going to make the mistake of not provisioning enough IPC for the country, and especially for us here in the South... I foresee more issues cropping up, and worse performance from now till the end of the year.

I'm afraid the writing is on the wall... THE CURRENT CYCLE WILL CONTINUE AND IS DOOMED TO KEEP REPEATING ITSELF - NOTHING WAS LEARNT :(
 
Working just splendid here in PMB. Guess since the rest of South Africa is running like crap, the network capacity is freed up.
 
Speeds are horrible again tonight. WTH is going on over there? IPC upgrade not holding up already??

3863615185.png


Code:
C:\>tracert www.afrihost.com

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.254
  2     7 ms     6 ms     6 ms  105-236-3-1-esr-lo.mtnbusiness.co.za [105.236.3.1]
  3    32 ms    28 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4    64 ms    78 ms    12 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    10 ms     8 ms     9 ms  jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.171]
  6    10 ms    11 ms     8 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7    55 ms    17 ms    43 ms  196.44.31.99
  8    13 ms    12 ms    26 ms  196.30.1.39
  9    23 ms   264 ms    15 ms  196.31.220.21
 10    21 ms    20 ms    11 ms  196.31.63.202
 11    16 ms    13 ms    21 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 12    11 ms    20 ms    64 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Some BF4 pings.. Disgusting!!

View attachment 161839

I know you are on Business and should not be shaped, but with all the p2p management going on etc your BF4 performance might be explainable by the following.

I have a home uncapped account for home use and last night while BF4 was logged into battlelog and waiting for our server to be online, I tried to watch youtube...no go. All traffic shaped to hell. First I thought it was mumble...so I quit that and tried again. Same result. All traffic shaped. So I quit battlelog and whalla. Youtube ran perfect at 450kB/s. Start Battlelog back up...all traffic shaped.

I reported this in the Home Uncapped thread as well. It is clear that BF4's traffic signature is being handled as P2P and being shaped on home uncapped. Again since you are on business this should not effect you, but since they have been "managing" p2p and it being contended and whatnot it could explain your performance.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X