Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Hey Afriman

I understand that you have already given more than enough away this month. I must thank you for the delivery of my MiFi, its a cool little gadget :) I was just wondering if there is going to be a "Mystery Bonus" this month. If not I'll just top up my capped account as normal.

P.S.
Tell Gian he is doing a brilliant job and I can't wait to see what is going to happen next

HAHAHA! Dude, this is so funny, reading in relation to your last post!!

I don't have any confirmation on capped promos. As soon as I see Gian, I'll be banging his door down demanding answers :)
 
Thanks Afrihost for the extra gigs :D I really needed it since I've run out :D

fDbugOK.png
 
@afriguy Am I missing something with the new capped prices? I only see a price change for the capped stand alone packages and not the capped bundled packages. Are the bundles also dropping in price?
 
@afriguy Am I missing something with the new capped prices? I only see a price change for the capped stand alone packages and not the capped bundled packages. Are the bundles also dropping in price?

The Capped Bundle packages aren't seeing a price drop as they're already quite heavily discounted when combined with the line.
 
Any problems on the network ? Some pages just time out.. like myBB. I now switched to Telskommel account and it seems fine.
 
No issues that we are aware of. Have you switched back to us yet? Drop me a PM :(

Howzit Afriman.

I'm encountering significant issues. Refer tracert below. :(
Code:
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.1
  2     8 ms     8 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3   741 ms   711 ms   511 ms  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
  4   466 ms   607 ms   657 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
  5   328 ms     9 ms     9 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  6   679 ms   601 ms   473 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
  7   428 ms   548 ms   619 ms  ct-cr-2.za--rb-cr-1.za.mtnns.net [196.44.31.69]
  8   396 ms    56 ms    32 ms  jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
  9   712 ms   711 ms   266 ms  196.30.1.39
 10   420 ms   427 ms    37 ms  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
 11     *      759 ms    32 ms  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
 12    30 ms    34 ms    30 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Pings... showing the same!
Code:
Ping statistics for 197.242.144.102:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 824ms, Average = 367ms
 
On 30GB usage, and I'm getting shaped? You have got to be *(&@^!@$$ kidding me... This is pathetic afrihost. How are people doing 600GB on a 2mbps account and I can't even get 1mbps worth of bandwidth on my 2mbps line from you $*&#^
 


Howzit Afriman.

I'm encountering significant issues. Refer tracert below. :(
Code:
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.1
  2     8 ms     8 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3   741 ms   711 ms   511 ms  ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
  4   466 ms   607 ms   657 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
  5   328 ms     9 ms     9 ms  compj-cpt-1.mtnns.net [196.44.18.2]
  6   679 ms   601 ms   473 ms  ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
  7   428 ms   548 ms   619 ms  ct-cr-2.za--rb-cr-1.za.mtnns.net [196.44.31.69]
  8   396 ms    56 ms    32 ms  jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
  9   712 ms   711 ms   266 ms  196.30.1.39
 10   420 ms   427 ms    37 ms  tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
 11     *      759 ms    32 ms  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
 12    30 ms    34 ms    30 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Pings... showing the same!
Code:
Ping statistics for 197.242.144.102:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 824ms, Average = 367ms

We saw a huge increase in demand, might be related to Apple updates last night. I couldn't get my devices to update - got errors from the Apple server, so just left it. We saw that demand only slacked off after around 11pm and everyone pretty much seemed to have normal service after that.

Let's hope everyone got their iOS fix last night, and all is back to normal tonight :)
 
On 30GB usage, and I'm getting shaped? You have got to be *(&@^!@$$ kidding me... This is pathetic afrihost. How are people doing 600GB on a 2mbps account and I can't even get 1mbps worth of bandwidth on my 2mbps line from you $*&#^

Since we're on the capped thread, I'm assuming you're on a Capped account there is no shaping at all applied to capped (or Business) products.

If not, remember that we only shape when demand is at its heaviest. Regardless of your usage, anyone could be potentially shaped to bring usage in line with demand. Our aim is to shape as few people as possible (to the least extent) but when demand is so high, as we're currently seeing with what we suspect to be related to Apple updates, we have to shape as many users as possible to protect the overall experience. So to ensure that you still have useable real time services (in fact to try to still provide an awesome experience is closer to what we're aiming for) we have to shape torrents and downloads to prevent slow throughput and high latency in general :(
 
Since we're on the capped thread, I'm assuming you're on a Capped account there is no shaping at all applied to capped (or Business) products.

If not, remember that we only shape when demand is at its heaviest. Regardless of your usage, anyone could be potentially shaped to bring usage in line with demand. Our aim is to shape as few people as possible (to the least extent) but when demand is so high, as we're currently seeing with what we suspect to be related to Apple updates, we have to shape as many users as possible to protect the overall experience. So to ensure that you still have useable real time services (in fact to try to still provide an awesome experience is closer to what we're aiming for) we have to shape torrents and downloads to prevent slow throughput and high latency in general :(

I'm currently testing your Capped connection and I am getting the same result - latency on the mtn IPC.

Code:
C:\Users>tracert mybroadband.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    39 ms     8 ms     8 ms  105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.1]
 [b] 3   120 ms   118 ms   120 ms  ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17][/b]
  4     *      107 ms   106 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   105 ms   104 ms   101 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6    90 ms    94 ms    99 ms  jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
  7   106 ms     *      100 ms  196.44.31.99
  8   106 ms     *       98 ms  196.30.1.39
  9   124 ms     *      119 ms  tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.21]
 10    92 ms    87 ms    87 ms  tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
 11   110 ms   117 ms   124 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12   108 ms   105 ms   103 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13   119 ms   129 ms   129 ms  mybroadband.co.za [41.203.21.137]

Trace complete.
 
No issues that we are aware of. Have you switched back to us yet? Drop me a PM :(

Will check it out today again when I get home. Guess it had to do with all the apple updates or all the extra free gigs some capped users got :whistle:
 
I'm currently testing your Capped connection and I am getting the same result - latency on the mtn IPC.

Code:
C:\Users>tracert mybroadband.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    39 ms     8 ms     8 ms  105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.1]
 [b] 3   120 ms   118 ms   120 ms  ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17][/b]
  4     *      107 ms   106 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   105 ms   104 ms   101 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6    90 ms    94 ms    99 ms  jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
  7   106 ms     *      100 ms  196.44.31.99
  8   106 ms     *       98 ms  196.30.1.39
  9   124 ms     *      119 ms  tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.21]
 10    92 ms    87 ms    87 ms  tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
 11   110 ms   117 ms   124 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12   108 ms   105 ms   103 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13   119 ms   129 ms   129 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Are you still seeing latency spikes on the local hops?
 
Are you still seeing latency spikes on the local hops?

Yup
Code:
C:\Users>tracert mybroadband.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     8 ms     8 ms  105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.1]
  3    97 ms    95 ms    97 ms  ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
  4   110 ms   109 ms   109 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   121 ms   113 ms   115 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6   109 ms   107 ms   108 ms  jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
  7   112 ms   114 ms   112 ms  196.44.31.99
  8    94 ms    97 ms    91 ms  196.30.1.39
  9    95 ms    91 ms    89 ms  tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net[196.31.220.21]
 10    96 ms    98 ms    99 ms  tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
 11   106 ms   103 ms    97 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12   117 ms   123 ms   116 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13   119 ms   124 ms   121 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Code:
C:\Users>ping -n 10 mybroadband.co.za

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=89ms TTL=56
Reply from 41.203.21.137: bytes=32 time=109ms TTL=56
Reply from 41.203.21.137: bytes=32 time=90ms TTL=56
Reply from 41.203.21.137: bytes=32 time=81ms TTL=56
Reply from 41.203.21.137: bytes=32 time=82ms TTL=56
Reply from 41.203.21.137: bytes=32 time=84ms TTL=56
Reply from 41.203.21.137: bytes=32 time=77ms TTL=56
Reply from 41.203.21.137: bytes=32 time=89ms TTL=56
Reply from 41.203.21.137: bytes=32 time=85ms TTL=56
Reply from 41.203.21.137: bytes=32 time=75ms TTL=56

Ping statistics for 41.203.21.137:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 109ms, Average = 86ms

EDIT:
To rule out the exchange or the line, on using my mweb uncapped connection I have 13ms local latencies.

It's also not really a spike, more of a consistent 90ms
 
Last edited:
Yup
Code:
C:\Users>tracert mybroadband.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     8 ms     8 ms  105-236-2-1-esr-lo.mtnbusiness.co.za [105.236.2.1]
  3    97 ms    95 ms    97 ms  ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178.17]
  4   110 ms   109 ms   109 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   121 ms   113 ms   115 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6   109 ms   107 ms   108 ms  jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
  7   112 ms   114 ms   112 ms  196.44.31.99
  8    94 ms    97 ms    91 ms  196.30.1.39
  9    95 ms    91 ms    89 ms  tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.net[196.31.220.21]
 10    96 ms    98 ms    99 ms  tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
 11   106 ms   103 ms    97 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12   117 ms   123 ms   116 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]
 13   119 ms   124 ms   121 ms  mybroadband.co.za [41.203.21.137]

Trace complete.

Code:
C:\Users>ping -n 10 mybroadband.co.za

Pinging mybroadband.co.za [41.203.21.137] with 32 bytes of data:
Reply from 41.203.21.137: bytes=32 time=89ms TTL=56
Reply from 41.203.21.137: bytes=32 time=109ms TTL=56
Reply from 41.203.21.137: bytes=32 time=90ms TTL=56
Reply from 41.203.21.137: bytes=32 time=81ms TTL=56
Reply from 41.203.21.137: bytes=32 time=82ms TTL=56
Reply from 41.203.21.137: bytes=32 time=84ms TTL=56
Reply from 41.203.21.137: bytes=32 time=77ms TTL=56
Reply from 41.203.21.137: bytes=32 time=89ms TTL=56
Reply from 41.203.21.137: bytes=32 time=85ms TTL=56
Reply from 41.203.21.137: bytes=32 time=75ms TTL=56

Ping statistics for 41.203.21.137:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 75ms, Maximum = 109ms, Average = 86ms

EDIT:
To rule out the exchange or the line, on using my mweb uncapped connection I have 13ms local latencies.

It's also not really a spike, more of a consistent 90ms

Thanks for the feedback, although not a whole lot better at least we aren't seeing any timeouts on the hops. We'll continue to monitor the IPC traffic.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X