Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Sinbad said:
Did you see my posts as well? Hopefully will lead the guys towards a solution.
Click to expand...

Yes, I have also seen them - everything seems to point to similar symptoms around peak demand on the network - and that leads me to believe it could be contention.

I notice you mentioned FNB connect - I don't know if they run on the MTN backbone or not, but they definitely don't run off our IPC, so that would be totally unrelated. Can you confirm they run off MTN - because I was under the impression that they had their own IPC at some stage?
 
BLIXEMPIE said:
I see it's not just me then. I sent some emails to Afrihost trying to get an explanation for all the shaping. My NNTP downloads are DEAD at 0KB/s. Only after 1am now did I see it coming alive again at acceptable speeds. But every day now for 3 days my NNTP downloads stop completely during the day and night up to 1am. Also my torrents don't run over 15KB/s. Is this shaping or some general issue? I also experienced latency spikes during online gaming tonight. It should be known I am a new uncapped subscriber with AH, so I don't know how my experience compares to that of other users. Do you all get shaped like this?
Click to expand...

Have you run any comparisons, like off a Free GB to see if you get different results on your P2P? This would definitely confirm shaping. Also, what DNS settings are you using?
 
myjdjames said:
did this too:
Ping Test:

ping 197.242.144.102

Request timeout for icmp_seq 1
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=56 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=43 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=58 time=47 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=211 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=42 time=215 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=42 time=216 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=42 time=211 ms
Request timeout for icmp_seq 5


Trace Test:

traceroute -n 197.242.144.102

1 192.168.0.1 1 ms 1 ms
2 41.181.221.2 51 ms
105.236.0.1 33 ms
3 41.181.165.1 44 ms
41.181.221.2 43 ms
4 196.44.31.1 44 ms
41.181.165.1 86 ms
5 196.30.1.5 42 ms
196.44.31.1 55 ms
6 196.31.220.2 47 ms
196.44.31.9 44 ms
7 196.30.42.1 46 ms
196.31.220.2 45 ms
8 197.242.144.1 43 ms
196.31.63.2 50 ms
9 196.30.42.1 52 ms
10 197.242.144.1 43 ms


traceroute -n 8.8.8.8

1 192.168.0.1 1 ms 1 ms 1 ms
2 105.236.0.1 33 ms 33 ms 47 ms
3 41.181.221.2 55 ms 53 ms
41.181.165.1 78 ms
4 41.181.165.1 56 ms 46 ms
41.181.139.9 45 ms
5 41.181.139.9 44 ms
196.44.0.1 43 ms
72.14.194.7 50 ms
6 72.14.194.7 45 ms
41.181.139.9 45 ms
72.14.242.2 212 ms
7 8.8.8.8 210 ms


DNS Test:

nslookup www.afrihost.com

Name: www.afrihost.com
Address: 197.242.144.102


nslookup www.google.com

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


nslookup thishouldfail.afrihost.com

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

Your local ping and hop to the exchange seems higher than it should be. Do you experience this consistently even with other ISP networks?
 
AfriMan said:
Yes, I have also seen them - everything seems to point to similar symptoms around peak demand on the network - and that leads me to believe it could be contention.

I notice you mentioned FNB connect - I don't know if they run on the MTN backbone or not, but they definitely don't run off our IPC, so that would be totally unrelated. Can you confirm they run off MTN - because I was under the impression that they had their own IPC at some stage?
Click to expand...
FNB connect definitely runs off MTN. Can't traceroute now to prove it but I'm 100% sure it's the case.

Contention where? IPC, exchange, or international transit?
 
18 gig file on the wire right now. Managed 5 gigs last night and I think my line will only get this done by Thursday...


(only on 2meg uncapped so that's expected)
 
Sinbad said:
FNB connect definitely runs off MTN. Can't traceroute now to prove it but I'm 100% sure it's the case.

Contention where? IPC, exchange, or international transit?
Click to expand...

It would be at the IPC level - which is why it should have nothing to do with FNB unless they were Afrihost or Axxess resellers. IPC contention can manifest on local or overseas traffic, but would be more noticeable on overseas traffic.
 
Wall said:
18 gig file on the wire right now. Managed 5 gigs last night and I think my line will only get this done by Thursday...


(only on 2meg uncapped so that's expected)
Click to expand...

East IPC has been chugging along nicely since upgrade - so glad there is nothing to report (or nothing bad at least) ;)
 
AfriMan said:
East IPC has been chugging along nicely since upgrade - so glad there is nothing to report (or nothing bad at least) ;)
Click to expand...

yeah, I just checked Clientzone and I'm unshaped :D

Its a game from psn store...
 
AfriMan said:
It would be at the IPC level - which is why it should have nothing to do with FNB unless they were Afrihost or Axxess resellers. IPC contention can manifest on local or overseas traffic, but would be more noticeable on overseas traffic.
Click to expand...
So nope. It's not IPC contention. (When I turbocharge, I get full speed on NNTP just by the way - so in terms of contention, there is no issue).

There's intermittent packet loss between MTN and the D3 servers somewhere along the line - and the shapers are shaping D3 traffic into the same bucket as NNTP. Two separate issues.
 
Sinbad said:
So nope. It's not IPC contention. (When I turbocharge, I get full speed on NNTP just by the way - so in terms of contention, there is no issue).

There's intermittent packet loss between MTN and the D3 servers somewhere along the line - and the shapers are shaping D3 traffic into the same bucket as NNTP. Two separate issues.
Click to expand...

Maybe if you run MTR to an D3 server - might show us where the packet loss is happening. Then I can definitely escalate that to MTN for their assistance.
 
AfriMan said:
Maybe if you run MTR to an D3 server - might show us where the packet loss is happening. Then I can definitely escalate that to MTN for their assistance.
Click to expand...

Happy to give it a shot. In the meantime can you check with the techies that the IPs I gave earlier are tagged as being realtime-service IPs? (maybe Blizzard added some new servers with the expansion, for instance).
 
Sinbad said:
Happy to give it a shot. In the meantime can you check with the techies that the IPs I gave earlier are tagged as being realtime-service IPs? (maybe Blizzard added some new servers with the expansion, for instance).
Click to expand...

Crap - can't seem to find them. Can you drop them in a PM and I'll fire off that query ASAP?
 
AfriMan said:
That sucks. Can I see that full trace route?
Click to expand...

spje6W9.jpg


yn9R8lg.jpg
 
Last edited:
New customer with Afrihost - happy with the speeds even though I don't understand how the shaping works, the speeds I'm getting does not correspond with the shaping stated on client-zone...

Last 24 hours - Green FTP Download - red web traffic:
chart.png
 
Help please, barely able to browse

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

64 bytes from 8.8.8.8: icmp_req=1 ttl=43 time=1474 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=43 time=1766 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=43 time=1610 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=43 time=1585 ms



Trace Test:

traceroute -n 197.242.144.102

1 Request timed out * *
10.0.0.2 139.061 ms
2 Request timed out * *
105.236.14.65 350.231 ms
3 Request timed out * *
undefined NaN ms
4 Request timed out * *
41.181.178.89 547.304 ms
5 Request timed out * *
196.44.0.146 966.38 ms
6 Request timed out * * *
7 Request timed out * *
undefined NaN ms
8 Request timed out * *
41.181.165.115 870.517 ms
9 Request timed out * *
undefined NaN ms
10 Request timed out * * *
11 Request timed out * * *
12 undefined NaN ms
Request timed out *
196.31.63.206 931.508 ms
13 Request timed out * *
undefined NaN ms
14 undefined NaN ms
Request timed out *
196.30.42.133 474.463 ms
15 Request timed out * *
undefined NaN ms
16 undefined NaN ms
Request timed out *
197.242.144.102 566.721 ms
17 Request timed out * *
18 Request timed out * *
19 Request timed out *
undefined NaN ms
20 Request timed out * *
21 Request timed out *
undefined NaN ms
22 Request timed out * *
23 197.242.144.102 790.23 ms
Request timed out *
24 Request timed out *
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 undefined NaN ms
29 197.242.144.102 748.916 ms
30 undefined NaN ms


traceroute -n 8.8.8.8

1 10.0.0.2 836.809 ms 23.805 ms 77.05 ms
2 Request timed out *
105.236.14.65 69.608 ms 392.815 ms
3 Request timed out *
41.181.178.77 57.952 ms 810.97 ms
4 undefined NaN ms
196.44.0.146 76.95 ms 776.191 ms
5 Request timed out *
196.44.31.95 21.125 ms 433.146 ms
6 Request timed out *
41.181.165.115 56.832 ms
undefined NaN ms
7 Request timed out *
72.14.194.74 68.997 ms
41.181.165.115 948.501 ms
8 undefined NaN ms NaN ms
66.249.95.8 247.895 ms
9 Request timed out * * *
10 Request timed out * *
66.249.95.8 970.822 ms
11 Request timed out *
8.8.8.8 236.419 ms
209.85.253.196 918.679 ms
12 Request timed out *
66.249.95.173 815.605 ms
13 Request timed out *
undefined NaN ms
14 Request timed out *
8.8.8.8 599.985 ms
15 Request timed out *
undefined NaN ms
16 undefined NaN ms
17 Request timed out *
18 undefined NaN ms
19 Request timed out *
20 Request timed out *
21 Request timed out *
22 Request timed out *
23 Request timed out *
24 undefined NaN ms
25 Request timed out *
26 Request timed out *
27 Request timed out *
28 Request timed out *
29 8.8.8.8 635.385 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.34.115
Name: www.google.com
Address: 173.194.34.116
Name: www.google.com
Address: 173.194.34.113
Name: www.google.com
Address: 173.194.34.112
Name: www.google.com
Address: 173.194.34.114


nslookup thishouldfail.afrihost.com

** server can't find thisshouldfail.com: NXDOMAIN
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X