Afrihost Uncapped ADSL Feedback (Pt2)

[vicv]

View attachment 94057

That's pretty damn good for a ping to the US and A.

 

[Martian]

What service do you use to hide your IP?

Using unotelly.

 

[Shamus]

Hi, got a strange problem which hopefully someone can help with. My download speeds, pings etc are great but browsing is sometimes slow. When I click on a link or type in an address it sometimes just sits for ages saying connecting but nothing comes up. Some sites just refuse to connect and eventually time out. Tried re-booting router, switching to capped account but no different. Phone connected through wifi to AH is the same but as soon as I connect through 3g all is well. I suspect it must be some sort of dns problem - had a look at the router and it shows primary dns as 196.7.7.7 and secondary as 196.7.8.9 - are these correct for Afrihost? These settings are obtained from AH automatically and there doesn't seem to be any option of entering them manually.

 

[Pakka]

I remember in Nov when I left Afrihost they had the capacity issues with no ETA. Has the capacity been implemented since, or at least an ETA?

 

[wingnut771]

I remember in Nov when I left Afrihost they had the capacity issues with no ETA. Has the capacity been implemented since, or at least an ETA?

Not yet, end of Feb would be a safe bet i would say

 

[Zertop]

Hi, got a strange problem which hopefully someone can help with. My download speeds, pings etc are great but browsing is sometimes slow. When I click on a link or type in an address it sometimes just sits for ages saying connecting but nothing comes up. Some sites just refuse to connect and eventually time out. Tried re-booting router, switching to capped account but no different. Phone connected through wifi to AH is the same but as soon as I connect through 3g all is well. I suspect it must be some sort of dns problem - had a look at the router and it shows primary dns as 196.7.7.7 and secondary as 196.7.8.9 - are these correct for Afrihost? These settings are obtained from AH automatically and there doesn't seem to be any option of entering them manually.

Could be the DNS... Could you change your DNS to google's servers, 8.8.8.8 and 8.8.4.4

If that doesn't help, it could be a packet loss issue. Please would you run the new Afrihost support tool (link a few posts back)

 

[Zertop]

Not yet, end of Feb would be a safe bet i would say

Most probably during the feb period

 

[Shamus]

Could be the DNS... Could you change your DNS to google's servers, 8.8.8.8 and 8.8.4.4

If that doesn't help, it could be a packet loss issue. Please would you run the new Afrihost support tool (link a few posts back)

Thanks for the reply. I have changed the dns as you suggested and will run with that to see how it goes but first impressions are that it is much the same.
Ran the Afrihost tool, results:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=58 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=57 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=174 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=101 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=207 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=207 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=208 ms



Trace Test:

traceroute -n 197.242.144.102

1 10.0.0.2 1 ms 1 ms
2 105.236.7.6 10 ms 13 ms
3 41.181.198.1 39 ms
41.181.51.1 41 ms
4 196.44.18.2 39 ms
41.181.198.1 118 ms
5 196.44.31.1 42 ms
196.44.18.2 40 ms
6 196.44.31.6 218 ms 61 ms
7 196.44.31.9 58 ms 58 ms
8 196.31.220.2 61 ms
196.31.220.1 61 ms
9 196.31.63.1 59 ms 124 ms
10 197.242.144.1 57 ms 58 ms


traceroute -n 8.8.8.8

1 10.0.0.2 1 ms 1 ms
2 105.236.7.6 17 ms 9 ms
3 41.181.198.1 38 ms
41.181.53.1 40 ms
4 196.44.31.1 204 ms
41.181.198.1 38 ms
5 196.44.31.6 57 ms
196.44.18.2 39 ms
6 41.181.139.1 57 ms
196.44.31.1 81 ms
7 72.14.194.7 56 ms
41.181.139.1 59 ms
8 Request timed out *
72.14.194.7 57 ms
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: 173.194.41.179
Name: www.google.com
Address: 173.194.41.177
Name: www.google.com
Address: 173.194.41.180
Name: www.google.com
Address: 173.194.41.178
Name: www.google.com
Address: 173.194.41.176


nslookup thishouldfail.afrihost.com

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


Don't mean a lot to me but your thoughts would be most welcome.

 

[Zertop]

Thanks for the reply. I have changed the dns as you suggested and will run with that to see how it goes but first impressions are that it is much the same.
Ran the Afrihost tool, results:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=58 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=57 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=174 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=59 time=101 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=207 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=207 ms
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=208 ms



Trace Test:

traceroute -n 197.242.144.102

110.0.0.2 1 ms 1 ms
2105.236.7.6 10 ms 13 ms
341.181.198.1 39 ms
41.181.51.1 41 ms
4196.44.18.2 39 ms
41.181.198.1 118 ms
5196.44.31.1 42 ms
196.44.18.2 40 ms
6196.44.31.6 218 ms 61 ms
7196.44.31.9 58 ms 58 ms
8196.31.220.2 61 ms
196.31.220.1 61 ms
9196.31.63.1 59 ms 124 ms
10197.242.144.1 57 ms 58 ms


traceroute -n 8.8.8.8

110.0.0.2 1 ms 1 ms
2105.236.7.6 17 ms 9 ms
341.181.198.1 38 ms
41.181.53.1 40 ms
4196.44.31.1 204 ms
41.181.198.1 38 ms
5196.44.31.6 57 ms
196.44.18.2 39 ms
641.181.139.1 57 ms
196.44.31.1 81 ms
772.14.194.7 56 ms
41.181.139.1 59 ms
8Request timed out *
72.14.194.7 57 ms
9Request 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: 173.194.41.179
Name:www.google.com
Address: 173.194.41.177
Name:www.google.com
Address: 173.194.41.180
Name:www.google.com
Address: 173.194.41.178
Name:www.google.com
Address: 173.194.41.176


nslookup thishouldfail.afrihost.com

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


Don't mean a lot to me but your thoughts would be most welcome.

Hey Shamus,

It seems that there may be some packet loss on your line :/ From these results, I can't seem to find the source, but as you can see where it says request timed out - that means a loss of connection (or packet loss) on the network. From the randomly high pings on certain hops, I could only guess there is some form of intermittent connection issue. Could you please contact live chat and they'll help you out

Z

 

[wingnut771]

Hey Shamus,

It seems that there may be some packet loss on your line :/ From these results, I can't seem to find the source, but as you can see where it says request timed out - that means a loss of connection (or packet loss) on the network. From the randomly high pings on certain hops, I could only guess there is some form of intermittent connection issue. Could you please contact live chat and they'll help you out

Z

I have zero issues but when I use this tool I get this:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=22 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=22 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=22 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=55 time=22 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=21 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=199 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=198 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms
2 196.210.157.1 9 ms 9 ms
3 196.38.73.2 21 ms 20 ms
4 168.209.1.1 21 ms
196.38.73.9 21 ms
5 196.26.0.1 21 ms
168.209.1.1 20 ms
6 41.208.29.1 21 ms
196.26.0.1 20 ms
7 196.44.0.2 23 ms
41.208.29.1 25 ms
8 196.44.31.9 21 ms 21 ms
9 196.30.1.3 22 ms 21 ms
10 196.31.220.2 22 ms 22 ms
11 196.31.63.1 22 ms 23 ms
12 197.242.144.1 22 ms 22 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms
2 196.210.157.1 9 ms
3 196.38.73.2 21 ms
4 196.38.73.9 21 ms
5 168.209.1.1 20 ms
6 196.26.0.1 42 ms
7 74.125.49.6 20 ms
8 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.52
Name: www.google.com
Address: 74.125.233.49
Name: www.google.com
Address: 74.125.233.48
Name: www.google.com
Address: 74.125.233.50
Name: www.google.com
Address: 74.125.233.51


nslookup thishouldfail.afrihost.com

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


I also get timeouts for no reason. If I manually do these tests, there is nothing wrong, so I think this tool has bugs or something and isn't really any help in diagnosing at the moment. Good idea tho.

Manual ping test:

C:\Users\Lindsay>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=200ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44
Reply from 8.8.8.8: bytes=32 time=199ms TTL=44

Ping statistics for 8.8.8.8:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 200ms, Average = 199ms
Control-C
^C

It's the same with the tracerts.

 

[Shamus]

Tried a tracert without using the AH tool and got:
Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 10 ms 10 ms 105.236.7.65
3 40 ms 39 ms 39 ms 41.181.53.150
4 40 ms 41 ms 42 ms 41.181.198.188
5 40 ms 39 ms 40 ms 196.44.18.2
6 40 ms 43 ms 40 ms 196.44.31.134
7 85 ms 57 ms 58 ms 196.44.31.69
8 57 ms 57 ms 57 ms 41.181.139.109
9 59 ms 58 ms 57 ms 72.14.194.74
10 203 ms 201 ms 202 ms 66.249.95.8
11 204 ms 202 ms 202 ms 209.85.253.196
12 207 ms 208 ms 208 ms 66.249.95.173
13 208 ms 207 ms 216 ms 209.85.251.231
14 * * * Request timed out.
15 208 ms 207 ms 209 ms 8.8.8.8

Still timeouts there but not sure if they are significant as they always occur at the same point.

Also, most of my downloads are using IDM which gives speeds of 240 KB/s on a 2Mb line. Just tried a download from the same source without IDM and only getting 140 KB/s so definitely a problem there. Also noticed that youtube is buffering a lot on 360 so also indicating a problem somewhere. Will contact AH support to see if they can sort it out.

 

[wingnut771]

Tried a tracert without using the AH tool and got:
Tracing route to 8.8.8.8 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.2
2 9 ms 10 ms 10 ms 105.236.7.65
3 40 ms 39 ms 39 ms 41.181.53.150
4 40 ms 41 ms 42 ms 41.181.198.188
5 40 ms 39 ms 40 ms 196.44.18.2
6 40 ms 43 ms 40 ms 196.44.31.134
7 85 ms 57 ms 58 ms 196.44.31.69
8 57 ms 57 ms 57 ms 41.181.139.109
9 59 ms 58 ms 57 ms 72.14.194.74
10 203 ms 201 ms 202 ms 66.249.95.8
11 204 ms 202 ms 202 ms 209.85.253.196
12 207 ms 208 ms 208 ms 66.249.95.173
13 208 ms 207 ms 216 ms 209.85.251.231
14 * * * Request timed out.
15 208 ms 207 ms 209 ms 8.8.8.8

Still timeouts there but not sure if they are significant as they always occur at the same point.

Also, most of my downloads are using IDM which gives speeds of 240 KB/s on a 2Mb line. Just tried a download from the same source without IDM and only getting 140 KB/s so definitely a problem there. Also noticed that youtube is buffering a lot on 360 so also indicating a problem somewhere. Will contact AH support to see if they can sort it out.

This is nothing to be concerned with, it isn't a timeout, but rather a firewall or something blocking it, it still gets to 8.8.8.8. Each hop has 3 pings, if there were timeouts, some of those pings would be missing, not all three on only one line (normally).

Why YT is buffering when you can download at 240 I don't know especially when YT is real time and is not supposed to be affected by shaping.

 

[Shamus]

Why YT is buffering when you can download at 240 I don't know especially when YT is real time and is not supposed to be affected by shaping.

I only download at 240 if I use IDM which is a multithreaded downloader but if I download without using it then I only download at 140. Not sure how YT works but if it is also running at 140 then that is probably why it is buffering.

 

[wingnut771]

I only download at 240 if I use IDM which is a multithreaded downloader but if I download without using it then I only download at 140. Not sure how YT works but if it is also running at 140 then that is probably why it is buffering.

Can you test with testmy.net as I think this is single threaded and download a 25MB file. I've noticed some ISP's limiting single thread downloads, which is why we need things like IDM.

Also, what region are you in? North and south are worse off than east, with north being the worst from what I hear until they get their planned upgraded capacity.

 

[Shamus]

Can you test with testmy.net as I think this is single threaded and download a 25MB file. I've noticed some ISP's limiting single thread downloads, which is why we need things like IDM.

Also, what region are you in? North and south are worse off than east, with north being the worst from what I hear until they get their planned upgraded capacity.

testmy.net gives me a download speed of 131KB/s on a 25Mb file which is pretty much what I get on downloads unless I use IDM.
I am in the Eastern Cape but it is not a shaping thing as I get exactly the same results with my capped account. Also, I this problem has only started in the last week or so, before that all was ok.
Time to get AH involved I think.

 

[AfriMan]

I wish telkom had the same customer service as you guys man would it make life easier...

We really try to do our best for each and every client we deal with. We hope that's what set's us apart from the rest

 

[AfriMan]

Telkom surprised me the other day.. I dropped a pm to TelkomZa 2 or three days ago and they got back to me within half a hour. Miracles do still happen from time to time..

But nothing beat Afrihost's client service!

We'll have to watch our backs. Don't want to fall to number 2 in the rankings

 

[AfriMan]

Business accounts are incredibly awesome. I'm speaking from personal experience. Will never go back to a Home package as long as this kind of performance keeps up.

Glad to hear it's working out for you

 

[AfriMan]

Hi, got a strange problem which hopefully someone can help with. My download speeds, pings etc are great but browsing is sometimes slow. When I click on a link or type in an address it sometimes just sits for ages saying connecting but nothing comes up. Some sites just refuse to connect and eventually time out. Tried re-booting router, switching to capped account but no different. Phone connected through wifi to AH is the same but as soon as I connect through 3g all is well. I suspect it must be some sort of dns problem - had a look at the router and it shows primary dns as 196.7.7.7 and secondary as 196.7.8.9 - are these correct for Afrihost? These settings are obtained from AH automatically and there doesn't seem to be any option of entering them manually.

As others have guessed, it also looks packet loss intermittently affecting your line.

I see you have posted some results, but I'd recommend running MTR (continous) tests to see if you see intermittent dropped packets and spikes in latency.

 

[AfriMan]

I remember in Nov when I left Afrihost they had the capacity issues with no ETA. Has the capacity been implemented since, or at least an ETA?

Not as yet. I don't have a confirmed ETA at the present moment - I'll post it up as soon as I have that info