Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
"Enough" bandwidth is when no contention occurs at any point of the day. In theory with the bandwidth we have available, contention will not happen at any point.
If it is not contention, then we're running out of possibilities. Shaping?

Can you move some bandwidth over to Axxess?
 
"Enough" bandwidth is when no contention occurs at any point of the day. In theory with the bandwidth we have available, contention will not happen at any point.
If your bandwidth isn't the problem, but the problem only manifests during periods of high usage then you have a rogue bandwidth management problem or a rogue routing rule.
 
If your bandwidth isn't the problem, but the problem only manifests during periods of high usage then you have a rogue bandwidth management problem or a rogue routing rule.
Yep, otherwise known as an overactive shaper.
 
The whole notice board issue seems to be down to the executives not wanting black marks on their spreadsheets. Its like the police, if you don't report the crime you can pretend crime isn't happening.
 
If it is not contention, then we're running out of possibilities. Shaping?

Can you move some bandwidth over to Axxess?

That is partly the struggle that we are having, is in finding out why this latency is happening and to find a permanent solution for it.

If purchasing additional bandwidth would resolve the issue, we would definitely have already done so.
 
The most senior person a customer can reach informed me.

Interesting... Thanks for sharing, definitely something that we need to look into, from what I understood Axxess was experiencing the same issue that we are, and that it wasn't related to contention. Definitely something to look into.
 
If your bandwidth isn't the problem, but the problem only manifests during periods of high usage then you have a rogue bandwidth management problem or a rogue routing rule.

I'm pretty sure that is where our issue is, finding the exact cause is tricky as we cannot simply unplug the bandwidth management tool results in very bad things happening...
 
Yep, otherwise known as an overactive shaper.

Hmmmmm... BUT this is * never * done on Afrihost capped accounts... but, come to think of it, this is behaving exactly like the soft-cap Afrihost++ "benefit" on my accounts.

Same latency introduction... same throughput throttle, same useless "functionality".

Round the mulberry bush again time it seems...

/meh
 
The whole notice board issue seems to be down to the executives not wanting black marks on their spreadsheets. Its like the police, if you don't report the crime you can pretend crime isn't happening.

I don't think that is the case, there are no consequences to putting up a notice, if there is an issue that the Higher-ups deem problematic enough, we will put up a notice.
 
I don't think that is the case, there are no consequences to putting up a notice, if there is an issue that the Higher-ups deem problematic enough, we will put up a notice.

Haha of course there are consequences for a poorly performing network... Putting up a notice is Afrihost officially admitting there is a problem, too many of those and it looks bad on the monthly reports.
 
I don't think that is the case, there are no consequences to putting up a notice, if there is an issue that the Higher-ups deem problematic enough, we will put up a notice.
Both Afrihost and Axxess are giving their customers a very rough experience wrt performance, yet the status light remains green.

They both seem to follow the same script in support calls as well. Blame Telkom and the customers' lines, then say nobody else is experiencing the problem.

A little honesty would help with customer relations. We know when we are being 'soft-soaped'.
 


So only time for normal latencies is at 00:00? I played just now it was fine, then suddenly got 300ms on international and at the moment 75ms on Teamspeak.

C:\Users\Henri>tracert www.afrihost.com

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

1 1 ms <1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 * * * Request timed out.
3 107 ms 98 ms 95 ms 41.181.54.85
4 104 ms 99 ms 99 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]

5 73 ms 69 ms 88 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 82 ms 83 ms 82 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 88 ms 86 ms 89 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

8 102 ms 104 ms 100 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
9 102 ms 99 ms 100 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.

These latencies only occured at 8pm, now it does in afternoon as well?
 
I'm sooooo glad I moved yesterday to another ISP...but also pissed at myself at the same time for not doing it sooner. I've been fed lies upon lies for weeks. I've done so many tracerts and speedtests...and this test and that test...trying to phone AH's call center...logging tickets...

At the end of the day...just move...only thing currently you can do.
 
local ping still 106ms on AH.... 11ms on Vox...

Download speed does seem to be back to normal.
http://www.speedtest.net/my-result/4439069535


Tracing route to www.afrihost.co.za [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 6 ms 6 ms 6 ms 105-236-240-129-esr-lo.mtnbusiness.co.za [105.236.240.129]
3 155 ms 164 ms 160 ms 41.181.51.182
4 115 ms 174 ms 105 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 116 ms 109 ms 111 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 171 ms 203 ms 161 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 173 ms 175 ms 173 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
8 124 ms 124 ms 122 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
Last edited:
4439076460.png
 
My 40mb line has gone down the tubes again this week in the East, ping is high and web pages failing to load..



traceroute to www.google.com (216.58.210.4), 30 hops max, 38 byte packets
1 * * *
2 41.181.221.217 (41.181.221.217) 349.862 ms 353.381 ms 342.654 ms
3 41.181.221.218 (41.181.221.218) 340.746 ms 322.121 ms 318.159 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 318.572 ms 323.850 ms 329.685 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 319.298 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 333.467 ms rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 322.934 ms
6 41.181.139.109 (41.181.139.109) 342.431 ms 342.696 ms 336.424 ms
7 72.14.194.74 (72.14.194.74) 340.420 ms 325.100 ms 332.158 ms
8 66.249.95.8 (66.249.95.8) 504.036 ms 487.629 ms 486.944 ms
9 216.239.51.7 (216.239.51.7) 504.713 ms 492.490 ms 489.392 ms
10 216.239.51.2 (216.239.51.2) 474.755 ms 454.157 ms 469.212 ms
11 209.85.250.169 (209.85.250.169) 505.215 ms 487.867 ms 491.395 ms
12 lhr08s06-in-f4.1e100.net (216.58.210.4) 492.851 ms 500.622 ms 495.719 ms
 
I'm sooooo glad I moved yesterday to another ISP...but also pissed at myself at the same time for not doing it sooner. I've been fed lies upon lies for weeks. I've done so many tracerts and speedtests...and this test and that test...trying to phone AH's call center...logging tickets...

At the end of the day...just move...only thing currently you can do.

I'm really sorry that you had to move to a different ISP to get the performance that you need. Definitely a case of us dropping the ball.

Once things are running again as they should be, and you are willing to give us a try again, send me a PM and I'll get you a full test account.
 
Both Afrihost and Axxess are giving their customers a very rough experience wrt performance, yet the status light remains green.

They both seem to follow the same script in support calls as well. Blame Telkom and the customers' lines, then say nobody else is experiencing the problem.

A little honesty would help with customer relations. We know when we are being 'soft-soaped'.

I can't speak for Axxess, but we certainly try to be as open and forthright as possible, at all times.

What do you mean by "soft-soaped"? I've never heard that term with regards to ADSL before.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X