Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Tapatalk won't let me quote. @Ol' Mean Bastid The test app is a little hard to make out for me compared to a normal traceroute, but it looks like you have some congestion at the 2nd hop
 
Ol' Mean Bastid said:
been having hassles today, slow or interrupted downloads

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=9 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=41 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=38 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=60 ms
Request timeout for icmp_seq 5


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=42 time=181 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=42 time=180 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=42 time=182 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=42 time=180 ms


Trace Test:

traceroute -n 197.242.144.102

1192.168.0.1 1 ms 1 ms
241.181.178.4 45 ms
105.236.12.1 11 ms
341.181.165.1 7 ms
41.181.178.4 8 ms
441.181.165.1 12 ms 13 ms
5196.44.0.2 9 ms
41.181.165.1 14 ms
6196.44.31.9 8 ms
196.44.0.2 43 ms
7196.31.220.8 13 ms
196.44.31.9 11 ms
8196.31.220.2 12 ms
196.31.220.8 20 ms
9196.31.63.2 30 ms
196.31.220.2 8 ms
10196.30.42.1 15 ms
196.31.63.2 8 ms
11197.242.144.1 27 ms
196.30.42.1 10 ms
12197.242.144.1 22 ms


traceroute -n 8.8.8.8

1192.168.0.1 1 ms
2105.236.12.1 6 ms
341.181.178.1 8 ms
441.181.165.1 18 ms
541.181.165.1 24 ms
641.181.139.1 9 ms
772.14.194.7 11 ms
8Request timed out *
98.8.8.8 180 ms


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.144
Name:www.google.com
Address: 173.194.41.148
Name:www.google.com
Address: 173.194.41.146
Name:www.google.com
Address: 173.194.41.145
Name:www.google.com
Address: 173.194.41.147


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

See hop 2 on the tracerts - those should be under 15ms, however your go Into the 40s. This indicates a issue between your network and the Afrihost network. You will probably have to report a line fault with Afrihost or Telkom :(
 
Ol' Mean Bastid said:
been having hassles today, slow or interrupted downloads

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=57 time=9 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=57 time=41 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=57 time=38 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=57 time=60 ms
Request timeout for icmp_seq 5


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=42 time=181 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=42 time=180 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=42 time=182 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=42 time=180 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms
2 41.181.178.4 45 ms
105.236.12.1 11 ms
3 41.181.165.1 7 ms
41.181.178.4 8 ms
4 41.181.165.1 12 ms 13 ms
5 196.44.0.2 9 ms
41.181.165.1 14 ms
6 196.44.31.9 8 ms
196.44.0.2 43 ms
7 196.31.220.8 13 ms
196.44.31.9 11 ms
8 196.31.220.2 12 ms
196.31.220.8 20 ms
9 196.31.63.2 30 ms
196.31.220.2 8 ms
10 196.30.42.1 15 ms
196.31.63.2 8 ms
11 197.242.144.1 27 ms
196.30.42.1 10 ms
12 197.242.144.1 22 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms
2 105.236.12.1 6 ms
3 41.181.178.1 8 ms
4 41.181.165.1 18 ms
5 41.181.165.1 24 ms
6 41.181.139.1 9 ms
7 72.14.194.7 11 ms
8 Request timed out *
9 8.8.8.8 180 ms


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.144
Name: www.google.com
Address: 173.194.41.148
Name: www.google.com
Address: 173.194.41.146
Name: www.google.com
Address: 173.194.41.145
Name: www.google.com
Address: 173.194.41.147


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

Your local ping are pretty high. Second hop also looks way too high, should never be more than 30ms - which already pretty horrible. Looking at the intermittent spikes, I would say it's more likely to be on the exchange than on your line :(
 
bugger looks even worse this morning, guess I'll have to call Telkom
 
I can honestly say that my SS steaming is so good, that it is actually boring, so I'm typing this to increase my post count.

Edit:
The streaming has now gone belly up since 10:11.
Constant spinning circle now @ 10:20

Logged out and now struggling to log in to the supersport.com website, so seems to be an issue on their side?
Eventually logged on, but can't get the cricket stream going.
Okay got it going, but took very long.

Running smooth again.
 
Last edited:
AfriMan said:
Let us know what they say. But I'd also recommend running the tests on saix.net with the telkom guest account so you can satisfy yourself that results are same on both networks.
Click to expand...

just did the test using the telkom guest account, you gotta love these results :(

Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


ping 8.8.8.8

Request timeout for icmp_seq 1
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 192.168.1.1 1 ms
2 165.145.102.1 6 ms
3 Request timed out *
4 Request timed out *
5 Request timed out *
6 Request timed out *
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 *
16 Request timed out *
17 Request timed out *
18 Request timed out *
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 Request timed out *
30 Request timed out *


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms
2 Request timed out *
165.145.102.1 6 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
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 * *
16 Request timed out * *
17 Request timed out * *
18 Request timed out * *
19 Request timed out * *
20 Request timed out * *
21 Request timed out * *
22 Request timed out * *
23 Request timed out * *
24 Request timed out * *
25 Request timed out * *
26 Request timed out * *
27 Request timed out * *
28 Request timed out * *
29 Request timed out *
30 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.49
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


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
AfriMan said:
Let us know what they say. But I'd also recommend running the tests on saix.net with the telkom guest account so you can satisfy yourself that results are same on both networks.
Click to expand...

okay, so Telkom recreated the port, they say there doesn't appear to be any problems at the exchange but it still looks like there's problems, so they suggested I log a fault with AH which I have just done
 
Ol' Mean Bastid said:
okay, so Telkom recreated the port, they say there doesn't appear to be any problems at the exchange but it still looks like there's problems, so they suggested I log a fault with AH which I have just done
Click to expand...

Looking at your results above there definitely does seem to be a fault on the exchange :( We'll keep you posted on the fault.
 
RoMark said:
I can honestly say that my SS steaming is so good, that it is actually boring, so I'm typing this to increase my post count.

Edit:
The streaming has now gone belly up since 10:11.
Constant spinning circle now @ 10:20

Logged out and now struggling to log in to the supersport.com website, so seems to be an issue on their side?
Eventually logged on, but can't get the cricket stream going.
Okay got it going, but took very long.

Running smooth again.
Click to expand...

We've confirmed with MTN that we are peered with Level 3 in the EU. It does not make sense to peer with them locally and we don't believe that it has any effect on local streaming performance.

So we're definitely satisfied that we're doing what we're supposed to be on our side.
 
Ol' Mean Bastid said:
just did the test using the telkom guest account, you gotta love these results :(

Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5


ping 8.8.8.8

Request timeout for icmp_seq 1
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 192.168.1.1 1 ms
2 165.145.102.1 6 ms
3 Request timed out *
4 Request timed out *
5 Request timed out *
6 Request timed out *
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 *
16 Request timed out *
17 Request timed out *
18 Request timed out *
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 Request timed out *
30 Request timed out *


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms
2 Request timed out *
165.145.102.1 6 ms
3 Request timed out * *
4 Request timed out * *
5 Request timed out * *
6 Request timed out * *
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 * *
16 Request timed out * *
17 Request timed out * *
18 Request timed out * *
19 Request timed out * *
20 Request timed out * *
21 Request timed out * *
22 Request timed out * *
23 Request timed out * *
24 Request timed out * *
25 Request timed out * *
26 Request timed out * *
27 Request timed out * *
28 Request timed out * *
29 Request timed out *
30 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.49
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


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
Click to expand...

LOL, the guest account is locked to telkom's sites, so it won't be able to do much.
 
Ol' Mean Bastid said:
okay, so Telkom recreated the port, they say there doesn't appear to be any problems at the exchange but it still looks like there's problems, so they suggested I log a fault with AH which I have just done
Click to expand...

Interesting, they say there's no problem but that we should log a fault with them to find the problem.

Cool, we'll do that ;)
 
AfriMan said:
We've confirmed with MTN that we are peered with Level 3 in the EU. It does not make sense to peer with them locally and we don't believe that it has any effect on local streaming performance.

So we're definitely satisfied that we're doing what we're supposed to be on our side.
Click to expand...

I had that problem that lasted about 30 minutes and then it ran solid again.
I'm happy with the Home account so far.
 
I am loving my Afrihost experience. Despite the few hassles and issues...still a great service that suits my needs.

Now if Telkom would be ever so damn kind and upgrade my DP to 10mb...
 
Holy balls Afriman, that shaping policy.

Shaping Policy: 50% Download/ 50% P2P

Not exactly what a new user of not even a month, wants to see.
Care to explain?
 
I'm shaped to 18.8 and 6.5%
65 GB on 4 Mbps line.
Rest of services running fine, including streaming
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X