Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Hmmm

Packet loss and decreased throughput on Afrihost accounts again...

This still the same ongoing issue to do with Southern contention and load shedding?

Shouldn't be higher than normal contention, IPC throughput looks good a the moment. Are you seeing the same packet loss issues to services that Henri18 reported above?
 
That is a Joke right?

Tracert cant even find your own server and you can't see anything wrong?

No wonder this network is going from bad to worse.

Telkom at least finds you in 18 hops but latency goes up by an order of magnitude after hop 8:
8 10 ms 9 ms 9 ms 196.43.25.206
9 133 ms 73 ms 102 ms mtn-gw.telkom-ipnet.co.za [196.25.165.198]

ICMP timeouts/ rejections don't always indicate an issue, hence the request for PM :)
 
Shouldn't be higher than normal contention, IPC throughput looks good a the moment. Are you seeing the same packet loss issues to services that Henri18 reported above?

I cannot comment on Henri18's issues... but on my Afrihost accounts most downloads seem limited to sub 50kbs, and fine on other ISP accounts.

I am torrenting at the moment at full speed with streaming audio and skype active while browsing on an IS capped account and it is all working.

torrent.jpg

On my Afrihost capped accounts, same torrent is limited to 18kbs, audio stream buffers and skype calls are a no-go.
 
Having issues, websites loading really slow, some playing Smite in the house are randomly teleporting around as well.
My ping is excellent though at ~180ms in-game. But tracerts:

Code:
ping vienna.at -t

Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=191ms TTL=47
Reply from 194.183.128.94: bytes=32 time=190ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=1055ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=486ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=190ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=688ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=192ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47

Ping statistics for 194.183.128.94:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 185ms, Maximum = 1055ms, Average = 263ms
 
I cannot comment on Henri18's issues... but on my Afrihost accounts most downloads seem limited to sub 50kbs, and fine on other ISP accounts.

I am torrenting at the moment at full speed with streaming audio and skype active while browsing on an IS capped account and it is all working.

View attachment 217196

On my Afrihost capped accounts, same torrent is limited to 18kbs, audio stream buffers and skype calls are a no-go.

That's very weird :(
I've run some tests on everything mentioned above, except Skype and it seems all good on our end.
 
Having issues, websites loading really slow, some playing Smite in the house are randomly teleporting around as well.
My ping is excellent though at ~180ms in-game. But tracerts:

Code:
ping vienna.at -t

Pinging vienna.at [194.183.128.94] with 32 bytes of data:
Reply from 194.183.128.94: bytes=32 time=191ms TTL=47
Reply from 194.183.128.94: bytes=32 time=190ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=1055ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=486ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=190ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=185ms TTL=47
Reply from 194.183.128.94: bytes=32 time=688ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=186ms TTL=47
Reply from 194.183.128.94: bytes=32 time=192ms TTL=47
Reply from 194.183.128.94: bytes=32 time=189ms TTL=47

Ping statistics for 194.183.128.94:
    Packets: Sent = 22, Received = 22, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 185ms, Maximum = 1055ms, Average = 263ms

Sorry to hear about the issues :(
Have you tried switching your DNS servers around to see if that helps at all?
 
Sorry to hear about the issues :(
Have you tried switching your DNS servers around to see if that helps at all?

It seems good again.
The issue with changing DNS servers is that I would have to use my old router, using the newer Telkom Pace due to the faster Wi-Fi.
 
It seems good again.
The issue with changing DNS servers is that I would have to use my old router, using the newer Telkom Pace due to the faster Wi-Fi.

Shouldn't the option to change DNS servers be fairly easy though?
 
That's very weird :(
I've run some tests on everything mentioned above, except Skype and it seems all good on our end.

Thanks... will try again on Afrihost tomorrow and see if it persists.

EDIT:

Just switched back now and giving Afrihost accounts a try... still the same;

torrentAH.jpg

Streaming now cannot even connect and Skype is a text only service on these accounts.
 
Last edited:
Thanks... will try again on Afrihost tomorrow and see if it persists.

EDIT:

Just switched back now and giving Afrihost accounts a try... still the same;

View attachment 217226

Streaming now cannot even connect and Skype is a text only service on these accounts.

:(
Sounds like your whole experience is a bit wonky. Apart from torrents, are HTTP downloads and your throughput in general, also slow?
 
Not great :( Didn't see any trending issues last night, would you be able to grab some tests if you see similar issues this evening? AfriGenie will be around until 8pm or so this evening.

Right now this is what im looking at:

Zb2uGP3.png


Tracert to the server:

r4dvR5i.png


Ideas?
 
So i have noticed over the past few days that browsing skysports is an issue. Landing page opens really slowly and any other pages that have articles take ages or dont load at all. Cleared my browsing data, cache etc, and then tried again. Tried opening the transfer news section and eventually get the err_connection_reset.



Speedtest result above and below is tracert local and then to Skysports.com

C:\Users\Brendan.WEALTH>tracert www.afrihost.co.za

Tracing route to www.afrihost.co.za [41.76.227.137]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 * 13 ms 12 ms 41.181.51.181
4 * * * Request timed out.
5 13 ms 10 ms 13 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 13 ms 10 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 10 ms 11 ms 23 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 11 ms 14 ms 15 ms 196.44.0.74
9 11 ms 21 ms 14 ms vox.cinx.net.za [196.223.22.21]
10 36 ms 45 ms 61 ms 41.193.120.14
11 35 ms 32 ms 84 ms 41.193.120.1
12 * * * Request timed out.
13 * 41 ms 79 ms 41.193.106.97
14 33 ms 35 ms 53 ms 41.193.106.101
15 32 ms * * 41.193.32.134
16 33 ms 33 ms 32 ms 41.76.224.8
17 32 ms 32 ms 31 ms 41.76.224.96
18 31 ms 35 ms 34 ms 41.76.227.137

Trace complete.

Then to Skysports:
C:\Users\Brendan.WEALTH>tracert www.skysports.com

Tracing route to www.skysports.com.c.footprint.net [197.80.129.125]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 * 11 ms 11 ms 41.181.53.149
4 11 ms 11 ms 11 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 * 12 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 10 ms 11 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 * 11 ms 10 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 11 ms 10 ms 10 ms 196.44.0.74
9 23 ms 21 ms 20 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.14
1]
10 22 ms 23 ms 27 ms tengig-0-2-1-0-101-cpt-pe-12.mweb.co.za [197.84.
7.12]
11 44 ms 35 ms 34 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
12 35 ms 38 ms 42 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]

13 33 ms 33 ms 37 ms tengig-0-0-0-0-101-vic-pe-1.mweb.co.za [197.80.7
.9]
14 38 ms 38 ms 36 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

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.

Trace complete.
 
Right now this is what im looking at:

Zb2uGP3.png


Tracert to the server:

r4dvR5i.png


Ideas?

Looks to me like you're connecting from the South. My reports don't show latency from our network in general at that time, but it seems like there is intermittent latency when you hit our network (not terrible but raises a flag for me) and then also when you reach optinet's network. Because I can't see the 2nd hop on the trace, it;s hard to say whether this latency exists before the ISP network. But definitely not seeing packet loss in general like this on any network (even during peak demand).

Are you only seeing this on connecting to this specific IP/server?
 
So i have noticed over the past few days that browsing skysports is an issue. Landing page opens really slowly and any other pages that have articles take ages or dont load at all. Cleared my browsing data, cache etc, and then tried again. Tried opening the transfer news section and eventually get the err_connection_reset.



Speedtest result above and below is tracert local and then to Skysports.com

C:\Users\Brendan.WEALTH>tracert www.afrihost.co.za

Tracing route to www.afrihost.co.za [41.76.227.137]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 10.0.0.2
2 * * * Request timed out.
3 * 13 ms 12 ms 41.181.51.181
4 * * * Request timed out.
5 13 ms 10 ms 13 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 13 ms 10 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 10 ms 11 ms 23 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 11 ms 14 ms 15 ms 196.44.0.74
9 11 ms 21 ms 14 ms vox.cinx.net.za [196.223.22.21]
10 36 ms 45 ms 61 ms 41.193.120.14
11 35 ms 32 ms 84 ms 41.193.120.1
12 * * * Request timed out.
13 * 41 ms 79 ms 41.193.106.97
14 33 ms 35 ms 53 ms 41.193.106.101
15 32 ms * * 41.193.32.134
16 33 ms 33 ms 32 ms 41.76.224.8
17 32 ms 32 ms 31 ms 41.76.224.96
18 31 ms 35 ms 34 ms 41.76.227.137

Trace complete.

Then to Skysports:
C:\Users\Brendan.WEALTH>tracert www.skysports.com

Tracing route to www.skysports.com.c.footprint.net [197.80.129.125]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 10.0.0.2
2 * * * Request timed out.
3 * 11 ms 11 ms 41.181.53.149
4 11 ms 11 ms 11 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150
]
5 * 12 ms 10 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 10 ms 11 ms 11 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 * 11 ms 10 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

8 11 ms 10 ms 10 ms 196.44.0.74
9 23 ms 21 ms 20 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.14
1]
10 22 ms 23 ms 27 ms tengig-0-2-1-0-101-cpt-pe-12.mweb.co.za [197.84.
7.12]
11 44 ms 35 ms 34 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
12 35 ms 38 ms 42 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]

13 33 ms 33 ms 37 ms tengig-0-0-0-0-101-vic-pe-1.mweb.co.za [197.80.7
.9]
14 38 ms 38 ms 36 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

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.

Trace complete.

These tests seem a little all over the place. Definitely concerned by the timeouts in both traces. Curious why skysports routes via optinet though. I'm guessing it's a caching thing with DsTV.
 
Hi AH. Tried updating the firmware on my sony z2 - download sat at 20 KB/s. Switched to an mweb account - 420 KB/s. Wtf?!?!
 
Just thought I'd chip in from my side - after struggling for a few weeks now..

Symptoms similar to everybody (i just scanned the first and last few pages of this 50+ page thread)

Inconsistent speed - at almost exactly 17:00 throttling kicks in at a grand scale - streaming/p2p/most international sites unusable - can't open gmail - and downloads hover around 3Kb/s-23Kb/s - usually 380+ (very stable 4Mb adsl) Also got asked about traceroutes/dns changes blah blah - and then last night Finally the first honest response!

The support guy mentioned that they have been struggling with this for a while now - but that the results need to go " to the CEO to action anything" -in his words " they/management don't believe us when we say that there is a problem - they say "everything is fine" " - obviously another change/firmware upgrade was done to those "fancy kit that had issues with firmware a few month ago" -

The problem is if effects ALL account types : capped and uncapped - and it's random.

During the problem hours - yesterday from 17:00 -and by 23:00 it was fine again - tried a test account from Crystalweb - everything ran 100%.

Difference on the surface is the one is on the IS backbone, and the other on MTN.

I think it's time the AH management started to take their customers seriously and go back to when something was changed and roll it back.

my 2 cents...

Will be cancelling and try another ISP for few months.
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X