Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
4422557552.png


20Mb line...

Not looking good here Afripeeps. :(
 
Latency here in Cape Town for me is slowly increasing, luckily I saw it before entering a rank match.




C:\Users\Henri>tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 * * * Request timed out.
3 117 ms 198 ms 73 ms 41.181.53.213
4 83 ms 80 ms 80 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 91 ms 64 ms 62 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 65 ms 61 ms 59 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 58 ms 60 ms 58 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

8 69 ms 67 ms 68 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
9 78 ms 76 ms 76 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
 
Henri18 said:
Latency here in Cape Town for me is slowly increasing, luckily I saw it before entering a rank match.




C:\Users\Henri>tracert www.afrihost.com

Tracing route to www.afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms home.gateway.home.gateway [192.168.1.254]
2 * * * Request timed out.
3 117 ms 198 ms 73 ms 41.181.53.213
4 83 ms 80 ms 80 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 91 ms 64 ms 62 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 65 ms 61 ms 59 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 58 ms 60 ms 58 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]

8 69 ms 67 ms 68 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.21
7]
9 78 ms 76 ms 76 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18
]

Trace complete.
Click to expand...

Would you mind testing your latency now and seeing if there is any change?
 
30% Packet on teamspeak cape town have to switch to WA to raid and game thx afrihost for never working
 
AfriGenie said:
Really?! Has that really made a big difference on your connection?
Click to expand...

I have a feeling that it is due to the "no shaping" network that it is causing such a big delay.

Will do a test with another ISP when I have some time.
 
ID_10_T said:
I have a feeling that it is due to the "no shaping" network that it is causing such a big delay.

Will do a test with another ISP when I have some time.
Click to expand...

If it the google photos syncing, it would be due to it uploading. Near destroys ADSL lines. One cannot download without upload.
 
AfriGenie said:
Our Team is already looking into the increased latency in the East, something is definitely off there, they should have things sorted out pronto!
Click to expand...

Thanks AfriGenie! all seems to be back to normal now..



traceroute to www.google.com (216.58.209.228), 30 hops max, 38 byte packets
1 * * *
2 41.181.221.217 (41.181.221.217) 18.290 ms 18.154 ms 17.921 ms
3 41.181.221.218 (41.181.221.218) 66.991 ms 17.900 ms 18.445 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 34.988 ms 18.389 ms 18.688 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 18.753 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 18.945 ms 18.937 ms
6 41.181.139.99 (41.181.139.99) 18.934 ms 41.181.139.109 (41.181.139.109) 18.437 ms 17.880 ms
7 72.14.194.74 (72.14.194.74) 24.721 ms 31.340 ms 26.716 ms
8 66.249.95.8 (66.249.95.8) 197.441 ms 201.364 ms 197.220 ms
9 216.239.51.7 (216.239.51.7) 197.492 ms 197.658 ms 197.889 ms
10 209.85.253.95 (209.85.253.95) 197.476 ms 198.196 ms 197.677 ms
11 209.85.250.171 (209.85.250.171) 197.212 ms 196.922 ms 196.941 ms
12 lhr08s05-in-f228.1e100.net (216.58.209.228) 196.672 ms 197.100 ms 196.866 ms

Thanks again for the help and quick response ;)
 
30% packetloss on teamspeak and cs:go servers tonight, no problems on other ISPs.
 
Prodegy said:
30% Packet on teamspeak cape town have to switch to WA to raid and game thx afrihost for never working
Click to expand...

We did see high latency over the course of the day yesterday, which the network team were working on. Things should be back to normal today but we'll only really know when major demand hits to see if our systems react they way they should to preserve latency.
 
ID_10_T said:
I have a feeling that it is due to the "no shaping" network that it is causing such a big delay.

Will do a test with another ISP when I have some time.
Click to expand...

If you are synching (as someone pointed out) then you are most likely maxxing your upload, which will cause latency on your local network. Particularly because ADSL is asymmetrical and you can't upload and download at the same time. If your upload is maxxed, you would get very little throughput on downloads.
 
kohlhtor said:
Hi latency tonight
Afrihost
View attachment 223922
telkom
View attachment 223924

22:20
Click to expand...

We are aware of the latency. We did manage to bring this under control around 5pm yesterday, but it did seem to spike again later in the evening. The network team are looking at this to see what caused the increase and to do what we can to prevent any latency going forward :(
 
tuneme said:
Thanks AfriGenie! all seems to be back to normal now..



traceroute to www.google.com (216.58.209.228), 30 hops max, 38 byte packets
1 * * *
2 41.181.221.217 (41.181.221.217) 18.290 ms 18.154 ms 17.921 ms
3 41.181.221.218 (41.181.221.218) 66.991 ms 17.900 ms 18.445 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 34.988 ms 18.389 ms 18.688 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 18.753 ms xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 18.945 ms 18.937 ms
6 41.181.139.99 (41.181.139.99) 18.934 ms 41.181.139.109 (41.181.139.109) 18.437 ms 17.880 ms
7 72.14.194.74 (72.14.194.74) 24.721 ms 31.340 ms 26.716 ms
8 66.249.95.8 (66.249.95.8) 197.441 ms 201.364 ms 197.220 ms
9 216.239.51.7 (216.239.51.7) 197.492 ms 197.658 ms 197.889 ms
10 209.85.253.95 (209.85.253.95) 197.476 ms 198.196 ms 197.677 ms
11 209.85.250.171 (209.85.250.171) 197.212 ms 196.922 ms 196.941 ms
12 lhr08s05-in-f228.1e100.net (216.58.209.228) 196.672 ms 197.100 ms 196.866 ms

Thanks again for the help and quick response ;)
Click to expand...


Glad to hear things are better! Will pass on your thanks to the Genie ;)
 
Nirv said:
30% packetloss on teamspeak and cs:go servers tonight, no problems on other ISPs.
Click to expand...

We do know that there was some latency on the network, so it may have affected teamspeak. This should have been gone from just before 11pm (especially in the South) so if you experienced latency after that, it's a bit weird. Do you know what port was used for TS?
 
AfriMan said:
If you are synching (as someone pointed out) then you are most likely maxxing your upload, which will cause latency on your local network. Particularly because ADSL is asymmetrical and you can't upload and download at the same time. If your upload is maxxed, you would get very little throughput on downloads.
Click to expand...

This is incorrect. The Asymmetrical in Asymmetrical Digital Subscriber Line refers to the fact that the upload and download speeds are different, so you get a 512Kb/s upload and a 4Mb/s download, ie. not symmetrical. A DSL (Digital Subscriber Line) has the same upload and download speed.

You have to be able to upload and download at the same time or else you would get ridiculous latency while waiting for packets to be verified, gaming wouldn't work, VOIP wouldn't work, Youtube would buffer forever.

I do however suspect that Afrihost's "advanced" system that allocates bandwidth to your account combines both upload and download speeds as determined by your account speed, so if you're paying for a 4Mb account, it allocates you 4Mb of bandwidth for both uploading and downloading, instead of 4Mb only for downloading and 512Kb only for uploading.
 
Scepter said:
This is incorrect. The Asymmetrical in Asymmetrical Digital Subscriber Line refers to the fact that the upload and download speeds are different, so you get a 512Kb/s upload and a 4Mb/s download, ie. not symmetrical. A DSL (Digital Subscriber Line) has the same upload and download speed.

You have to be able to upload and download at the same time or else you would get ridiculous latency while waiting for packets to be verified, gaming wouldn't work, VOIP wouldn't work, Youtube would buffer forever.

I do however suspect that Afrihost's "advanced" system that allocates bandwidth to your account combines both upload and download speeds as determined by your account speed, so if you're paying for a 4Mb account, it allocates you 4Mb of bandwidth for both uploading and downloading, instead of 4Mb only for downloading and 512Kb only for uploading.
Click to expand...

Both are correct, in a way, and Afriman used the wrong terminology, but the result is the same.

If your upload bandwidth is fully utilised, uploading a file, other web pages / protocols are unable to send an ACK, back to remote servers so, in turn, they will wait for that ACK or time out and no data will be sent. It will appear as if your downloads die as a result of upload bandwidth but in reality it dies because the handshake failed.

You can mitigate it with shaping locally, and limit upload bandwidth available to any one application, to prevent it using the full bandwidth. An upload manager or something like netlimiter should help if you do a lot of uploads.

Cheers
Chris
 
Last edited:
Scepter said:
This is incorrect. The Asymmetrical in Asymmetrical Digital Subscriber Line refers to the fact that the upload and download speeds are different, so you get a 512Kb/s upload and a 4Mb/s download, ie. not symmetrical. A DSL (Digital Subscriber Line) has the same upload and download speed.

You have to be able to upload and download at the same time or else you would get ridiculous latency while waiting for packets to be verified, gaming wouldn't work, VOIP wouldn't work, Youtube would buffer forever.

I do however suspect that Afrihost's "advanced" system that allocates bandwidth to your account combines both upload and download speeds as determined by your account speed, so if you're paying for a 4Mb account, it allocates you 4Mb of bandwidth for both uploading and downloading, instead of 4Mb only for downloading and 512Kb only for uploading.
Click to expand...

Just had a chat with AfriMan, he seems to have confused himself. :)

We're all on the same bandwagon now, the Asymmetrical component of ADSL refers to the prioritization of download speeds over upload speeds on an ADSL connection.

Up until your connection leaves the Exchange the basic up and down traffic will be handled by the Telkom system, and that treats all up and down traffic the same, so if you have a 4Mbps connection you will have 4Mbps download with 512Kbps upload completely separate with both being able to run at full speed without - in theory - interfering without the other.
 
AfriMan said:
We do know that there was some latency on the network, so it may have affected teamspeak. This should have been gone from just before 11pm (especially in the South) so if you experienced latency after that, it's a bit weird. Do you know what port was used for TS?
Click to expand...
By 11pm I had switched to a different account, so did not see if the latency still existed on my afrihost account. However it is rare for me to use the line after 11pm in the week so it is fairly useless for me to only have a usable line after 11pm. The teamspeak server was the MWEB Gamezone server, can't check the port right now but it's a popular server.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X