Any idea what your 30-day rolling window usage is?
I've done 160GB since the move (16th Oct) and 277GB since the 7th October. (Worked out as 1GB = 1,000MB).
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Any idea what your 30-day rolling window usage is?
HaHa they see most of us decided to quit / leave so now they don't even reply on this thread anymore![]()
This type of throttling by the ISP means that it is at the ISP's door...I wonder how much all these issues can be attributed to Telkoms account upgrades and their inability to accommodate the extra bandwidth requirements?? Ultimately, at the end of the day the buck always stops at their front door and we know how efficient and effective they are!!
My usage last night:
View attachment 27114
From 1am to 2am it was 1Mbit.
From 2am to 3am it slowly creeped up to 4Mbit
From 3am to 4:30am it remained at roughly 4Mbit
From 4:30am to 6:30am it jumped to and remained at 10Mbit (maintaining above 1000kb/s which is more than I'm used to).
Currently it's at 4Mbit again.
This shaping or throttling nonsense is the most irritating inconsistent mess ever.
View attachment 27116
View attachment 27118
![]()
So inconsistent!!!
MyBB should do an article on the poor performance. Maybe then Afrihost will wake up.
Afrihost made a lot of friends with the excellent performance and value of these accounts from May until the switch to the MTN network. I think many of us still want to believe that the performance we got on the IS network is the way Afrihost wants these accounts to run and are prepared to wait a few days to see if they get restored to what they were before the switch. Unfortunately we have all paid for the month so cancelling now will only take effect from next month. Surely Afrihost must realize that they risk a flood of cancellations closer to the end of the month if they don't do something urgent. I am all for punishing a service provider for bad service and fully intend to cancel before the end of the month if it stays like this. Does anyone know if it is possible to cancel now and then perhaps if normal service is restored to stop the cancellation via client zone?
YSimple question: What exactly stopped them from pretesting the network themselves AND bringing over a few to test?
Simple question: What exactly stopped them from pretesting the network themselves AND bringing over a few to test?
Guys, this is not shaping, its THROTTLING. If I didn't know better, I'd say Afrihost's technical department don't actually KNOW how to setup & manage shaping models on even a basic level.
I've been singing Afrihost's praises for a while now, even during the transition to MTN (I was one of the lucky low-ish latency customers), but since this last weekend things have just gotten silly.
Mweb's 6-month contract special (with 2 months free) on their 10mb uncapped bundle works out to roughly the same as Afrihost's 10mb uncapped bundle (R1359*6 - R2718 = R906pm vs. R897pm). Even though this price is over the first 6 months, I'm still VERY tempted to move back.
AFRIHOST, STOP THROTTLING THE INNOCENT USERS AND GET YOURSELVES INTO SHAPE
(see what i did there)
$ ping -c 10 105.236.3.129
PING 105.236.3.129 (105.236.3.129) 56(84) bytes of data.
64 bytes from 105.236.3.129: icmp_req=1 ttl=253 time=288 ms
64 bytes from 105.236.3.129: icmp_req=2 ttl=253 time=257 ms
64 bytes from 105.236.3.129: icmp_req=3 ttl=253 time=256 ms
64 bytes from 105.236.3.129: icmp_req=4 ttl=253 time=240 ms
64 bytes from 105.236.3.129: icmp_req=5 ttl=253 time=249 ms
64 bytes from 105.236.3.129: icmp_req=6 ttl=253 time=251 ms
64 bytes from 105.236.3.129: icmp_req=7 ttl=253 time=253 ms
64 bytes from 105.236.3.129: icmp_req=8 ttl=253 time=255 ms
64 bytes from 105.236.3.129: icmp_req=9 ttl=253 time=258 ms
64 bytes from 105.236.3.129: icmp_req=10 ttl=253 time=262 ms
--- 105.236.3.129 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9010ms
rtt min/avg/max/mdev = 240.692/257.519/288.516/11.753 ms
They probably did do just that. The problem is we told them their network would fall to crap when they moved to MTN, they said just watch this space.
To be fair they did do this with the Rage vouchers and a few MyBB users (me being one of them). Of course there was no way for us to know QoS hadn't been setup when we were testing.
As I've said before, no expense is being spared to address this problem, and to get things to where they should be.
Let me rather give you an idea of what is being done. We have MTN's network people working in our offices now, as well as some guys from a 3rd party company who are helping QA the shaping and QoS - they have experience in implementing this for other ISP's. We have a think tank set up in our boardroom, and this is being overseen by our directors, who are demanding a better result. We are also getting input from our Dev team, and our General manager who manages the support channels and has a good grasp of what the current complaints relate to. We have also engaged an external company, based in JHB and CT, who are now running intensive diagnostics on the network. they are running capped and uncapped accounts alongside our major competitors and analyzing the differences in performance, including latencies and QoS, and this is being fed back into the team.
As I've said before, no expense is being spared to address this problem, and to get things to where they should be. We have the full backing of MTN to make the changes we need to the network, and policies are being implemented and adjusted in real time.
Johannesburg... London... Johannesburg. Seems pretty consistent to me for those locations.