Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Gavin107 said:
Rock solid 4Mbps connection today, international sites fast, real time services working reliably. What a pleasure. What changed?
Click to expand...

We're just keeping a very close eye on the network today, hopefully we'll be able to keep things running this way. :)
 
electrofreeze said:
as you are throttling our speed at the moment we can see the packet loss slightly improving
why don't you just sort your capacity out so we all get what we pay for
Click to expand...

Why would AH do this? I told all my users to go from MWEB to AH, but I will never be able to do that again. AH just can't be trusted at the moment. Wait, correction: Can NEVER be trusted!
 
Francois Marais said:
Ag pork me over...
Again AH and slow speed. Gave up on my steam download.
So slow. Can understand why my clients left you!

http://www.speedtest.net/my-result/4274165381
http://www.speedtest.net/my-result/4274172608
Click to expand...

That's definitely not cool at all!

Especially that high latency on your local speedtest. Would you be able to run a traceroute to Afrihost.com and Google.com and post it here please? I need to get an idea as to where the latency is being introduced into your connection.
 
hmm...C:\Windows\system32>tracert afrihost.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 311 ms * 323 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 * 299 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 262 ms * * 196.30.1.39
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * ^C
Gave up at 12...

C:\Windows\system32>tracert google.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 339 ms 348 ms 345 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 316 ms 204 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 348 ms * rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * 269 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.

Hope that helps..
At least I have a iPad to use tonight. It seems that that will be the only connection tonight...
 
Last edited:
Francois Marais said:
hmm...C:\Windows\system32>tracert afrihost.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 311 ms * 323 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 * 299 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 262 ms * * 196.30.1.39
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * ^C
Gave u at 12...

C:\Windows\system32>tracert google.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 339 ms 348 ms 345 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 316 ms 204 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 348 ms * rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * 269 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.

Hope that helps..
At least I have a iPad to use tonight. It seems that that will be the only connection tonight...
Click to expand...

That first hop is crazy high. You have exchange issues bud. How do other ISP's perform on your line?
 
Francois Marais said:
hmm...C:\Windows\system32>tracert afrihost.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 311 ms * 323 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 * 299 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 262 ms * * 196.30.1.39
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * ^C
Gave up at 12...

C:\Windows\system32>tracert google.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 339 ms 348 ms 345 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 316 ms 204 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 348 ms * rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * 269 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.

Hope that helps..
At least I have a iPad to use tonight. It seems that that will be the only connection tonight...
Click to expand...

Sheesh, that definitely looks like an unhappy ADSL line or Exchange. How long have you been getting those types of latencies? Did the Port Recreate that I did help at all?
 
Will check. Just have something else keeping me busy.
Started this weekend if I am not wrong. Saw that the line was a bit slow on Monday. Did not notice last night. Was waiting for Windows Updates, so will check tonight. Thanks for the help.
 
Francois Marais said:
Will check. Just have something else keeping me busy.
Started this weekend if I am not wrong. Saw that the line was a bit slow on Monday. Did not notice last night. Was waiting for Windows Updates, so will check tonight. Thanks for the help.
Click to expand...

No problem! Please let me know once you've been able to test.
 
Francois Marais said:
hmm...C:\Windows\system32>tracert afrihost.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 311 ms * 323 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 * 299 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 262 ms * * 196.30.1.39
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * ^C
Gave up at 12...

C:\Windows\system32>tracert google.com

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

1 2 ms 1 ms 1 ms 192.168.0.1
2 339 ms 348 ms 345 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 * * * Request timed out.
4 316 ms 204 ms * rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 348 ms * rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * 269 ms jnb01s08-in-f14.1e100.net [216.58.223.46]

Trace complete.

Hope that helps..
At least I have a iPad to use tonight. It seems that that will be the only connection tonight...
Click to expand...

Bryn said:
That first hop is crazy high. You have exchange issues bud. How do other ISP's perform on your line?
Click to expand...

AfriGenie said:
Sheesh, that definitely looks like an unhappy ADSL line or Exchange. How long have you been getting those types of latencies? Did the Port Recreate that I did help at all?
Click to expand...

I hope for your sake it isn't your exchange.

Have a fault with my exchange since 11 February and diddley-squat has been done.
Every query with Telkom is met with "we will escalate it to the relevant department and someone will be in contact shortly", which of course never happens.
Telkom has admitted to Critical Care at AH that the problem is linked to a fault at the exchange causing congestion at peak times and that there is no ETR.
Critical Care even asked if my line could be put on a different exchange and was told that both exchanges in my area area congested.
Out of interest, a friend of mine phoned asking if he could get an adsl line in my area - and guess what - of course he can.
Ridiculous.
 
AfriGenie said:
No problem! Please let me know once you've been able to test.
Click to expand...

First TR on AH, 2nd one on Axxess:

tracert google.co.za

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

1 2 ms 2 ms 2 ms 192.168.0.1
2 342 ms 373 ms 354 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.
3.193]
3 * 230 ms 265 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 210 ms 137 ms 215 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 * * * Request timed out.
6 * 391 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 262 ms 246 ms 220 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94
]
8 371 ms 365 ms 383 ms 41.181.139.109
9 * 400 ms 430 ms 72.14.194.74
10 368 ms 410 ms 375 ms 72.14.239.129
11 380 ms 350 ms 328 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\François Marais>tracert google.co.za

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

1 2 ms 2 ms 2 ms 192.168.0.1
2 409 ms 339 ms 279 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.
3.193]
3 326 ms 361 ms 398 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 339 ms 325 ms 292 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 343 ms 354 ms 347 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 411 ms 411 ms 278 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 248 ms 331 ms 353 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 338 ms 322 ms 305 ms 41.181.139.99
9 241 ms 170 ms 207 ms 72.14.194.74
10 387 ms 348 ms 359 ms 72.14.239.129
11 313 ms * 285 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
 
Dianysis said:
I hope for your sake it isn't your exchange.

Have a fault with my exchange since 11 February and diddley-squat has been done.
Every query with Telkom is met with "we will escalate it to the relevant department and someone will be in contact shortly", which of course never happens.
Telkom has admitted to Critical Care at AH that the problem is linked to a fault at the exchange causing congestion at peak times and that there is no ETR.
Critical Care even asked if my line could be put on a different exchange and was told that both exchanges in my area area congested.
Out of interest, a friend of mine phoned asking if he could get an adsl line in my area - and guess what - of course he can.
Ridiculous.
Click to expand...

:(

Sadly, your story is not unique at all! Telkom is all too-happy to connect new ADSL accounts, but they once it comes to adequately upgrading and expanding Exchanges, the timeline is very vague quite often much longer than expected.
 
Francois Marais said:
First TR on AH, 2nd one on Axxess:

tracert google.co.za

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

1 2 ms 2 ms 2 ms 192.168.0.1
2 342 ms 373 ms 354 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.
3.193]
3 * 230 ms 265 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 210 ms 137 ms 215 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 * * * Request timed out.
6 * 391 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 262 ms 246 ms 220 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net [196.44.31.94
]
8 371 ms 365 ms 383 ms 41.181.139.109
9 * 400 ms 430 ms 72.14.194.74
10 368 ms 410 ms 375 ms 72.14.239.129
11 380 ms 350 ms 328 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

C:\Users\François Marais>tracert google.co.za

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

1 2 ms 2 ms 2 ms 192.168.0.1
2 409 ms 339 ms 279 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.
3.193]
3 326 ms 361 ms 398 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 339 ms 325 ms 292 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 343 ms 354 ms 347 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 411 ms 411 ms 278 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 248 ms 331 ms 353 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 338 ms 322 ms 305 ms 41.181.139.99
9 241 ms 170 ms 207 ms 72.14.194.74
10 387 ms 348 ms 359 ms 72.14.239.129
11 313 ms * 285 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
Click to expand...

I've sent you a PM, but in short I've logged a fault with Telkom, it does look like there have been quite a few issues at your Exchange recently.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X