Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
My trace route:

Warning: afrihost.com has multiple addresses; using 104.20.31.244
traceroute to afrihost.com (104.20.31.244) , 5 relative hops max, 52 byte packets
1 myrouter.home (192.168.1.1) 1.645 ms 18.167 ms 21.181 ms
2 * * *
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 22.815 ms 89.637 ms 92.690 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 23.320 ms 397.587 ms 404.774 ms
5 41.162.84.192 (41.162.84.192) 21.894 ms 62.143 ms 66.354 ms
6 172.18.1.162 (172.18.1.162) 29.910 ms 59.752 ms 62.267 ms
7 196.46.25.198 (196.46.25.198) 437.759 ms 4481.292 ms 4484.748 ms
8 104.20.31.244 (104.20.31.244) 354.442 ms 740.965 ms 743.328 ms
 
Still this rubbish in KZN. Everything was fine last night, what's changed? And why is it taking so long to rectify?

Tracing route to [69.171.230.68]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 12 ms 12 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 12 ms 11 ms 10 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 16 ms 15 ms 15 ms 41.162.84.192
6 20 ms 20 ms 21 ms 172.18.1.162
7 196 ms 213 ms 202 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
8 324 ms 331 ms 349 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
9 364 ms 356 ms 336 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
10 344 ms 322 ms 333 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
11 357 ms 352 ms 368 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
12 329 ms 335 ms 343 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
13 365 ms 354 ms 341 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
14 355 ms 364 ms 357 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
15 321 ms 350 ms 345 ms 80.231.62.2
16 357 ms 321 ms 299 ms ae11.mpr2.lhr2.uk.zip.zayo.com [64.125.30.52]
17 424 ms 435 ms 407 ms ae27.cs1.lhr11.uk.eth.zayo.com [64.125.30.236]
18 423 ms 450 ms 428 ms ae5.cs1.lga5.us.eth.zayo.com [64.125.29.126]
19 389 ms 388 ms 408 ms ae27.cr1.lga5.us.zip.zayo.com [64.125.30.251]
20 418 ms 410 ms 369 ms ae2.er3.lga5.us.zip.zayo.com [64.125.31.214]
21 414 ms 412 ms 421 ms 128.177.165.234.IPYX-100687-870-ZYO.zip.zayo.com [128.177.165.234]
22 431 ms 433 ms 454 ms be2.bb02.lga1.tfbnw.net [157.240.32.44]
23 438 ms 419 ms 406 ms be17.bb02.dca1.tfbnw.net [31.13.28.90]
24 449 ms 456 ms 494 ms be24.bb02.prn2.tfbnw.net [74.119.79.99]
25 570 ms 486 ms 474 ms ae1.dr12.prn1.tfbnw.net [31.13.28.25]
 
Sadly, I'm also not having a pleasant experience this evening...

My trace route:

traceroute to afrihost.com (104.20.31.244) , 5 relative hops max, 52 byte packets
1 myrouter.home (192.168.1.1) 2.177 ms 16.825 ms 20.010 ms
2 * * *
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 57.811 ms 155.831 ms 158.539 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 20.548 ms 88.960 ms 92.774 ms
5 41.162.84.192 (41.162.84.192) 25.229 ms 58.158 ms 60.229 ms
6 172.18.1.162 (172.18.1.162) 33.289 ms 59.353 ms 62.034 ms
7 196.46.25.198 (196.46.25.198) 364.876 ms 4857.407 ms 4861.948 ms
8 104.20.31.244 (104.20.31.244) 367.504 ms 744.565 ms 746.996 ms
 
It's probably a repeat of a year ago (or was it 2 years, happened so much, cant keep track of it), where they blamed Telkom for not providing what they need on time.. which they copy/pasted for nearly a year to all the clients complaining about slow interwebs/latency/streaming.

Time to jump ship again before the excuses come flooding in
 
moedawood said:
Sadly, I'm also not having a pleasant experience this evening...

My trace route:

traceroute to afrihost.com (104.20.31.244) , 5 relative hops max, 52 byte packets
1 myrouter.home (192.168.1.1) 2.177 ms 16.825 ms 20.010 ms
2 * * *
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 57.811 ms 155.831 ms 158.539 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 20.548 ms 88.960 ms 92.774 ms
5 41.162.84.192 (41.162.84.192) 25.229 ms 58.158 ms 60.229 ms
6 172.18.1.162 (172.18.1.162) 33.289 ms 59.353 ms 62.034 ms
7 196.46.25.198 (196.46.25.198) 364.876 ms 4857.407 ms 4861.948 ms
8 104.20.31.244 (104.20.31.244) 367.504 ms 744.565 ms 746.996 ms
Click to expand...

This looks like a line fault causing havoc with the router.
 
moedawood said:
Sadly, I'm also not having a pleasant experience this evening...

My trace route:

traceroute to afrihost.com (104.20.31.244) , 5 relative hops max, 52 byte packets
1 myrouter.home (192.168.1.1) 2.177 ms 16.825 ms 20.010 ms
2 * * *
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 57.811 ms 155.831 ms 158.539 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 20.548 ms 88.960 ms 92.774 ms
5 41.162.84.192 (41.162.84.192) 25.229 ms 58.158 ms 60.229 ms
6 172.18.1.162 (172.18.1.162) 33.289 ms 59.353 ms 62.034 ms
7 196.46.25.198 (196.46.25.198) 364.876 ms 4857.407 ms 4861.948 ms
8 104.20.31.244 (104.20.31.244) 367.504 ms 744.565 ms 746.996 ms
Click to expand...

Try using a LAN cable to rule out the WiFi. I had an issue with my WiFi as well, the neighbors installed a new network that destroyed mine in the evenings (wireless signals propagate further at night). Install something like SSID as well to check for signal overlap on your laptop, else Wireless Analyzer on a phone (if the LAN cable fixes the issue).
 
Still going on in KZN cant jam on any eu servers as the klt cape town link is causing high pings



C:\Users\BLA>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.90]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 24 ms 22 ms 22 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 23 ms 22 ms 22 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 22 ms 22 ms 22 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 22 ms 22 ms 23 ms 41.162.84.192
7 31 ms 30 ms 31 ms 172.18.1.162
8 188 ms 192 ms 192 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 356 ms 362 ms 354 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 369 ms 378 ms 382 ms if-ae-5-90.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
11 315 ms 314 ms 330 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 358 ms 387 ms 372 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 306 ms 316 ms 355 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
14 364 ms 366 ms 346 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
15 392 ms 368 ms 360 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
16 371 ms 325 ms 290 ms 195.219.83.102
17 * * * Request timed out.
18 352 ms 348 ms 363 ms unknown.Level3.net [212.187.139.230]
19 * * * Request timed out.
20 * * * Request timed out.
21 367 ms 359 ms 363 ms ae0.er02.cwwtf.bbc.co.uk [132.185.254.90]
22 339 ms * 356 ms 132.185.255.165
23 366 ms 363 ms 371 ms bbc-vip011.cwwtf.bbc.co.uk [212.58.246.90]

Trace complete.




C:\Users\BLA>tracert www.battle.net

Tracing route to www.battle.net [24.105.29.30]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 23 ms 21 ms 21 ms dbn-up1.ip.adsl.co.za [169.1.5.161]
4 23 ms 22 ms 22 ms dbn-up2.ip.adsl.co.za [169.1.5.162]
5 22 ms 22 ms 22 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
6 22 ms 22 ms 21 ms 41.162.84.192
7 31 ms 30 ms 31 ms 172.18.1.162
8 167 ms 163 ms 157 ms if-ae-7-0.tcore1.JSO-Johannesburg.as6453.net [41.206.178.29]
9 421 ms 394 ms 387 ms if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
10 419 ms 414 ms 422 ms if-ae-5-40.tcore2.PV9-Lisbon.as6453.net [80.231.159.89]
11 398 ms 402 ms * if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
12 410 ms 421 ms 428 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
13 376 ms 376 ms 409 ms if-ae-6-2.thar1.NJY-Newark.as6453.net [80.231.138.18]
14 * 405 ms * if-ae-1-3.thar2.NJY-Newark.as6453.net [216.6.57.2]
15 417 ms 427 ms 388 ms if-ae-14-15.tcore2.NTO-New-York.as6453.net [66.198.111.9]
16 440 ms 427 ms 405 ms if-ae-12-2.tcore1.N75-New-York.as6453.net [66.110.96.5]
17 442 ms 431 ms 413 ms 66.110.96.146
18 414 ms 424 ms 450 ms hu-1-3-0-8-cr02.newyork.ny.ibone.comcast.net [68.86.84.241]
19 356 ms 385 ms 402 ms be-33-pe01.60hudson.ny.ibone.comcast.net [68.86.84.78]
20 * as30036.350ecermak.il.ibone.comcast.net [173.167.57.150] reports: Destination net unreachable.

Trace complete.
 
Last edited:
Things are also pretty bad here in Durban.... I thought problem was on my end but looks like AH messed up somewhere
Streaming is basically dead unless you wait 30min to buffer..
 
WTH?! Videos are not loading at all at the moment. Are the engineers on to fixing this issue or what? C'mon already.
 
Yeah ive been fighting with AH for almost a month now about this its only us KZN okes that seem to have this problem, its that one Cape Town link thats doing it and it routes all our traffic out internationally so yeah videos from int sites games on EU servers all no good locally its fine but not out internationally. Dont know why we have to even use a Cape Town point i thought there was one here in Durb
 
Last edited:
International latency is very erratic ATM, KZN. When will it be fixed? We heard the whole of last week 'they are working on it'.
Edit: even myBB taking a while to open.
 
Every night for a week so far here in KZN. Afrihost are you oversold? Do you have the necessary capacity to handle us? Why is KZN given such crappy service. C'mon we have been moaning and groaning every night on here. And the reply is - send tracert's, oh, so sorry, our engineers and NOC team is working on it.

What is the good news that Gian is going to give us? That you are glad to announce that you have bought more capacity to be viable again in 6 months (when the capacity goes live and that we must just again must "hang" in there). @Afriguy does not even respond anymore to requests asking if there is feedback.

Since day 1 of me being on ADSL i have been with Afrihost, through the bumpy times, through capacity issues, through the switch to MTN, to Afrigreen. All that I ask is please be transparent with what issues you sit with that we can make our plans and work around it.

This is not on...
 
High latency AGAIN. I already downgraded the account at the end of last month because i couldn't use it properly. Its fast approaching the time i cancel all together. Either Afrihost hasn't a clue what the problem is and are fumbling in the dark or they have capacity problems.
 
Just tried webafrica account and streaming is great..........AH sucks...over 1 week and every evening same crap....
 
And my AH has gone for a ball of sh¡t

Come on afrihost!
East London. Put mweb details in and no problem!

Can't game, wife can't even stream youtube atm!!
 
Hi AFRIHOST and AFRIGUY!
It is still the same problem - slow steaming with full speed speedtests !
There on the forum is another tread with the same issues - http://mybroadband.co.za/vb/showthread.php/839398-Afrihost-streaming-issues
You only bull*hit us and buying the time with the questions about ping and trace!
Everything is working fine with other ISP with the same line, hardware and software.
So this is the last chance to you to explain issue before you will lost me as client.
Now is your turn . . .
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X