Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
AfriMan said:
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.
Click to expand...

Mate , it better be damn good changes as I already have another ISP account and all you have left is your notice period before I chuck it in with your changes....
 
avr-rulez said:
Mate , it better be damn good changes as I already have another ISP account and all you have left is your notice period before I chuck it in with your changes....
Click to expand...

I wish I could give guarantees, but I'd rather be as open as possible. We're confident that it will resolve the bulk of the symptoms reported, but we're preparing for extensive testing afterwards to see exactly what is the same, better or worse and we'll continue to work on this until we get the results we're after. I really do have confidence in the team, they have worked really hard and I think they're done a great job of absorbing all the feedback we've given them and translating this in to a solution.
 
AfriGenie said:
If the cancellation date is listed as the 30th of November 2015, it probably means there was promotional data loaded at some point, I can just update this from my side to allow the cancellation at the end of April.

If you request an ADSL line cancellation now, it should be effective from the 30th of April, with the ADSL line back with Telkom within 48 hours after that. You will not be billed twice for the ADSL line.
Click to expand...

Sent you a PM, never got a reply :/
 
Hey AfriPeeps,

Experiencing latency spikes in CPT. Line experience is, as a result, sluggish.
10mbps line topping out at ~4mbps to 5mbps.

Here's a tracert and ping. Checkout the pikes and occasional packet loss.
Something is obviously awry :(.

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     7 ms     7 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3     9 ms    11 ms     9 ms  41.181.201.94
  4    25 ms     9 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.18.188]
  5    10 ms    10 ms    11 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  6    33 ms    33 ms    33 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
  7   100 ms   101 ms    99 ms  jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
  8    33 ms    32 ms    32 ms  196.44.31.99
  9    32 ms    33 ms    34 ms  196.30.1.39
 10    98 ms    97 ms    98 ms  196.31.220.23
 11    33 ms    32 ms    32 ms  196.31.63.206
 12    34 ms    37 ms    33 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 13    32 ms    33 ms    32 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

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     7 ms     7 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3     9 ms    59 ms     8 ms  41.181.201.94
  4    13 ms     9 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
  5    10 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  6    33 ms    34 ms    33 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
  7   105 ms   114 ms   103 ms  jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
  8    33 ms    34 ms    32 ms  196.44.31.99
  9    31 ms    48 ms    33 ms  196.30.1.39
 10    84 ms    91 ms    85 ms  196.31.220.23
 11    32 ms    32 ms    32 ms  196.31.63.206
 12    41 ms    37 ms    33 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 13    32 ms    32 ms    32 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Code: 
Pinging www.afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=48ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=60ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 15, Received = 14, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 60ms, Average = 35ms
 
steel_dog said:
Hey AfriPeeps,

Experiencing latency spikes in CPT. Line experience is, as a result, sluggish.
10mbps line topping out at ~4mbps to 5mbps.

Here's a tracert and ping. Checkout the pikes and occasional packet loss.
Something is obviously awry :(.

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     7 ms     7 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3     9 ms    11 ms     9 ms  41.181.201.94
  4    25 ms     9 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.18.188]
  5    10 ms    10 ms    11 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  6    33 ms    33 ms    33 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
  7   100 ms   101 ms    99 ms  jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
  8    33 ms    32 ms    32 ms  196.44.31.99
  9    32 ms    33 ms    34 ms  196.30.1.39
 10    98 ms    97 ms    98 ms  196.31.220.23
 11    33 ms    32 ms    32 ms  196.31.63.206
 12    34 ms    37 ms    33 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 13    32 ms    33 ms    32 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

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     7 ms     7 ms     7 ms  105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
  3     9 ms    59 ms     8 ms  41.181.201.94
  4    13 ms     9 ms     9 ms  tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
  5    10 ms    10 ms     9 ms  unc-cpt-1.mtnns.net [196.44.18.8]
  6    33 ms    34 ms    33 ms  pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
  7   105 ms   114 ms   103 ms  jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
  8    33 ms    34 ms    32 ms  196.44.31.99
  9    31 ms    48 ms    33 ms  196.30.1.39
 10    84 ms    91 ms    85 ms  196.31.220.23
 11    32 ms    32 ms    32 ms  196.31.63.206
 12    41 ms    37 ms    33 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 13    32 ms    32 ms    32 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

Code: 
Pinging www.afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=48ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=60ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58

Ping statistics for 197.242.144.102:
    Packets: Sent = 15, Received = 14, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 60ms, Average = 35ms
Click to expand...

:(

That's definitely worrisome! Thanks for posting those results, we'll look into this ASAP. I believe we've already asked the networking people at MTN Business to look into this, so we should have this looking better soon.
 
AfriGenie said:
:(

That's definitely worrisome! Thanks for posting those results, we'll look into this ASAP. I believe we've already asked the networking people at MTN Business to look into this, so we should have this looking better soon.
Click to expand...
Thanks. Please share feedback when you receive any.
 
GG afrihost:

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=120ms TTL=59
Reply from 197.242.144.102: bytes=32 time=164ms TTL=59
Reply from 197.242.144.102: bytes=32 time=123ms TTL=59
Reply from 197.242.144.102: bytes=32 time=151ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 164ms, Average = 139ms

kohlhtor said:
I try to update ios 8.3 3 Hr Afrihost 10 min telkom
Click to expand...

Oh god apple released an update? RIP Afrihost for next 2 weeks. People buy up spare accounts.
 
I have issues updating apps on IOS as well. Started yesterday already. Today IOS 8.3 is released and it will apparently take 3 hours for the update on my 20 meg line!
Everything else runs well except IOS updates. Funny enough, early in the morning the updates run at full speed. Shaping IOS updates much AfriHost?
 
In Cape Town. Having major latency issues at the moment, ping around 300ms. Yet on MWEB it's 9ms... Hmmm...
 
Afrihost:

4275217858.png

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=160ms TTL=59
Reply from 197.242.144.102: bytes=32 time=136ms TTL=59
Reply from 197.242.144.102: bytes=32 time=117ms TTL=59
Reply from 197.242.144.102: bytes=32 time=127ms TTL=59

Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 117ms, Maximum = 160ms, Average = 135ms

Another ISP:

4275224935.png

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=28ms TTL=53
Reply from 197.242.144.102: bytes=32 time=28ms TTL=53
Reply from 197.242.144.102: bytes=32 time=31ms TTL=53
Reply from 197.242.144.102: bytes=32 time=28ms TTL=53

Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 31ms, Average = 28ms

Wait, I can see into the future. We will get told "Our team noticed some unusual spiking last night and have been working hard to implement fixes. You should be seeing an improvement." And then tomorrow night it will happen again.
 
Last edited:
Yes, same here at the moment ping extremely high here in Cape Town only occur around 9pm though.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X