South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
try running test from the command line, I've lost faith in the AH Network Tester as it gives totally different results and grinds away with traceroutes compared to results from the command line
They are just milking the higher prices as long as they can
Still request timed outs and general slow
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 4 ms 1 ms 2 ms XXXX
2 59 ms 56 ms 46 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 24 ms 31 ms * ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178
.5]
4 59 ms 148 ms 47 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 38 ms 39 ms 47 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
6 46 ms 48 ms 43 ms 41.181.139.109
7 56 ms 62 ms * 72.14.194.74
8 201 ms 221 ms 222 ms 66.249.95.8
9 224 ms 227 ms 189 ms 209.85.253.196
10 * 239 ms 208 ms 66.249.95.173
11 224 ms 202 ms 229 ms 209.85.251.231
12 * * * Request timed out.
13 214 ms 228 ms 239 ms google-public-dns-a.google.com [8.8.8.8]
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=214ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=206ms TTL=42
Reply from 8.8.8.8: bytes=32 time=202ms TTL=42
Reply from 8.8.8.8: bytes=32 time=206ms TTL=42
Reply from 8.8.8.8: bytes=32 time=221ms TTL=42
Reply from 8.8.8.8: bytes=32 time=222ms TTL=42
Reply from 8.8.8.8: bytes=32 time=221ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=224ms TTL=42
Reply from 8.8.8.8: bytes=32 time=197ms TTL=42
Reply from 8.8.8.8: bytes=32 time=212ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=211ms TTL=42
Reply from 8.8.8.8: bytes=32 time=224ms TTL=42
Reply from 8.8.8.8: bytes=32 time=232ms TTL=42
Reply from 8.8.8.8: bytes=32 time=228ms TTL=42
Reply from 8.8.8.8: bytes=32 time=213ms TTL=42
Reply from 8.8.8.8: bytes=32 time=192ms TTL=42
Reply from 8.8.8.8: bytes=32 time=212ms TTL=42
Reply from 8.8.8.8: bytes=32 time=233ms TTL=42
Ping statistics for 8.8.8.8:
Packets: Sent = 21, Received = 18, Lost = 3 (14% l
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 233ms, Average = 215ms
Still request timed outs and general slow
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 4 ms 1 ms 2 ms XXXX
2 59 ms 56 ms 46 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1
.65]
3 24 ms 31 ms * ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178
.5]
4 59 ms 148 ms 47 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 38 ms 39 ms 47 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
6 46 ms 48 ms 43 ms 41.181.139.109
7 56 ms 62 ms * 72.14.194.74
8 201 ms 221 ms 222 ms 66.249.95.8
9 224 ms 227 ms 189 ms 209.85.253.196
10 * 239 ms 208 ms 66.249.95.173
11 224 ms 202 ms 229 ms 209.85.251.231
12 * * * Request timed out.
13 214 ms 228 ms 239 ms google-public-dns-a.google.com [8.8.8.8]
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=214ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=206ms TTL=42
Reply from 8.8.8.8: bytes=32 time=202ms TTL=42
Reply from 8.8.8.8: bytes=32 time=206ms TTL=42
Reply from 8.8.8.8: bytes=32 time=221ms TTL=42
Reply from 8.8.8.8: bytes=32 time=222ms TTL=42
Reply from 8.8.8.8: bytes=32 time=221ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=224ms TTL=42
Reply from 8.8.8.8: bytes=32 time=197ms TTL=42
Reply from 8.8.8.8: bytes=32 time=212ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=211ms TTL=42
Reply from 8.8.8.8: bytes=32 time=224ms TTL=42
Reply from 8.8.8.8: bytes=32 time=232ms TTL=42
Reply from 8.8.8.8: bytes=32 time=228ms TTL=42
Reply from 8.8.8.8: bytes=32 time=213ms TTL=42
Reply from 8.8.8.8: bytes=32 time=192ms TTL=42
Reply from 8.8.8.8: bytes=32 time=212ms TTL=42
Reply from 8.8.8.8: bytes=32 time=233ms TTL=42
Ping statistics for 8.8.8.8:
Packets: Sent = 21, Received = 18, Lost = 3 (14% l
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 233ms, Average = 215ms
+1Satrting to think that working for AH support may be a good career move ... seems to be a part time job.
Support is half the rason I gave up on my last ISP. (Or rather lack of QUALITY support).
This is what they send to a friend of mine after query that his 2mbs line keeps reverting to 1024 sync - tried numerous times to resync on the clientzone, and thus ending up in opening a ticket
We manage all of our uncapped adsl accounts on an hour to hour basis depending on the performance of our network at that time.
If the capacity of the network is stretched at that time we will dynamically shape and manage the account to relieve congestion on the network.
These uncapped clients will be chosen based on historical bandwidth usage.The uncapped users with the most amount of bandwidth used will be managed first if there is network congestion.
Capped adsl accounts will not be affected by any shaping or management on the account. The capped accounts will always get whatever your line speed is able to give you.
We evaluate our network capacity on a hour to hour basis and if network congestion is eased we will un-manage the uncapped accounts until such time as capacity is stretched.
It is our goal to ensure the best possible experience for both the biggest and the smallest of our clients given the parameters we have and as such we reserve the right to manage the uncapped adsl accounts as we deem necessary to ensure optimal performance across our network for all of our clients.
I hope information is useful
What a load of rubbish!
+1
I can suck up the whole "why you shape" story - fine. But then, jump at the opportunity when I agree to pay more for uncapped to solve YOUR problem.
In theory, I can change my account at will, but your pricing and advertising dont add up. The only reply I have from support does not in ANY WAY answer my query. Your guy answering me obviously did not read my query and was less than helpful. If less time is spent generating excuses and more time is spent helping customers, things will go alot better for both of us.
Help me to help you, rather than to offer up lame excuses as to why I have bought a 1600cc limited to 10Km/h!!
If you either cant or wont assist me to upgrade to your "unshaped" business account then you expect me to post snotty comments!
And the longer you make me wait for an answer, the more posts I will make .......
Hey Afriguy I just want to bring up an issue I've discussed with Afriman in the past.
Possible reasons were given by Afriman why shaping would affect the quality of the Netflix stream but I can't for the life of me remember what was said and going back in the thread will take ages.
What reasons can there be for the reduction in quality? I know shaping is not supposed to have any affect on it but it most definitely has, well for me and some other people at least. I am on a 4mb line but struggling to keep a consistent 240p stream going, nevermind anything that resembles HD.
Is there any tests that I can do that can be analysed by you guys to seek a solution to this?
AfriMan, quick question regarding the shaping.
If I'm on a 4mb line and the ClientZone reports 50% Download \ 25% P2P, does that mean I will achieve 2mb on HTTP downloads and 1mb on P2P simultaneously? (Assuming I have a HTTP and P2P download running at the same time).
Shaping eases up at around 23:00, by which time I'm getting ready for bed. I would like to use the internet at least when I get home. Realtime services are great, but when you're trying to download new graphics drivers on a 4mbps line at 60kb/s it's not cool anymore. Like I say I understand that P2P has to be shaped, but don't quite fathom the need for http download shaping, as that is a core part of receiving files over the internet (updating your phone, anti-virus, everyday applications etc.)
Thats interesting then. Is shaping now working how much you download now? I have had a heavy start to March, so I'm guessing that it might it. I will have a look at my shaping after 7 tonight to see if it has eased up.
I think what they're saying is that the promotion then went ahead, despite of the shaping.
You can't really blame people for being annoyed. Massive shaping issues due to capacity, then all the extra unshaped bandwidth being handed out despite of it. Of course people are going to be up in arms.
When will bundle rates be reduced?
Slow as sin - 2mbs uncapped
http://www.speedtest.net/my-result/3367254724
Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=537 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=62 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=42 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=38 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=57 time=25 ms
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=42 time=199 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Trace Test:
traceroute -n 197.242.144.102
1 XXXX 1 ms 12 ms
2 105.236.1.6 66 ms
41.181.178.1 24 ms
3 41.181.178.1 47 ms
41.181.165.1 35 ms
4 196.31.180.4 67 ms 27 ms
5 196.44.0.2 72 ms 45 ms
6 196.44.31.9 27 ms 29 ms
7 196.31.220.2 63 ms
196.30.1.5 21 ms
8 196.31.63.2 393 ms
196.31.220.2 78 ms
9 197.242.144.1 43 ms
196.31.63.2 27 ms
10 196.30.42.1 42 ms
11 197.242.144.1 23 ms
traceroute -n 8.8.8.8
1 XXXX 1 ms
2 105.236.1.6 349 ms
3 41.181.178.5 26 ms
4 196.31.180.4 45 ms
5 41.181.139.1 102 ms
6 72.14.194.7 58 ms
7 Request timed out *
8 Request timed out *
9 Request timed out *
10 Request timed out *
11 Request timed out *
12 Request timed out *
13 Request timed out *
14 Request timed out *
15 Request timed out *
** server can't find thisshouldfail.com: NXDOMAIN
I am trying to change from a 4Mb standard (shaped to death) package, with my line at Telkom to the 4Mb bundled package.
If I use the CP and follow the steps, I port my line over to AH, R244, and then take the business uncapped R697, total, R941.
BUT .... According to this ....View attachment 105076 I should be being milked for R697....
Have PMd Afriperson twice - no response as yet, and have had some advice from support, which was as valuable as a fridge in the Arctic.
That aside - I have been following AH for some time now, and the two things that seem to be loooooooooooooong in the coming was the price reviews and capacity increases. "Soon" could mean anytime in the next decade.
Afripeople - help me to move over to bundled business - if its difficult for you imagine how difficult it is for your customers.
Thank you.