Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Ping Test:

ping 197.242.144.102

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


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=209 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=188 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=190 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 2 ms 4 ms
2 Request timed out * *
3 41.181.178.6 57 ms 56 ms
4 41.181.178.5 65 ms 48 ms
5 41.181.165.1 73 ms 54 ms
6 196.44.0.2 56 ms 57 ms
7 196.44.31.9 50 ms 49 ms
8 196.30.1.3 61 ms 67 ms
9 196.31.220.2 49 ms
196.31.63.2 48 ms
10 196.31.63.2 50 ms
196.30.42.1 56 ms
11 196.30.42.1 58 ms
197.242.144.1 49 ms
12 197.242.144.1 91 ms


traceroute -n 8.8.8.8

1 192.168.0.1 2 ms 2 ms
2 Request timed out * *
3 41.181.221.2 52 ms
Request timed out *
4 41.181.165.1 51 ms
Request timed out *
5 41.181.165.1 57 ms
Request timed out *
6 41.181.139.1 43 ms
Request timed out *
7 72.14.194.7 49 ms
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: 173.194.34.81
Name: www.google.com
Address: 173.194.34.83
Name: www.google.com
Address: 173.194.34.84
Name: www.google.com
Address: 173.194.34.82
Name: www.google.com
Address: 173.194.34.80


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Here's a tip... dump Axxess or anyone who uses the MTN backbone if you want to stream Netflix.
 
pumbaa said:
Just received my mystery bonus Thanks a stack. What to do ... What to do ... :D
Click to expand...

Really liking the looks of this new series called Dominion. Would great for a (legal) download :)

Otherwise, I'm sure there's a distro that needs your full attention :)
 
Beri said:
Ping Test:

ping 197.242.144.102

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


ping 8.8.8.8

Request timeout for icmp_seq 1
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=209 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=188 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=190 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 2 ms 4 ms
2 Request timed out * *
3 41.181.178.6 57 ms 56 ms
4 41.181.178.5 65 ms 48 ms
5 41.181.165.1 73 ms 54 ms
6 196.44.0.2 56 ms 57 ms
7 196.44.31.9 50 ms 49 ms
8 196.30.1.3 61 ms 67 ms
9 196.31.220.2 49 ms
196.31.63.2 48 ms
10 196.31.63.2 50 ms
196.30.42.1 56 ms
11 196.30.42.1 58 ms
197.242.144.1 49 ms
12 197.242.144.1 91 ms


traceroute -n 8.8.8.8

1 192.168.0.1 2 ms 2 ms
2 Request timed out * *
3 41.181.221.2 52 ms
Request timed out *
4 41.181.165.1 51 ms
Request timed out *
5 41.181.165.1 57 ms
Request timed out *
6 41.181.139.1 43 ms
Request timed out *
7 72.14.194.7 49 ms
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: 173.194.34.81
Name: www.google.com
Address: 173.194.34.83
Name: www.google.com
Address: 173.194.34.84
Name: www.google.com
Address: 173.194.34.82
Name: www.google.com
Address: 173.194.34.80


nslookup thishouldfail.afrihost.com

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

That timeout on hop 2 seems to be the same, and it looks like the routing issue that roadcat reported. I'm still working with MTN on this, but they asked for new traces. Can you please both me new traces with your usernames (and anyone else still experiencing this timeout on hop 2 and routing through North from the South)
 
AfriGuy said:
:D
Click to expand...

I have received no bonus. Again. 4 months in a row of having to ask manually.

This is even after changing the email address recorded in the clientzone as suggested last month to rule out the old email was the problem and the mail may have been getting blocked.

Tired of it.

Really poor form.
 
thewusman said:
I have received no bonus. Again. 4 months in a row of having to ask manually.

This is even after changing the email address recorded in the clientzone as suggested last month to rule out the old email was the problem and the mail may have been getting blocked.

Tired of it.

Really poor form.
Click to expand...

Why would your email address affect allocation of the mystery bonus? Surely the email is just for notification purposes?
 
thewusman said:
I have received no bonus. Again. 4 months in a row of having to ask manually.

This is even after changing the email address recorded in the clientzone as suggested last month to rule out the old email was the problem and the mail may have been getting blocked.

Tired of it.

Really poor form.
Click to expand...

I haven't received the email yet either. Perhaps they're staggered?
 
AfriMan said:
That timeout on hop 2 seems to be the same, and it looks like the routing issue that roadcat reported. I'm still working with MTN on this, but they asked for new traces. Can you please both me new traces with your usernames (and anyone else still experiencing this timeout on hop 2 and routing through North from the South)
Click to expand...

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=49 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=48 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=51 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=48 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=48 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=44 time=188 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=44 time=188 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=44 time=189 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=44 time=218 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=44 time=188 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 41.181.178.6 58 ms 54 ms 55 ms
4 41.181.178.5 46 ms 46 ms 47 ms
5 41.181.165.1 53 ms 60 ms
196.31.180.4 54 ms
6 196.44.0.2 55 ms 56 ms
196.31.180.4 56 ms
7 196.44.31.9 49 ms 47 ms 48 ms
8 196.30.1.3 53 ms 53 ms
196.31.220.2 62 ms
9 196.31.220.2 48 ms 49 ms
196.31.63.2 48 ms
10 196.30.42.1 56 ms 56 ms
196.31.63.2 48 ms
11 197.242.144.1 50 ms 48 ms 47 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 41.181.221.2 50 ms 50 ms
Request timed out *
4 41.181.221.2 49 ms 50 ms
Request timed out *
5 41.181.165.1 56 ms 51 ms
Request timed out *
6 41.181.165.1 42 ms 43 ms
Request timed out *
7 72.14.194.7 48 ms 83 ms
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: 173.194.41.176
Name: www.google.com
Address: 173.194.41.178
Name: www.google.com
Address: 173.194.41.180
Name: www.google.com
Address: 173.194.41.179
Name: www.google.com
Address: 173.194.41.177


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Chevron said:
Why would your email address affect allocation of the mystery bonus? Surely the email is just for notification purposes?
Click to expand...

If you don't get an email notification you haven't got a bonus.

It's not rocket science, some bundle clients simply aren't getting their bonuses and have to ask manually.

The best AH can say is "we have sent you the mail it must be getting blocked, check your spam filter".

Funny that. 2 email addresses. One Gmail, the other Exchange based. No rules. No filters. All other AH emails come through, even promo types.
 
There is definitely shaping or some limiting happening on the capped account tonight :( It's bursting from line speed down to <1/10th of that in a way that only a shaper can. Time to bypass this rubbish DSL and start dealing with a Tier1 ISP via FTTx.
 
Timber_MG said:
There is definitely shaping or some limiting happening on the capped account tonight :( It's bursting from line speed down to <1/10th of that in a way that only a shaper can. Time to bypass this rubbish DSL and start dealing with a Tier1 ISP via FTTx.
Click to expand...

Seeing throughput issues too, not that it's abnormal. Also seeing packet loss, which is also not abnormal but not normally an issue on a Sunday evening when the line is completely idle.

Screenshot%202014-06-22%2019.39.45.png


These AH capped accounts are about as reliable as a chocolate solar panel.
 
The packet loss has been endemic of late. One will never get anything other than PR out of this lot. Now about Bitco, and not as a WISP...
 
thewusman said:
I have received no bonus. Again. 4 months in a row of having to ask manually.

This is even after changing the email address recorded in the clientzone as suggested last month to rule out the old email was the problem and the mail may have been getting blocked.

Tired of it.

Really poor form.
Click to expand...

Sorry to hear that. It's pretty odd that your address consistenly fails, I'm pretty sure you are in the list to be emailed.

Please PM (if you haven't already - still catching up from the weekend) and I'll drop you the info you need.
 
thewusman said:
If you don't get an email notification you haven't got a bonus.

It's not rocket science, some bundle clients simply aren't getting their bonuses and have to ask manually.

The best AH can say is "we have sent you the mail it must be getting blocked, check your spam filter".

Funny that. 2 email addresses. One Gmail, the other Exchange based. No rules. No filters. All other AH emails come through, even promo types.
Click to expand...

There is definitely something odd happening. I would normally say that you'll usually have a percentage of exceptions when doing bulk mail, but to fail consistently four months in a row and on different addresses is definitely pretty odd :(
 
I don't get it when people go for the bundle option. It's cheaper to go unbundled and you know your always getting double data till September or longer if they extend it.
 
Mark.K said:
I don't get it when people go for the bundle option. It's cheaper to go unbundled and you know your always getting double data till September or longer if they extend it.
Click to expand...

We should be revising bundles again to offer some great value. Don't have all the details but best to stay bundle for now - we probably do mystery bonuses until the new bundle structure comes into effect :)
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X