Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
What sort of account do you have? And what speeds are you seeing at the moment? Has there been any increase in latency on your connection as well?

It's a capped account, on 10mb line.

No increase in latency, 8ms ping to the exchange.

Getting about 110kb/S now from a multi-threaded HTTP download
 
I have the exact modem, and I kept getting those types of errors as well, setting the DNS to manual seems to correct it for me. The strange thing is that I have gone through a few - lightning killed four in a year in Centurion - and this happened on two of them, so I wonder if there is perhaps not something on the modem firmware that is unhappy with automatically pulling the DNS settings from us.

Well, well, done this, entered 196.7.7.7. and 196.7.8.9 as DNS and rebooted every pc in the house as well as the modem. Looking schweet so far - You might just have fixed it!

I would have tried my other modem, a Netgear DGN2200, but I've loaned it out for the week.

Thanks Afrigenie.
 
It's a capped account, on 10mb line.

No increase in latency, 8ms ping to the exchange.

Getting about 110kb/S now from a multi-threaded HTTP download

Are you able to run a speedtest at the moment? Would that affect your download at all?
 
I'm also on a D-link 2750U jobbie. Problem I have with this issue that it is intermittent and does not always happen. I can't imagine that it is entirely attributable to the modem.

Have alternated between assigned and static DNS servers. Not much of a change in stability.
 
I'm also on a D-link 2750U jobbie. Problem I have with this issue that it is intermittent and does not always happen. I can't imagine that it is entirely attributable to the modem.

Have alternated between assigned and static DNS servers. Not much of a change in stability.

Do you have the latest firmware?

Firmware 1.65 ?
 
I'm also on a D-link 2750U jobbie. Problem I have with this issue that it is intermittent and does not always happen. I can't imagine that it is entirely attributable to the modem.

Have alternated between assigned and static DNS servers. Not much of a change in stability.

It is probably a combination of the firmware of the modem and something on our end, it definitely doesn't affect all DSL-2750U's, as I have had at least two different DSL-2750U's that never had this issue occur.

Could you try use 196.7.7.7 and 8.8.8.8 and see if it makes any difference at all to the stability.
 
Performance started to degrade from around 19:30. Latest tracert:

Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 13 ms 13 ms 13 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 21 ms 12 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 16 ms 18 ms 18 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 26 ms 23 ms 21 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 * 11 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 211 ms 216 ms 243 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

8 192 ms 213 ms 216 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 214 ms 213 ms 214 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 201 ms 193 ms 202 ms 209.85.255.76
11 200 ms 213 ms 203 ms 66.249.95.9
12 197 ms 222 ms 193 ms 72.14.239.129
13 196 ms * 192 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.
 
Performance started to degrade from around 19:30. Latest tracert:

Tracing route to google.com [216.58.223.46]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 13 ms 13 ms 13 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 21 ms 12 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 16 ms 18 ms 18 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 26 ms 23 ms 21 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 * 11 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 211 ms 216 ms 243 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

8 192 ms 213 ms 216 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 214 ms 213 ms 214 ms google-peering-ls-pr-2.uk.mtnns.net [209.212.99.
13]
10 201 ms 193 ms 202 ms 209.85.255.76
11 200 ms 213 ms 203 ms 66.249.95.9
12 197 ms 222 ms 193 ms 72.14.239.129
13 196 ms * 192 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.

That traceroute seems okay, Google.com does route internationally. What sort of speeds are you getting at the moment?
 
Weird thing is speed test is fine. Is this tracert a little more informative?

Tracing route to netflix.com [107.20.177.34]
over a maximum of 30 hops:

1 6 ms 3 ms 1 ms DD-WRT [192.168.1.1]
2 10 ms 10 ms 11 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 20 ms 15 ms 18 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 16 ms 17 ms 15 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 26 ms 19 ms 18 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 38 ms 20 ms 20 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 213 ms 218 ms 235 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 193 ms 200 ms 216 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 202 ms 201 ms 199 ms 195.50.122.181
10 * 283 ms * ae-3-80.edge2.Washington1.Level3.net [4.69.149.1
42]
11 * * * Request timed out.
12 341 ms 274 ms 339 ms AMAZON.COM.edge2.Washington1.Level3.net [4.79.22
.74]
13 288 ms 288 ms 292 ms 72.21.220.157
14 275 ms 277 ms 274 ms 205.251.245.232
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 270 ms 271 ms 277 ms 216.182.224.83
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
 
It is probably a combination of the firmware of the modem and something on our end, it definitely doesn't affect all DSL-2750U's, as I have had at least two different DSL-2750U's that never had this issue occur.

Could you try use 196.7.7.7 and 8.8.8.8 and see if it makes any difference at all to the stability.

Model Name: DSL-2750U
Firmware Version: AF_1.69_T10

I was using that exact combination when the issues started. Have gone auto and didn't help much. I'll try again tomorrow and see if it works better, Telkom internet is garbage in the evenings...
 
Weird thing is speed test is fine. Is this tracert a little more informative?

Tracing route to netflix.com [107.20.177.34]
over a maximum of 30 hops:

1 6 ms 3 ms 1 ms DD-WRT [192.168.1.1]
2 10 ms 10 ms 11 ms 105-236-4-65-esr-lo.mtnbusiness.co.za [105.236.4
.65]
3 20 ms 15 ms 18 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 16 ms 17 ms 15 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 26 ms 19 ms 18 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 38 ms 20 ms 20 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 213 ms 218 ms 235 ms ls-cr-2.uk--rb-cr-1.za-g.mtnns.net [196.44.31.11
4]
8 193 ms 200 ms 216 ms ls-pr-2.uk--ls-cr-2.uk-a.mtn.net [209.212.111.18
7]
9 202 ms 201 ms 199 ms 195.50.122.181
10 * 283 ms * ae-3-80.edge2.Washington1.Level3.net [4.69.149.1
42]
11 * * * Request timed out.
12 341 ms 274 ms 339 ms AMAZON.COM.edge2.Washington1.Level3.net [4.79.22
.74]
13 288 ms 288 ms 292 ms 72.21.220.157
14 275 ms 277 ms 274 ms 205.251.245.232
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 270 ms 271 ms 277 ms 216.182.224.83
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.

Even those traceroutes appear fine, Netflix should be routing to the US. Which DNS tool are you using to get your connection to Netflix?
 
There has to be a problem with torrents this evening. Tried 15 different torrent, all highly seeded but none will go over 70kbps on my 4mb capped account. Speed test is 100% fine.
Pretty sure that torrents are being shaped or something is very wrong on AH side.
 
There has to be a problem with torrents this evening. Tried 15 different torrent, all highly seeded but none will go over 70kbps on my 4mb capped account. Speed test is 100% fine.
Pretty sure that torrents are being shaped or something is very wrong on AH side.
Queue standard AH response...
 
Tested a torrent on Web Africa account. Flying. . .
Tested on AH, crap.
 
Jip AF must be borked again.

I tried a few torrents mostly linux distros well seeeded usually get 4.2Mb/s

Struggling on 88Kb/s

So I suspect something on AF side probably
 
There has to be a problem with torrents this evening. Tried 15 different torrent, all highly seeded but none will go over 70kbps on my 4mb capped account. Speed test is 100% fine.
Pretty sure that torrents are being shaped or something is very wrong on AH side.

I'm not aware of a general problem. I ran some torrents yesterday evening (in the North) and was getting about 1.5MB/s on a 20Mbps line (capped account).

Are you in the South. North or East?
 
Thanks Afrihost - poor again on News server. HEAVY shaping/Throttling tonight. IPC South

So not only Torrents.

I haven't tested NNTP, but I can ask AfriGuy what he's seeing. Are you using our server? I see you're in the South so we'll test in that region for you.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X