Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Just received a call from the CC team at Afrihost to ask detailed information regarding my problem.

They took down all the information, asked specific questions relating to the problem and have provided me with a test account while they run my account to pin point the problem.

The type of service I've come to expect from Afrihost.

+1

That's awesome - let's hope the tests we run with you can isolate this issue :)

Thanks for doing this for us.
 
For the entire day I've been having this:

Pinging www.google.co.za [173.194.41.152] with 32 bytes of data:
Reply from 173.194.41.152: bytes=32 time=557ms TTL=53
Reply from 173.194.41.152: bytes=32 time=675ms TTL=53
Reply from 173.194.41.152: bytes=32 time=679ms TTL=53
Reply from 173.194.41.152: bytes=32 time=643ms TTL=53

Ping statistics for 173.194.41.152:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 557ms, Maximum = 679ms, Average = 638ms

Other than that, shaped into the ground. What is going on?

This looks like it's a latency issue, either on your line or exchange - also judging from the other pings you've posted on the thread. Could you please post a full traceroute?
 
This shaping is ridiculous. It's 6AM and I can't even get half my line speed.

*edit*

And my account says no shaping policy is applied. :rolleyes:

We'll need to run further tests here, cos it sounds like whatever is happening is not related to shaping.

Please PM me :(
 
Guy's I'm on the East which got it's full IPC upgrade. Believe me it got a little better, but it's nowhere what I expected. Still shaped to death until 7-8 in the evening regularly. Don't hold your breath.

Seems the only way to go to get a good internet experience is to pony up for a business account.

Remember that shaping is always going to be part of the Uncapped product. Extreme shaping for an hour or so a day is not really that bad compared to other entry Uncapped products that are throttled or hard shaped from 8am to 8pm (or something like that. Remember that it's also demand based, so you won't always be shaped if there is available capacity to allow you to be shaped.

In general, the East network is running nicely and we're seeing many clients unshaped for a lot longer - we think it's a great balance to offer the type of value we want to see in a premium semi-shaped Uncapped product.
 
There's poo on the MTN network


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 10.0.0.1
2 5 ms 4 ms 4 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.14.65]
3 9 ms 9 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 9 ms 8 ms 8 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 9 ms 8 ms 9 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 6 ms 7 ms 6 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 26 ms 9 ms 8 ms 196.44.0.72
8 10 ms 9 ms 10 ms postfix.wipronet.co.za [196.22.161.133]
9 * * 31 ms 197-80-7-34.jhb.mweb.co.za [197.80.7.34]
10 30 ms * * tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
11 * 31 ms 32 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
12 30 ms 29 ms 29 ms 196.28.178.66
13 32 ms 31 ms 31 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 33 ms 57 ms 32 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 29 ms 28 ms 28 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 32 ms 31 ms 31 ms 41-86-110-143.mweb.co.za [41.86.110.143]

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 10.0.0.1
2 5 ms 5 ms 5 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.14.65]
3 8 ms 8 ms 8 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 40 ms 31 ms 9 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 8 ms 7 ms 9 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 7 ms 6 ms 6 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 187 ms 186 ms 186 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 185 ms 197 ms 185 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 * 177 ms 178 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 186 ms 187 ms 187 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 187 ms 188 ms 187 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 183 ms * * te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 182 ms 181 ms 180 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 10.0 megabytes in 1:29 seconds. (113.92 KB/s)

Local Speedtest
Downloaded 8000.0 kilobytes in 31 seconds. (256.31 KB/s)




Test End Timestamp
21/05/2014 9:06:26.47
 
There's poo on the MTN network


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 10.0.0.1
2 5 ms 4 ms 4 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.14.65]
3 9 ms 9 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
4 9 ms 8 ms 8 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 9 ms 8 ms 9 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 6 ms 7 ms 6 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 26 ms 9 ms 8 ms 196.44.0.72
8 10 ms 9 ms 10 ms postfix.wipronet.co.za [196.22.161.133]
9 * * 31 ms 197-80-7-34.jhb.mweb.co.za [197.80.7.34]
10 30 ms * * tengige0-0-0-0.cpt-p-1.mweb.co.za [197.84.4.34]
11 * 31 ms 32 ms 197-84-5-238.cpt.mweb.co.za [197.84.5.238]
12 30 ms 29 ms 29 ms 196.28.178.66
13 32 ms 31 ms 31 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 33 ms 57 ms 32 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 29 ms 28 ms 28 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 32 ms 31 ms 31 ms 41-86-110-143.mweb.co.za [41.86.110.143]

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 10.0.0.1
2 5 ms 5 ms 5 ms 105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.14.65]
3 8 ms 8 ms 8 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 40 ms 31 ms 9 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 8 ms 7 ms 9 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 7 ms 6 ms 6 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 187 ms 186 ms 186 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.114]
8 185 ms 197 ms 185 ms ls-cr-1.uk--ls-cr-2.uk-a.mtnns.net [196.44.31.156]
9 * 177 ms 178 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
10 186 ms 187 ms 187 ms linx-gw1.thn.ncuk.net [195.66.224.240]
11 187 ms 188 ms 187 ms te2-1-9.star10g.bdr-rt3.thdo.ncuk.net [80.249.97.17]
12 183 ms * * te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85]
13 182 ms 181 ms 180 ms www.thinkbroadband.com [80.249.99.130]

Trace complete.

International Speedtest
Downloaded 10.0 megabytes in 1:29 seconds. (113.92 KB/s)

Local Speedtest
Downloaded 8000.0 kilobytes in 31 seconds. (256.31 KB/s)




Test End Timestamp
21/05/2014 9:06:26.47

Not seeing anything too conclusive here. First trace shows problems only after our network, and latency seems mostly normal throughout here.
 
Not seeing anything too conclusive here. First trace shows problems only after our network, and latency seems mostly normal throughout here.

Bad latency on D3 (packet loss resulting in lag spikes), packet loss to google AND local destinations, Zertop showing slow local and international transfers despite account being unshaped according to clientzone...
I guess it could be my exchange - it's not overloaded though, 1st 3 hops are fine. So it points to transit somewhere being an issue?
 
Bad latency on D3 (packet loss resulting in lag spikes), packet loss to google AND local destinations, Zertop showing slow local and international transfers despite account being unshaped according to clientzone...
I guess it could be my exchange - it's not overloaded though, 1st 3 hops are fine. So it points to transit somewhere being an issue?
Dusted off my old free FNB Connect account. Much better...
Definitely an issue with D3 on Afrihost.
 
Correct me if I'm wrong but NNTP forms part of their shaped protocols. Therefor when shaping is active - it SHOULD be shaped.

Yes, but the question becomes if NNTP runs over SSL is just the data encrypted or the entire packet? How do they differentiate between say web SSL traffic and NNTP SSL traffic? According to Afrihost, SSL is not shaped

And also 75% should give me about 300kb/s
 
Yes, but the question becomes if NNTP runs over SSL is just the data encrypted or the entire packet? How do they differentiate between say web SSL traffic and NNTP SSL traffic? According to Afrihost, SSL is not shaped

And also 75% should give me about 300kb/s

Speaking under strict assumptions so forgive me if I sound like an idiot. Even if something runs via ssl and is encrypted, the source signature should still be identifiable as far as I know... (the gurus can weigh in here and correct me if I'm wrong)

And indeed. You should be getting 300. Tracert show any packet loss or latency spikes?
 
Speaking under strict assumptions so forgive me if I sound like an idiot. Even if something runs via ssl and is encrypted, the source signature should still be identifiable as far as I know... (the gurus can weigh in here and correct me if I'm wrong)

And indeed. You should be getting 300. Tracert show any packet loss or latency spikes?

Not sure what you mean by signature? If the traffic type is identifiable by looking at an encrypted stream that is a sign of poor encryption? Isn't the point of encryption to look like its is random data without distinguishable patterns which can lead to "decrypting" without the key?

I can understand if they shape by port or even destination but that maybe a bit sneaky?

Oh and tracert seem fine except for routing problems to certain sites which is still not fixed.
 
Bad latency on D3 (packet loss resulting in lag spikes), packet loss to google AND local destinations, Zertop showing slow local and international transfers despite account being unshaped according to clientzone...
I guess it could be my exchange - it's not overloaded though, 1st 3 hops are fine. So it points to transit somewhere being an issue?

Hard to tell - we'd need to run multiple tests to see a pattern.
 
Yes, but the question becomes if NNTP runs over SSL is just the data encrypted or the entire packet? How do they differentiate between say web SSL traffic and NNTP SSL traffic? According to Afrihost, SSL is not shaped

And also 75% should give me about 300kb/s

We should still be able to determine the packet signature whether it's SSL encrypted. Most of the info we need is probably in the headers and not in the data itself. Might need to speak to the more clever people, who are obviously very secretive for network security reasons. But I don't think SSL interferes with our shaping, though I can imagine the whole heartbleed thing has made a lot of traffic more SSL based that previously.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X