Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
Beri said:
No idea. Strange thing. My one computer is connected via a lan cable and it works. The router shows that their is no internet connection and the light is red. I connect via wifi but have no internet. On laptop or ipad.
Click to expand...

And the trace was done from the LAN connected PC? Will see what my AH Network test tool says for it's routing but those private addresses normally would mean it's finding another route out.
 
roadcat said:
And the trace was done from the LAN connected PC? Will see what my AH Network test tool says for it's routing but those private addresses normally would mean it's finding another route out.
Click to expand...

Charlo exchange:

traceroute -n 197.242.144.102

1 10.0.0.2 1 ms 1 ms
2 Request timed out * *
3 41.181.178.3 46 ms 46 ms
4 41.181.178.2 49 ms 48 ms
5 41.181.165.1 54 ms 53 ms
6 41.181.165.1 53 ms 55 ms
7 196.31.220.8 54 ms
196.44.31.9 46 ms
8 196.31.220.2 47 ms
196.31.220.8 57 ms
9 196.31.63.2 54 ms
196.31.220.2 47 ms
10 196.30.42.1 55 ms
196.31.63.2 54 ms
11 196.30.42.1 55 ms
12 197.242.144.1 54 ms
 
roadcat said:
And the trace was done from the LAN connected PC? Will see what my AH Network test tool says for it's routing but those private addresses normally would mean it's finding another route out.
Click to expand...

Your 5th hop is a Telkom 8ta IP address - have you got something else connected?

1 172.20.10.1 1 ms 1 ms 42 ms
2 Request timed out * * *
3 172.17.32.9 141 ms 168 ms 143 ms
4 192.168.102.2 136 ms 91 ms 122 ms
5 41.150.177.2 58 ms
 
@Afrihost, I'm currently on your 2meg uncapped product. I, switched over to my capped Afrihost account because of shaping.

I then used up all my data on the capped account and I couldn't access any websites. That's understandable but I couldn't even access Afrihost.com to get my access details to switch over to my uncapped line.


I think that if you capped, it should take you to afrihost.com as a landing page. From there you can purchase more data or view your balance etc.

just my 2c.

PS - I eventually downloaded your mobile app and recharged my prepaid account from there...
 
Beri said:
Cannot connect via wifi. Red light on my router shows no sync but my son is connected via a lan cable and it works but very slow.
he reported lots of issues today.
Click to expand...

Really sorry about the authentication issues, our team does seem to have found a fix for this. We're monitoring everything very closely along with MTN and Telkom.

Strange that a LAN connection would work though :/
 
DrJohnZoidberg said:
Afrihost really starting to annoy me. First there is the subpar performance on their unshaped capped accounts, then the authentication issues and now they've decided to overcharge me this month for this wonderful service.

I think I have been a pretty easy customer to this point, but when I get overcharged by over R300 I start getting annoyed. :mad:
Click to expand...

I can't see any anomalies on our billing system, what was the overcharge for?
 
Wall said:
@Afrihost, I'm currently on your 2meg uncapped product. I, switched over to my capped Afrihost account because of shaping.

I then used up all my data on the capped account and I couldn't access any websites. That's understandable but I couldn't even access Afrihost.com to get my access details to switch over to my uncapped line.


I think that if you capped, it should take you to afrihost.com as a landing page. From there you can purchase more data or view your balance etc.

just my 2c.

PS - I eventually downloaded your mobile app and recharged my prepaid account from there...
Click to expand...

I feel you, this is definitely something that we're working on though :)
You can always setup an auto topup in the mean time.
 
AfriGuy said:
I can't see any anomalies on our billing system, what was the overcharge for?
Click to expand...

Was sorted out this morning. There was an "error" which caused my bundle discount not to reflect. I wonder how many other clients also have this error but haven't noticed it.
 
DrJohnZoidberg said:
Was sorted out this morning. There was an "error" which caused my bundle discount not to reflect. I wonder how many other clients also have this error but haven't noticed it.
Click to expand...

Very strange, is there a ticket ref# that I can look at on this?
 
I see it is a Telkom network fault in regards to authentication in the Cape. Apologies.
 
Last edited:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=45 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=44 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=208 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=206 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=207 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=206 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=206 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 2 ms
2 Request timed out * * *
3 41.181.178.3 50 ms 50 ms 49 ms
4 41.181.178.2 50 ms 49 ms 49 ms
5 41.181.165.1 42 ms 43 ms 41 ms
6 196.31.180.4 41 ms 49 ms 41 ms
7 196.44.31.9 53 ms 51 ms 51 ms
8 196.31.220.8 51 ms 42 ms 41 ms
9 196.31.220.2 53 ms 50 ms 52 ms
10 196.31.63.2 49 ms 50 ms 49 ms
11 197.242.144.1 43 ms 44 ms 43 ms


traceroute -n 8.8.8.8

1 192.168.0.1 2 ms 2 ms 1 ms
2 Request timed out * * *
3 41.181.178.4 49 ms
Request timed out * *
4 41.181.178.4 146 ms 49 ms
Request timed out *
5 41.181.165.1 42 ms 43 ms
Request timed out *
6 Request timed out * *
196.31.180.4 75 ms
7 Request timed out * *
41.181.180.1 202 ms
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.78.104
Name: www.google.com
Address: 173.194.78.105
Name: www.google.com
Address: 173.194.78.103
Name: www.google.com
Address: 173.194.78.106
Name: www.google.com
Address: 173.194.78.99
Name: www.google.com
Address: 173.194.78.147


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Intl. Latency is about 35-40ms lower than usual but packet loss and jitter today, wonder whether some things are being router over SAT3/SAFE?
 
and the crap continues

port recreated, AH says no problems with the line, and so we're all hunky dory

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.0.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 11 ms 13 ms 13 ms 105-236-12-193-esr-lo.mtnbusiness.co.za [105.236.12.193]
4 32 ms 26 ms 39 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
5 8 ms 7 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 8 ms 7 ms 7 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
7 8 ms 11 ms 23 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
8 * 14 ms 19 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
9 33 ms 39 ms 26 ms postfix.wipronet.co.za [196.22.161.133]
10 68 ms 54 ms 32 ms tengig-0-0-0-3-vic-p-2.mweb.co.za [197.80.7.34]
11 37 ms 79 ms 34 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
12 30 ms 99 ms 67 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
13 30 ms 30 ms 32 ms 196.28.178.66
14 75 ms 28 ms 52 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
15 34 ms 33 ms 30 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
16 28 ms 27 ms 69 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
17 30 ms 42 ms 171 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert
Unable to resolve target system name thinkbroadband.com.

International Speedtest

Local Speedtest
Downloaded 15.6 megabytes in 48 seconds. (328.72 KB/s)
 
Ol' Mean Bastid said:
and the crap continues

port recreated, AH says no problems with the line, and so we're all hunky dory

Local Tracert

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms [192.168.0.1]
2 1 ms 1 ms 1 ms 192.168.1.1
3 11 ms 13 ms 13 ms 105-236-12-193-esr-lo.mtnbusiness.co.za [105.236.12.193]
4 32 ms 26 ms 39 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
5 8 ms 7 ms 10 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
6 8 ms 7 ms 7 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.180.4]
7 8 ms 11 ms 23 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
8 * 14 ms 19 ms jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]
9 33 ms 39 ms 26 ms postfix.wipronet.co.za [196.22.161.133]
10 68 ms 54 ms 32 ms tengig-0-0-0-3-vic-p-2.mweb.co.za [197.80.7.34]
11 37 ms 79 ms 34 ms tengig-0-0-0-0-cpt-p-1.mweb.co.za [197.84.4.34]
12 30 ms 99 ms 67 ms vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
13 30 ms 30 ms 32 ms 196.28.178.66
14 75 ms 28 ms 52 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
15 34 ms 33 ms 30 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
16 28 ms 27 ms 69 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
17 30 ms 42 ms 171 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.

International Tracert
Unable to resolve target system name thinkbroadband.com.

International Speedtest

Local Speedtest
Downloaded 15.6 megabytes in 48 seconds. (328.72 KB/s)
Click to expand...

The latency spikes and timeouts seem concerning, especially the error on thinkbroadband.com

Does the same occur on other ISP networks?
 
Beri said:
Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=45 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=44 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=208 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=45 time=206 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=207 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=206 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=45 time=206 ms


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms 2 ms
2 Request timed out * * *
3 41.181.178.3 50 ms 50 ms 49 ms
4 41.181.178.2 50 ms 49 ms 49 ms
5 41.181.165.1 42 ms 43 ms 41 ms
6 196.31.180.4 41 ms 49 ms 41 ms
7 196.44.31.9 53 ms 51 ms 51 ms
8 196.31.220.8 51 ms 42 ms 41 ms
9 196.31.220.2 53 ms 50 ms 52 ms
10 196.31.63.2 49 ms 50 ms 49 ms
11 197.242.144.1 43 ms 44 ms 43 ms


traceroute -n 8.8.8.8

1 192.168.0.1 2 ms 2 ms 1 ms
2 Request timed out * * *
3 41.181.178.4 49 ms
Request timed out * *
4 41.181.178.4 146 ms 49 ms
Request timed out *
5 41.181.165.1 42 ms 43 ms
Request timed out *
6 Request timed out * *
196.31.180.4 75 ms
7 Request timed out * *
41.181.180.1 202 ms
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.78.104
Name: www.google.com
Address: 173.194.78.105
Name: www.google.com
Address: 173.194.78.103
Name: www.google.com
Address: 173.194.78.106
Name: www.google.com
Address: 173.194.78.99
Name: www.google.com
Address: 173.194.78.147


nslookup thishouldfail.afrihost.com

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

I think this must be something to do with a local Telkom routing. I know roadcat has logged with Telkom - wonder if there has been any progress on this?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X