Afrihost Business Uncapped Feedback

hammell · Apr 10, 2014

Terrible line today:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=334 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=372 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=449 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=377 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=181 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=212 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=332 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=425 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.9.6 153 ms
Request timed out *
41.181.53.2 138 ms
3 196.44.18.2 55 ms
196.30.1.3 35 ms
196.44.31.6 129 ms
4 196.44.31.6 182 ms
196.31.220.2 38 ms
196.30.1.3 335 ms
5 196.30.42.1 150 ms
197.242.144.1 38 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.9.6 45 ms 11 ms
Request timed out *
3 41.181.53.1 307 ms 247 ms
Request timed out *
4 196.44.18.2 30 ms
Request timed out *
72.14.194.7 223 ms
5 41.181.139.1 151 ms
Request timed out * *
6 Request timed out * * *
7 Request timed out * *
8 Request timed out * *
9 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 74.125.233.50
Name: www.google.com
Address: 74.125.233.52
Name: www.google.com
Address: 74.125.233.48
Name: www.google.com
Address: 74.125.233.51
Name: www.google.com
Address: 74.125.233.49

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

AfriMan · Apr 10, 2014

NAG - Wesley said:
Has that not gone through yet or is there a time later today when the switch-on will happen?

My 2MB Line as it is now, for what it's worth.

Not bad, let's see how it all holds up now.

Edit: HTTP downloads also top out at over 200KB/s as expected.

Looks good - but the IPC hasn't been upgraded just yet. I think demand just hasn't peaked for the day. But let's hope the speeds stay constant anyway

AfriMan · Apr 10, 2014

skoenman said:
Cool HOpe everything works...out today...

Let's all hold thumbs - think this will help more than a few people get a better internet experience.

cortexenslaver · Apr 10, 2014

AfriMan said:
Sorry to hear that. We do see mild packet loss when there are periods of high contention, which is why we need to shape as aggressively on Uncapped accounts to try to control contention.

So, is this FINALLY an admission that AH IS actually shaping even Business Uncapped?
So much for, "we don't shape Business at all"....

PurSpyk!! · Apr 10, 2014

Do we have to do anything on our side once the capacity has been increased, reboot routes etc.

savage · Apr 10, 2014

cortexenslaver said:
So, is this FINALLY an admission that AH IS actually shaping even Business Uncapped?
So much for, "we don't shape Business at all"....

AfriMan · Apr 10, 2014

PurSpyk!! said:
Do we have to do anything on our side once the capacity has been increased, reboot routes etc.

You shouldn't need to do anything usually - but it can't hurt to reboot if, for example, you're not connecting again (the IPC may go down briefly when they reboot the hardware).

But generally things should just kick in by themselves.

AfriMan · Apr 10, 2014

hammell said:
Terrible line today:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=334 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=372 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=449 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=377 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=181 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=212 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=332 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=425 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.9.6 153 ms
Request timed out *
41.181.53.2 138 ms
3 196.44.18.2 55 ms
196.30.1.3 35 ms
196.44.31.6 129 ms
4 196.44.31.6 182 ms
196.31.220.2 38 ms
196.30.1.3 335 ms
5 196.30.42.1 150 ms
197.242.144.1 38 ms

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.9.6 45 ms 11 ms
Request timed out *
3 41.181.53.1 307 ms 247 ms
Request timed out *
4 196.44.18.2 30 ms
Request timed out *
72.14.194.7 223 ms
5 41.181.139.1 151 ms
Request timed out * *
6 Request timed out * * *
7 Request timed out * *
8 Request timed out * *
9 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 74.125.233.50
Name: www.google.com
Address: 74.125.233.52
Name: www.google.com
Address: 74.125.233.48
Name: www.google.com
Address: 74.125.233.51
Name: www.google.com
Address: 74.125.233.49

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Your second hop latency is pretty high - unusually so. However, if you're in the South where contention is high at times, that could also play a part. But it could be that your exchange is congested or there is a fault on your line.

Do you get the same results if you connect to another network - like guest@telkoadsl (password guest)?

hammell · Apr 10, 2014

The problem isn't with my line - please see tests performed below with Openweb account which on speedtest.net gave me 11ms on Openweb versus 400ms on Afrihost:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=301 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=62 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=330 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=383 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=31 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=480 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=180 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=199 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=444 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=234 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 196.210.201.1 115 ms 9 ms
Request timed out *
3 196.38.72.1 15 ms 12 ms
Request timed out *
4 196.35.115.1 12 ms 11 ms
Request timed out *
5 168.209.6.1 192 ms 12 ms
6 168.209.2.1 27 ms 12 ms
7 41.208.29.2 13 ms 27 ms
8 196.44.0.7 12 ms 12 ms
9 196.44.31.6 32 ms
196.44.31.9 32 ms
10 196.44.31.9 146 ms
196.30.1.3 31 ms
11 196.30.1.3 101 ms
Request timed out *
12 196.31.220.2 37 ms
Request timed out *
13 196.31.63.2 35 ms
Request timed out *
14 196.30.42.1 33 ms
Request timed out *
15 197.242.144.1 32 ms
Request timed out *
16 Request timed out *
17 Request timed out *
18 Request timed out *

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms
2 Request timed out *
168.209.100.1 411 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
7 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 196.23.168.176
Name: www.google.com
Address: 196.23.168.152
Name: www.google.com
Address: 196.23.168.177
Name: www.google.com
Address: 196.23.168.159
Name: www.google.com
Address: 196.23.168.187
Name: www.google.com
Address: 196.23.168.185
Name: www.google.com
Address: 196.23.168.144
Name: www.google.com
Address: 196.23.168.170
Name: www.google.com
Address: 196.23.168.165
Name: www.google.com
Address: 196.23.168.154
Name: www.google.com
Address: 196.23.168.163
Name: www.google.com
Address: 196.23.168.155
Name: www.google.com
Address: 196.23.168.181
Name: www.google.com
Address: 196.23.168.174
Name: www.google.com
Address: 196.23.168.148
Name: www.google.com
Address: 196.23.168.166

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

AfriMan · Apr 10, 2014

hammell said:
The problem isn't with my line - please see tests performed below with Openweb account which on speedtest.net gave me 11ms on Openweb versus 400ms on Afrihost:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=54 time=301 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=54 time=62 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=54 time=330 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=54 time=383 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=54 time=31 ms

ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=480 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=180 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=199 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=444 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=234 ms

Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 196.210.201.1 115 ms 9 ms
Request timed out *
3 196.38.72.1 15 ms 12 ms
Request timed out *
4 196.35.115.1 12 ms 11 ms
Request timed out *
5 168.209.6.1 192 ms 12 ms
6 168.209.2.1 27 ms 12 ms
7 41.208.29.2 13 ms 27 ms
8 196.44.0.7 12 ms 12 ms
9 196.44.31.6 32 ms
196.44.31.9 32 ms
10 196.44.31.9 146 ms
196.30.1.3 31 ms
11 196.30.1.3 101 ms
Request timed out *
12 196.31.220.2 37 ms
Request timed out *
13 196.31.63.2 35 ms
Request timed out *
14 196.30.42.1 33 ms
Request timed out *
15 197.242.144.1 32 ms
Request timed out *
16 Request timed out *
17 Request timed out *
18 Request timed out *

traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms
2 Request timed out *
168.209.100.1 411 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
7 Request timed out *

DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102

nslookup www.google.com

Name: www.google.com
Address: 196.23.168.176
Name: www.google.com
Address: 196.23.168.152
Name: www.google.com
Address: 196.23.168.177
Name: www.google.com
Address: 196.23.168.159
Name: www.google.com
Address: 196.23.168.187
Name: www.google.com
Address: 196.23.168.185
Name: www.google.com
Address: 196.23.168.144
Name: www.google.com
Address: 196.23.168.170
Name: www.google.com
Address: 196.23.168.165
Name: www.google.com
Address: 196.23.168.154
Name: www.google.com
Address: 196.23.168.163
Name: www.google.com
Address: 196.23.168.155
Name: www.google.com
Address: 196.23.168.181
Name: www.google.com
Address: 196.23.168.174
Name: www.google.com
Address: 196.23.168.148
Name: www.google.com
Address: 196.23.168.166

nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN

Are these new test results from the alternative network - cos I'm still seeing high latency on the second hop still and intermittent high pings

Gatecrasher · Apr 10, 2014

AfriMan said:
Are these new test results from the alternative network - cos I'm still seeing high latency on the second hop still and intermittent high pings

That tracert is on the IS network. Which answers your question.

xera · Apr 10, 2014

http://www.speedtest.net/result/3429812898.png

4Mbps line, 3.47Mbps down, 0.42Mbps up, 21ms ping

AfriMan · Apr 10, 2014

xera said:
http://www.speedtest.net/result/3429812898.png

4Mbps line, 3.47Mbps down, 0.42Mbps up, 21ms ping

Not too shabby

hammell · Apr 10, 2014

OK seriously now:

http://www.speedtest.net/my-result/3429910349

6mbps line, 1.86 down 0.14 up and 271ms

This is really not good enough...

hammell · Apr 10, 2014

And:

ping -t www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=245ms TTL=58
Reply from 197.242.144.102: bytes=32 time=202ms TTL=58
Reply from 197.242.144.102: bytes=32 time=85ms TTL=58
Reply from 197.242.144.102: bytes=32 time=318ms TTL=58
Reply from 197.242.144.102: bytes=32 time=376ms TTL=58
Reply from 197.242.144.102: bytes=32 time=588ms TTL=58
Reply from 197.242.144.102: bytes=32 time=218ms TTL=58
Reply from 197.242.144.102: bytes=32 time=165ms TTL=58
Reply from 197.242.144.102: bytes=32 time=119ms TTL=58
Reply from 197.242.144.102: bytes=32 time=330ms TTL=58
Reply from 197.242.144.102: bytes=32 time=301ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=215ms TTL=58
Reply from 197.242.144.102: bytes=32 time=555ms TTL=58
Reply from 197.242.144.102: bytes=32 time=446ms TTL=58
Reply from 197.242.144.102: bytes=32 time=150ms TTL=58
Reply from 197.242.144.102: bytes=32 time=456ms TTL=58
Reply from 197.242.144.102: bytes=32 time=531ms TTL=58
Reply from 197.242.144.102: bytes=32 time=273ms TTL=58

Ping statistics for 197.242.144.102:
Packets: Sent = 19, Received = 18, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 588ms, Average = 309ms

Zertop · Apr 10, 2014

hammell said:
And:

ping -t www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=245ms TTL=58
Reply from 197.242.144.102: bytes=32 time=202ms TTL=58
Reply from 197.242.144.102: bytes=32 time=85ms TTL=58
Reply from 197.242.144.102: bytes=32 time=318ms TTL=58
Reply from 197.242.144.102: bytes=32 time=376ms TTL=58
Reply from 197.242.144.102: bytes=32 time=588ms TTL=58
Reply from 197.242.144.102: bytes=32 time=218ms TTL=58
Reply from 197.242.144.102: bytes=32 time=165ms TTL=58
Reply from 197.242.144.102: bytes=32 time=119ms TTL=58
Reply from 197.242.144.102: bytes=32 time=330ms TTL=58
Reply from 197.242.144.102: bytes=32 time=301ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=215ms TTL=58
Reply from 197.242.144.102: bytes=32 time=555ms TTL=58
Reply from 197.242.144.102: bytes=32 time=446ms TTL=58
Reply from 197.242.144.102: bytes=32 time=150ms TTL=58
Reply from 197.242.144.102: bytes=32 time=456ms TTL=58
Reply from 197.242.144.102: bytes=32 time=531ms TTL=58
Reply from 197.242.144.102: bytes=32 time=273ms TTL=58

Ping statistics for 197.242.144.102:
Packets: Sent = 19, Received = 18, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 588ms, Average = 309ms

-_-

Please run one of the tools in my sig. You sure it's not a line issue? What does it look like on other ISP accounts?

Z

hammell · Apr 10, 2014

Zertop's "Is it my Line" Results
Basic Report:

Your average ping was 463ms
Your maximum ping was 724ms

Looking at your average ping, there is definitely something wrong with your line-( Please post the results (at the end of the program) into the forum for advice

Detailed Report

Code:

Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) 

Pinging 105.236.9.65 with 32 bytes of data:
Reply from 105.236.9.65: bytes=32 time=357ms TTL=254
Reply from 105.236.9.65: bytes=32 time=259ms TTL=254
Reply from 105.236.9.65: bytes=32 time=384ms TTL=254
Reply from 105.236.9.65: bytes=32 time=505ms TTL=254
Reply from 105.236.9.65: bytes=32 time=515ms TTL=254
Reply from 105.236.9.65: bytes=32 time=480ms TTL=254
Reply from 105.236.9.65: bytes=32 time=348ms TTL=254
Reply from 105.236.9.65: bytes=32 time=615ms TTL=254
Reply from 105.236.9.65: bytes=32 time=579ms TTL=254
Reply from 105.236.9.65: bytes=32 time=724ms TTL=254
Reply from 105.236.9.65: bytes=32 time=636ms TTL=254
Reply from 105.236.9.65: bytes=32 time=469ms TTL=254
Reply from 105.236.9.65: bytes=32 time=245ms TTL=254
Reply from 105.236.9.65: bytes=32 time=332ms TTL=254
Reply from 105.236.9.65: bytes=32 time=434ms TTL=254
Reply from 105.236.9.65: bytes=32 time=619ms TTL=254
Reply from 105.236.9.65: bytes=32 time=555ms TTL=254
Reply from 105.236.9.65: bytes=32 time=575ms TTL=254
Reply from 105.236.9.65: bytes=32 time=577ms TTL=254
Reply from 105.236.9.65: bytes=32 time=532ms TTL=254
Reply from 105.236.9.65: bytes=32 time=494ms TTL=254
Reply from 105.236.9.65: bytes=32 time=281ms TTL=254
Reply from 105.236.9.65: bytes=32 time=402ms TTL=254
Reply from 105.236.9.65: bytes=32 time=428ms TTL=254
Reply from 105.236.9.65: bytes=32 time=577ms TTL=254
Reply from 105.236.9.65: bytes=32 time=404ms TTL=254
Reply from 105.236.9.65: bytes=32 time=401ms TTL=254
Reply from 105.236.9.65: bytes=32 time=540ms TTL=254
Reply from 105.236.9.65: bytes=32 time=429ms TTL=254
Reply from 105.236.9.65: bytes=32 time=211ms TTL=254

Ping statistics for 105.236.9.65:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 211ms, Maximum = 724ms, Average = 463ms
 
2014-04-10 12:24:52,54

hammell · Apr 10, 2014

But when using my Openweb account I get:

ping -t www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=34ms TTL=53
Reply from 197.242.144.102: bytes=32 time=35ms TTL=53
Reply from 197.242.144.102: bytes=32 time=34ms TTL=53
Reply from 197.242.144.102: bytes=32 time=31ms TTL=53
Reply from 197.242.144.102: bytes=32 time=40ms TTL=53
Reply from 197.242.144.102: bytes=32 time=480ms TTL=53
Reply from 197.242.144.102: bytes=32 time=829ms TTL=53
Reply from 197.242.144.102: bytes=32 time=768ms TTL=53
Reply from 197.242.144.102: bytes=32 time=815ms TTL=53
Reply from 197.242.144.102: bytes=32 time=454ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=31ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=46ms TTL=53
Reply from 197.242.144.102: bytes=32 time=45ms TTL=53

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

DJ... · Apr 10, 2014

If that's on your second hop then you're looking at exchange congestion. That's a Telkom issue unfortunately. Time to get on the line and harass them every day for an upgrade at your exchange...

DJ... · Apr 10, 2014

hammell said:
But when using my Openweb account I get:

ping -t www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=34ms TTL=53
Reply from 197.242.144.102: bytes=32 time=35ms TTL=53
Reply from 197.242.144.102: bytes=32 time=34ms TTL=53
Reply from 197.242.144.102: bytes=32 time=31ms TTL=53
Reply from 197.242.144.102: bytes=32 time=40ms TTL=53
Reply from 197.242.144.102: bytes=32 time=480ms TTL=53
Reply from 197.242.144.102: bytes=32 time=829ms TTL=53
Reply from 197.242.144.102: bytes=32 time=768ms TTL=53
Reply from 197.242.144.102: bytes=32 time=815ms TTL=53
Reply from 197.242.144.102: bytes=32 time=454ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=31ms TTL=53
Reply from 197.242.144.102: bytes=32 time=32ms TTL=53
Reply from 197.242.144.102: bytes=32 time=46ms TTL=53
Reply from 197.242.144.102: bytes=32 time=45ms TTL=53

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

Run the same tests on both accounts immediately after each other. Exchange congestion is a weird kind of evil - there one second, gone the next...

Join the MyBroadband community

Get started

Afrihost Business Uncapped Feedback

Senior Member

Afrihost Representative

Afrihost Representative

Senior Member

Expert Member

Expert Member

Afrihost Representative

Afrihost Representative

Senior Member

Afrihost Representative

Executive Member

Expert Member

Afrihost Representative

Senior Member

Senior Member

Expert Member

Senior Member

Senior Member

Banned

Banned