And I thought I had issues on Business Uncapped... Stay strong man!Well, there is no shaping on my account, but I'm being treated to these wonderful speeds on my 4 Meg line:
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What is your non-negotiable item, device, or app for international travel?
Afrihost Uncapped ADSL Feedback (Pt2)
- Thread starter bwana
- Start date
- Status
HapticSimian
Honorary Master
And here...
Code:
Tracing route to any-rc.a01.yahoodns.net [98.139.102.145]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 9 ms 19 ms 11 ms 105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6.65]
3 136 ms 132 ms 123 ms ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178.5]
4 126 ms 140 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 143 ms 138 ms 137 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 290 ms 298 ms 307 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
7 329 ms 319 ms 326 ms ge-1-1-0.pat1.the.yahoo.com [195.66.224.129]
8 371 ms 434 ms 403 ms as-0.pat1.nyc.yahoo.com [66.196.65.13]
9 404 ms 422 ms 483 ms ae-2.pat1.bfz.yahoo.com [216.115.100.26]
10 582 ms 444 ms 405 ms ae-3.msr1.bf1.yahoo.com [216.115.100.29]
11 419 ms 416 ms 421 ms UNKNOWN-98-139-129-X.yahoo.com [98.139.129.171]
12 415 ms 413 ms 414 ms et-18-25.fab5-1-gdc.bf1.yahoo.com [98.139.128.61]
13 395 ms 395 ms 393 ms po-13.bas1-1-prd.bf1.yahoo.com [98.139.129.77]
14 414 ms 416 ms 403 ms w2.rc.vip.bf1.yahoo.com [98.139.102.145]
Take a look!!!
Code:
ping 41.181.178.89 -t
Pinging 41.181.178.89 with 32 bytes of data:
Reply from 41.181.178.89: bytes=32 time=113ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=102ms TTL=57
Reply from 41.181.178.89: bytes=32 time=119ms TTL=57
Reply from 41.181.178.89: bytes=32 time=122ms TTL=57
Reply from 41.181.178.89: bytes=32 time=122ms TTL=57
Reply from 41.181.178.89: bytes=32 time=117ms TTL=57
Reply from 41.181.178.89: bytes=32 time=103ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=149ms TTL=57
Reply from 41.181.178.89: bytes=32 time=125ms TTL=57
Reply from 41.181.178.89: bytes=32 time=117ms TTL=57
Reply from 41.181.178.89: bytes=32 time=137ms TTL=57
Reply from 41.181.178.89: bytes=32 time=120ms TTL=57
Reply from 41.181.178.89: bytes=32 time=124ms TTL=57
Reply from 41.181.178.89: bytes=32 time=124ms TTL=57
Reply from 41.181.178.89: bytes=32 time=122ms TTL=57
Reply from 41.181.178.89: bytes=32 time=145ms TTL=57
Reply from 41.181.178.89: bytes=32 time=118ms TTL=57
Reply from 41.181.178.89: bytes=32 time=123ms TTL=57
Reply from 41.181.178.89: bytes=32 time=121ms TTL=57
Reply from 41.181.178.89: bytes=32 time=118ms TTL=57
Reply from 41.181.178.89: bytes=32 time=118ms TTL=57
Reply from 41.181.178.89: bytes=32 time=120ms TTL=57
Reply from 41.181.178.89: bytes=32 time=123ms TTL=57
Reply from 41.181.178.89: bytes=32 time=124ms TTL=57
Reply from 41.181.178.89: bytes=32 time=120ms TTL=57
Reply from 41.181.178.89: bytes=32 time=114ms TTL=57
Reply from 41.181.178.89: bytes=32 time=148ms TTL=57
Reply from 41.181.178.89: bytes=32 time=125ms TTL=57
Reply from 41.181.178.89: bytes=32 time=113ms TTL=57
Reply from 41.181.178.89: bytes=32 time=106ms TTL=57
Reply from 41.181.178.89: bytes=32 time=101ms TTL=57
Reply from 41.181.178.89: bytes=32 time=110ms TTL=57
Reply from 41.181.178.89: bytes=32 time=106ms TTL=57
Reply from 41.181.178.89: bytes=32 time=108ms TTL=57
Reply from 41.181.178.89: bytes=32 time=99ms TTL=57
Reply from 41.181.178.89: bytes=32 time=127ms TTL=57
Reply from 41.181.178.89: bytes=32 time=107ms TTL=57
Reply from 41.181.178.89: bytes=32 time=108ms TTL=57
Reply from 41.181.178.89: bytes=32 time=138ms TTL=57
Reply from 41.181.178.89: bytes=32 time=111ms TTL=57
Reply from 41.181.178.89: bytes=32 time=103ms TTL=57
Reply from 41.181.178.89: bytes=32 time=105ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=110ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=127ms TTL=57
Reply from 41.181.178.89: bytes=32 time=106ms TTL=57
Reply from 41.181.178.89: bytes=32 time=108ms TTL=57
Reply from 41.181.178.89: bytes=32 time=115ms TTL=57
Reply from 41.181.178.89: bytes=32 time=110ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=116ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=122ms TTL=57
Reply from 41.181.178.89: bytes=32 time=95ms TTL=57
Reply from 41.181.178.89: bytes=32 time=90ms TTL=57
Reply from 41.181.178.89: bytes=32 time=113ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=105ms TTL=57
Reply from 41.181.178.89: bytes=32 time=105ms TTL=57
Reply from 41.181.178.89: bytes=32 time=102ms TTL=57
Reply from 41.181.178.89: bytes=32 time=101ms TTL=57
Reply from 41.181.178.89: bytes=32 time=98ms TTL=57
Reply from 41.181.178.89: bytes=32 time=107ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=106ms TTL=57
Reply from 41.181.178.89: bytes=32 time=97ms TTL=57
Reply from 41.181.178.89: bytes=32 time=108ms TTL=57
Reply from 41.181.178.89: bytes=32 time=105ms TTL=57
Reply from 41.181.178.89: bytes=32 time=126ms TTL=57
Reply from 41.181.178.89: bytes=32 time=88ms TTL=57
Reply from 41.181.178.89: bytes=32 time=110ms TTL=57
Reply from 41.181.178.89: bytes=32 time=130ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=103ms TTL=57
Reply from 41.181.178.89: bytes=32 time=102ms TTL=57
Reply from 41.181.178.89: bytes=32 time=109ms TTL=57
Reply from 41.181.178.89: bytes=32 time=110ms TTL=57
Reply from 41.181.178.89: bytes=32 time=113ms TTL=57
Reply from 41.181.178.89: bytes=32 time=106ms TTL=57
Reply from 41.181.178.89: bytes=32 time=120ms TTL=57
Reply from 41.181.178.89: bytes=32 time=101ms TTL=57
Reply from 41.181.178.89: bytes=32 time=102ms TTL=57
Reply from 41.181.178.89: bytes=32 time=93ms TTL=57
Reply from 41.181.178.89: bytes=32 time=95ms TTL=57
Reply from 41.181.178.89: bytes=32 time=87ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=111ms TTL=57
Reply from 41.181.178.89: bytes=32 time=89ms TTL=57
Reply from 41.181.178.89: bytes=32 time=102ms TTL=57
Reply from 41.181.178.89: bytes=32 time=100ms TTL=57
Reply from 41.181.178.89: bytes=32 time=156ms TTL=57
Reply from 41.181.178.89: bytes=32 time=93ms TTL=57
Reply from 41.181.178.89: bytes=32 time=92ms TTL=57
Reply from 41.181.178.89: bytes=32 time=100ms TTL=57
Reply from 41.181.178.89: bytes=32 time=94ms TTL=57
Reply from 41.181.178.89: bytes=32 time=95ms TTL=57
Reply from 41.181.178.89: bytes=32 time=93ms TTL=57
Reply from 41.181.178.89: bytes=32 time=95ms TTL=57
Reply from 41.181.178.89: bytes=32 time=93ms TTL=57
Reply from 41.181.178.89: bytes=32 time=83ms TTL=57
Reply from 41.181.178.89: bytes=32 time=88ms TTL=57
Reply from 41.181.178.89: bytes=32 time=88ms TTL=57
Reply from 41.181.178.89: bytes=32 time=112ms TTL=57
Reply from 41.181.178.89: bytes=32 time=84ms TTL=57
Reply from 41.181.178.89: bytes=32 time=80ms TTL=57
Reply from 41.181.178.89: bytes=32 time=87ms TTL=57
Reply from 41.181.178.89: bytes=32 time=95ms TTL=57
Reply from 41.181.178.89: bytes=32 time=83ms TTL=57
Reply from 41.181.178.89: bytes=32 time=86ms TTL=57
Reply from 41.181.178.89: bytes=32 time=79ms TTL=57
Reply from 41.181.178.89: bytes=32 time=77ms TTL=57
Reply from 41.181.178.89: bytes=32 time=89ms TTL=57
Reply from 41.181.178.89: bytes=32 time=76ms TTL=57
Reply from 41.181.178.89: bytes=32 time=72ms TTL=57
Reply from 41.181.178.89: bytes=32 time=67ms TTL=57
Reply from 41.181.178.89: bytes=32 time=69ms TTL=57
Reply from 41.181.178.89: bytes=32 time=72ms TTL=57
Reply from 41.181.178.89: bytes=32 time=79ms TTL=57
Reply from 41.181.178.89: bytes=32 time=107ms TTL=57
Reply from 41.181.178.89: bytes=32 time=75ms TTL=57
Reply from 41.181.178.89: bytes=32 time=86ms TTL=57
Reply from 41.181.178.89: bytes=32 time=76ms TTL=57
Reply from 41.181.178.89: bytes=32 time=79ms TTL=57
Reply from 41.181.178.89: bytes=32 time=73ms TTL=57
Reply from 41.181.178.89: bytes=32 time=82ms TTL=57
Reply from 41.181.178.89: bytes=32 time=78ms TTL=57
Reply from 41.181.178.89: bytes=32 time=69ms TTL=57
Reply from 41.181.178.89: bytes=32 time=84ms TTL=57
Reply from 41.181.178.89: bytes=32 time=63ms TTL=57
Reply from 41.181.178.89: bytes=32 time=79ms TTL=57
Reply from 41.181.178.89: bytes=32 time=65ms TTL=57
Reply from 41.181.178.89: bytes=32 time=77ms TTL=57
Reply from 41.181.178.89: bytes=32 time=78ms TTL=57
Reply from 41.181.178.89: bytes=32 time=68ms TTL=57
Reply from 41.181.178.89: bytes=32 time=74ms TTL=57
Reply from 41.181.178.89: bytes=32 time=70ms TTL=57
Reply from 41.181.178.89: bytes=32 time=61ms TTL=57
Reply from 41.181.178.89: bytes=32 time=55ms TTL=57
Reply from 41.181.178.89: bytes=32 time=104ms TTL=57
Reply from 41.181.178.89: bytes=32 time=70ms TTL=57
Reply from 41.181.178.89: bytes=32 time=63ms TTL=57
Reply from 41.181.178.89: bytes=32 time=62ms TTL=57
Reply from 41.181.178.89: bytes=32 time=53ms TTL=57
Reply from 41.181.178.89: bytes=32 time=59ms TTL=57
Reply from 41.181.178.89: bytes=32 time=55ms TTL=57
Reply from 41.181.178.89: bytes=32 time=71ms TTL=57
Reply from 41.181.178.89: bytes=32 time=55ms TTL=57
Reply from 41.181.178.89: bytes=32 time=70ms TTL=57
Reply from 41.181.178.89: bytes=32 time=82ms TTL=57
Reply from 41.181.178.89: bytes=32 time=57ms TTL=57
Reply from 41.181.178.89: bytes=32 time=51ms TTL=57
Reply from 41.181.178.89: bytes=32 time=62ms TTL=57
Reply from 41.181.178.89: bytes=32 time=60ms TTL=57
Reply from 41.181.178.89: bytes=32 time=64ms TTL=57
Reply from 41.181.178.89: bytes=32 time=68ms TTL=57
Reply from 41.181.178.89: bytes=32 time=65ms TTL=57
Reply from 41.181.178.89: bytes=32 time=62ms TTL=57
Reply from 41.181.178.89: bytes=32 time=62ms TTL=57
Reply from 41.181.178.89: bytes=32 time=63ms TTL=57
Reply from 41.181.178.89: bytes=32 time=56ms TTL=57
Reply from 41.181.178.89: bytes=32 time=52ms TTL=57
Reply from 41.181.178.89: bytes=32 time=66ms TTL=57
Reply from 41.181.178.89: bytes=32 time=57ms TTL=57
Reply from 41.181.178.89: bytes=32 time=63ms TTL=57
Reply from 41.181.178.89: bytes=32 time=64ms TTL=57
Reply from 41.181.178.89: bytes=32 time=74ms TTL=57
Reply from 41.181.178.89: bytes=32 time=63ms TTL=57
Reply from 41.181.178.89: bytes=32 time=64ms TTL=57
Reply from 41.181.178.89: bytes=32 time=60ms TTL=57
Ping statistics for 41.181.178.89:
Packets: Sent = 173, Received = 173, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 156ms, Average = 95ms
Hi guys
It looks like latency has jumped up again, just as everything was starting to normalise
I'm really sorry about this, it hasn't been the best of days!
Our team are looking at this and should be resolved soon.
It looks like latency has jumped up again, just as everything was starting to normalise
I'm really sorry about this, it hasn't been the best of days!Our team are looking at this and should be resolved soon.
- Joined
- May 18, 2011
- Messages
- 4,433
- Reaction score
- 1,632
Sorry for that. Our team is looking into the jump in latency. Hopefully it will be resolved soon.
Wolfling
Well-Known Member
I am having several problems since yesterday with connectivity. In some cases my ping speeds go up to 1800ms. I only saw now that Afrihost might be the problem.
Where can I see if I am being shapped?
Where can I see if I am being shapped?
- Joined
- May 18, 2011
- Messages
- 4,433
- Reaction score
- 1,632
The latency issue should be resolved now. You can check on your shaping in the new ClientZone under Connectivity.
SilverCode
Expert Member
Latency seems to have improved, but download speeds are still crawling. ClientZone says I'm not being shaped, but my http download from Amazon S3 server tops out at 60KB/s and averages about 35KB/s. 12 Hours to go to download a 1.8GB file.
Wolfling
Well-Known Member
I dont see any shaping on my account, however I am still experiencing high latency and cannot play any online games. I have logged a fault with the 24-hour support. Ticket ID VMF-968-46803 refers. Still waiting for a reply on it.
FalconZA
Senior Member
Shaping Policy: 18.8% Download/ 6.25% P2P
at 21:37pm????
what gives?
at 21:37pm????
what gives?
Fatality07
Senior Member
mines been like that 24/7 for 10 days now. extremely irate now
Wolfling
Well-Known Member
My connection has now downgraded to ZERO. The modem reports it is connected, but there is no internet.
I am still waiting for any feedback on Ticket ID VMF-968-46803. Your 24-hours a day, 1 hour reply support service is not so 24-hours a day, 1 hours reply...
I am still waiting for any feedback on Ticket ID VMF-968-46803. Your 24-hours a day, 1 hour reply support service is not so 24-hours a day, 1 hours reply...
Hi guys
It looks like latency has jumped up again, just as everything was starting to normalise
Our team are looking at this and should be resolved soon.
It hasn't been the best of weeks (plural)
I feel for you guys, I come from the ISP industry as well (many years ago, however, switched industries at around 2008), and I know these things can be frustrating on a technical level and an absolute PR nightmare at the same time. But since I always play devil's advocate, I'm looking at it from both sides - in this case, from a consumer side as well.Many people made a big leap of faith to move over to Afrihost, since AH offered better service, better client interaction (and that is still top notch, btw - kudos there), and better performance. However, things have been going downhill the last few weeks and for us as consumers, it's incredibly frustrating as it puts us in an impossible situation. We need to decide whether to stay with Afrihost, or move away. I think I speak for most of us when I say we dont want to move to another ISP - I still think AH is one of the best out there. But guys - this cannot go on like this.
We need answers. We need to know WHY the network is under such strain all of a sudden lately, we need to know what you're doing to resolve it. We need to know what the forecast is. We need to know what the network capacity is, how close we are to it (and from the last couple of weeks I assume we're OVER capacity or at least very close to it). We need to know what's going to happen in terms of the network capacity. We... need... answers.
I know you can't provide internal proprietary information, but we can't work with vague answers either. Just like you, we also need to look at information and make decisions based on that. If the answers dont paint a rosy picture, then so be it. If you honestly don't know the answers, then so be it. Just tell us. It doesn't mean we'll leave in droves, but at least we know what's going on. I don't want to pull the "it's our right!" card, but it really IS our right as paying customers to know what's really going on, what's causing it, and what's being done about it. To take myself as an example, I've been tempted since the beginning to move my Telkom line management over to Afrihost as well, but there is no way on earth I can do that while I'm not sure whether Afrihost is the right permanent solution for my Internet provision needs under the current circumstances.
The problem here is twofold: heavy shaping, and bad latency. Personally, I think the latency is a much worse issue than the shaping. Don't get me wrong, I HATE heavy shaping (I'm completely okay with reasonably shaping when it's necessary, but this shaping is HEAVY with a capital F). But "realtime services" are slow as hell most of the time for most of us, and THAT is what irks me endlessly. YouTube, Netflix, gaming, even browsing - these aren't supposed to be affected by shaping, and yet they're suffering bigtime too. I know there's shaping going on, but don't blame the problems on "shaping because the network is under heavy strain". Because firstly, it brings me back to my first series of questions - why? why now? And secondly, shaping isn't what's causing lag with realtime services.
Having said all that, your customer interaction and follow-up on an individual level is amazing and pretty unique as far as SA ISP's go. Please do keep it up
Afriman followed up on my other thread with a PM conversation that lead to a specialist giving me a call on Monday to see if they can help. I am impressed and I appreciate that - I really do. But even the specialist couldn't answer my questions as outlined above I'm sorry if this sounds like a harsh dig at Afrihost - I assure you, it's not intended as such. You should've seen my email messages to MWeb (regarding their scripted vague answers and bullshyte policies), compared to this message :twisted: I could paste their responses here, but I think we've had enough hysterical laughter for one day. Besides which, this thread isn't about MWeb, it's about you - and about how we're going to take these issues on as provider + customers, together, and find an equitable way forward.
Last edited:
gotaway
Expert Member
She's been flying again
18.8% Download/ 6.25% P2P
This is what i have been dealing with for weeks now, its been like this whole night.
Just as a matter of interest, what would happen to the Afrihost network if all the uncapped clients you currently have move to large capped accounts and start going crazy on downloads and P2P?
This is what i have been dealing with for weeks now, its been like this whole night.
Just as a matter of interest, what would happen to the Afrihost network if all the uncapped clients you currently have move to large capped accounts and start going crazy on downloads and P2P?
bloublou100
Member
- Joined
- Apr 28, 2012
- Messages
- 19
- Reaction score
- 0
@ aktor You hit the nail on the head. Also awaiting a proper response with regards to, " WHY the network is under such strain " and how they plan on fixing it. Throttling us to death and just saying..Oops we having network strains, is not cutting it. Not for R700 a month.
DarrenFord
Well-Known Member
So last night around 7pm I check and had "no shaping applied" but was not even able to stream a radio station. Explain please?
DarrenFord
Well-Known Member
It hasn't been the best of weeks (plural)
Many people made a big leap of faith to move over to Afrihost, since AH offered better service, better client interaction (and that is still top notch, btw - kudos there), and better performance. However, things have been going downhill the last few weeks and for us as consumers, it's incredibly frustrating as it puts us in an impossible situation. We need to decide whether to stay with Afrihost, or move away. I think I speak for most of us when I say we dont want to move to another ISP - I still think AH is one of the best out there. But guys - this cannot go on like this.
We need answers. We need to know WHY the network is under such strain all of a sudden lately, we need to know what you're doing to resolve it. We need to know what the forecast is. We need to know what the network capacity is, how close we are to it (and from the last couple of weeks I assume we're OVER capacity or at least very close to it). We need to know what's going to happen in terms of the network capacity. We... need... answers.
I know you can't provide internal proprietary information, but we can't work with vague answers either. Just like you, we also need to look at information and make decisions based on that. If the answers dont paint a rosy picture, then so be it. If you honestly don't know the answers, then so be it. Just tell us. It doesn't mean we'll leave in droves, but at least we know what's going on. I don't want to pull the "it's our right!" card, but it really IS our right as paying customers to know what's really going on, what's causing it, and what's being done about it. To take myself as an example, I've been tempted since the beginning to move my Telkom line management over to Afrihost as well, but there is no way on earth I can do that while I'm not sure whether Afrihost is the right permanent solution for my Internet provision needs under the current circumstances.
The problem here is twofold: heavy shaping, and bad latency. Personally, I think the latency is a much worse issue than the shaping. Don't get me wrong, I HATE heavy shaping (I'm completely okay with reasonably shaping when it's necessary, but this shaping is HEAVY with a capital F). But "realtime services" are slow as hell most of the time for most of us, and THAT is what irks me endlessly. YouTube, Netflix, gaming, even browsing - these aren't supposed to be affected by shaping, and yet they're suffering bigtime too. I know there's shaping going on, but don't blame the problems on "shaping because the network is under heavy strain". Because firstly, it brings me back to my first series of questions - why? why now? And secondly, shaping isn't what's causing lag with realtime services.
Having said all that, your customer interaction and follow-up on an individual level is amazing and pretty unique as far as SA ISP's go. Please do keep it up
I'm sorry if this sounds like a harsh dig at Afrihost - I assure you, it's not intended as such. You should've seen my email messages to MWeb (regarding their scripted vague answers and bullshyte policies), compared to this message :twisted: I could paste their responses here, but I think we've had enough hysterical laughter for one day. Besides which, this thread isn't about MWeb, it's about you - and about how we're going to take these issues on as provider + customers, together, and find an equitable way forward.
Well said, I think it's the same thing everyone is thinking!
- Status