Afrihost Uncapped ADSL Feedback (Pt2)

[vicv]

A few pages back - ask anyone in JHB to check their shaping and post back

I haven't been shaped since the upgrade

 

[hawker]

I haven't been shaped since the upgrade

Same. It's glorious.

 

[wingnut771]

When I had ADSDL directly with Telkom, it was easy to get hold of Telkom and resolve, but Afrihost is supposed to be "now managing the ADSL line", and it seems like that nothing is being managed.

Never keep your ADSL with an ISP for exactly this reason.

 

[ClintonExsteen]

internet keeps falling over, total lose of connection, job interview well that was a fail.... 3rd time I have requested support to help

 

[Hectic]

You would generally never get full speed on an international throughput because of the additional latency. It will also vary according to traffic etc.

Is this on a 4Mbps line?

Yes it is on 4Mbps line, so I would expect speeds in the region of 3.2 - 3.4Mbps, which is what I got my TI uncapped account till they self destructed.

Surlely you can't tell me you provide 2Mbps just because it is an uncapped account?

I'm in the Eastern Cape.

 

[Type RSA]

Would anyone recommend going back onto Home Uncapped from Business Uncapped. How is the shaping looking in the North of Joburg?

 

[5plus2equals9]

People in the North are fortunate

 

[HowTo]

AfriMan

Quick question Capped account contention ratio?

 

[AfriMan]

When I had ADSDL directly with Telkom, it was easy to get hold of Telkom and resolve, but Afrihost is supposed to be "now managing the ADSL line", and it seems like that nothing is being managed.

I'm sorry that it took too long to reach us to log the issue - but I do believe Telkom would also have logged a fault for a technician to investigate and from that point it would be the same process. Without knowing what is happening on the exchange - which we don't manage, just the line - we can't really do much for now and neither could Telkom or any ISP managing your line.

 

[AfriMan]

Never keep your ADSL with an ISP for exactly this reason.

Aside from taking a while to reach us cos our response is slow, I think we've handled this the right way.

I also personally love having my line managed cos I can use Fix My Line when things are crappy. Have used it extensively cos I'm on an old exchange, and it does wonders for me

But to each his own, I guess

 

[AfriMan]

internet keeps falling over, total lose of connection, job interview well that was a fail.... 3rd time I have requested support to help

Sorry that you're battling with your line. What do you Network Test App results look like?

 

[AfriMan]

Yes it is on 4Mbps line, so I would expect speeds in the region of 3.2 - 3.4Mbps, which is what I got my TI uncapped account till they self destructed.

Surlely you can't tell me you provide 2Mbps just because it is an uncapped account?

I'm in the Eastern Cape.

We're talking strictly international here now. It would be very unusual to have full line speed on international. If you're getting 3.4Mbps local on a 4Mbps line, then around 2.8Mbps for international would be considered good and anything above excellent.

Remember that you're looking at 180ms to EU vs 15-20ms local latency, and around 260ms to the US. That extra latency will definitely affect overall throughput.

 

[AfriMan]

People in the North are fortunate

View attachment 99199

Yeah, someone in Cape Town is downloading all the things

 

[Shamus]

In the EC and shaped to 25% download - why????

 

[Hectic]

We're talking strictly international here now. It would be very unusual to have full line speed on international. If you're getting 3.4Mbps local on a 4Mbps line, then around 2.8Mbps for international would be considered good and anything above excellent.

Remember that you're looking at 180ms to EU vs 15-20ms local latency, and around 260ms to the US. That extra latency will definitely affect overall throughput.

Well if you look at my post #9853 you will see that my local speed test indicate 2Mbps.

Is this normal Afrihost?

I've added a MTR test to afrihost.co.za or do I need to test another location.
Maybe it sheds some info.

 

[wingnut771]

Aside from taking a while to reach us cos our response is slow, I think we've handled this the right way.

I also personally love having my line managed cos I can use Fix My Line when things are crappy. Have used it extensively cos I'm on an old exchange, and it does wonders for me

But to each his own, I guess

Back in the day when I did have my line with you, out of curiosity, I tried this facility on numerous occasions but never worked, or should I say never finished, longest 3 minutes of my life.

If it did work, then I would see the benefit, but alas, there was none, so moved it back to Telkom when I ditched home uncapped after the MTN move.

While on the subject of diag tools, the network test tool gives me time-outs when there are none, ie; I have a perfect line/exchange and doing the same tests that the tool does, all looks normal, but the tool makes my line look like swiss cheese.

So, nice tool set concept you have but just a big paper weight for me as they don't work.

 

[Fudzy]

I also personally love having my line managed cos I can use Fix My Line when things are crappy. Have used it extensively cos I'm on an old exchange, and it does wonders for me

You should have left it unbundled and you wouldn't have to battle with constant line issues.

 

[TEXTILE GUY]

So, nice tool set concept you have but just a big paper weight for me as they don't work.

Also take a look here ...
http://mybroadband.co.za/vb/showthread.php/576445-quot-Help-me-fix-my-internet-quot-report-tool

Thanks to user Zertop, a great little tracert / ping analysis tool for diagnostics aimed at those folk who are on a steep IT incline so to speak.

 

[wingnut771]

Also take a look here ...
http://mybroadband.co.za/vb/showthread.php/576445-quot-Help-me-fix-my-internet-quot-report-tool

Thanks to user Zertop, a great little tracert / ping analysis tool for diagnostics aimed at those folk who are on a steep IT incline so to speak.

I should have included Zertop's tool in my previous comment, as that just backs up my theory AH tool is broken.

Case in point:

Zertop:

Local Tracert

Tracing route to google.co.za [173.194.34.119]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 8 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 22 ms 21 ms 21 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
4 21 ms 22 ms 21 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
5 23 ms 22 ms 22 ms core1a-pkl-te-1-1.ip.isnet.net [196.26.0.60]
6 21 ms 21 ms 19 ms 168.209.1.179
7 23 ms 21 ms 21 ms 74.125.49.66
8 187 ms 186 ms 185 ms 66.249.95.8
9 186 ms 186 ms 185 ms 209.85.253.47
10 184 ms 184 ms 184 ms lhr14s20-in-f23.1e100.net [173.194.34.119]

Trace complete.

International Tracert

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 9 ms 9 ms 196-210-157-1.dynamic.isadsl.co.za [196.210.157.1]
3 20 ms 24 ms 21 ms 196.38.72.229
4 22 ms 20 ms 19 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
5 24 ms 24 ms 22 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 189 ms 186 ms 187 ms 168.209.201.93
7 186 ms 184 ms 184 ms linx-gw2.thdo.ncuk.net [195.66.236.240]
8 193 ms 193 ms 192 ms gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
9 190 ms 189 ms 203 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 20.0 megabytes in 49 seconds. (412.04 KB/s)

Local Speedtest


Test End Timestamp
2014/02/12 7:59:02.05

AH Test Tool:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=24 ms
Request timeout for icmp_seq 2
64 bytes from 197.242.144.102: icmp_req=3 ttl=56 time=24 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=23 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=23 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=45 time=191 ms
Request timeout for icmp_seq 2
64 bytes from 8.8.8.8: icmp_req=3 ttl=45 time=190 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=45 time=190 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 10 ms 8 ms
3 196.38.73.1 57 ms 20 ms
4 196.38.73.1 20 ms
168.209.1.1 23 ms
5 168.209.1.1 42 ms 20 ms
6 168.209.1.1 22 ms
41.208.29.1 22 ms
7 41.208.29.1 61 ms
196.44.0.2 23 ms
8 196.44.0.2 24 ms
196.44.31.9 23 ms
9 196.44.31.9 23 ms
196.31.220.6 22 ms
10 196.31.220.6 46 ms
196.31.220.2 23 ms
11 196.31.63.1 36 ms
197.242.144.1 24 ms
12 197.242.144.1 23 ms


traceroute -n 8.8.8.8

1 192.168.1.1 1 ms 1 ms
2 196.210.157.1 9 ms 9 ms
3 196.38.73.1 19 ms 19 ms
4 196.38.73.1 19 ms 20 ms
5 168.209.1.1 22 ms 21 ms
6 168.209.1.1 19 ms 19 ms
7 74.125.49.6 35 ms
Request timed out *
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.132.104
Name: www.google.com
Address: 74.125.132.106
Name: www.google.com
Address: 74.125.132.99
Name: www.google.com
Address: 74.125.132.103
Name: www.google.com
Address: 74.125.132.147
Name: www.google.com
Address: 74.125.132.105


nslookup thishouldfail.afrihost.com

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

 

[wingnut771]

ping -n 100 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=194ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=189ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=190ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=193ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=202ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=191ms TTL=45
Reply from 8.8.8.8: bytes=32 time=192ms TTL=45

Ping statistics for 8.8.8.8:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 189ms, Maximum = 202ms, Average = 190ms