kohlhtor
Expert Member
Again iOS app download slow
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
So packet loss + terrible pings tonight again, LoL servers just lag and blizzard games I cant even connect to their servers, switched to web africa problem goes away and im playing again, I have been posting for almost 2 months now with this issue as well feels like nothing has changed and I keep having to buy cap from other ISP's.
Anyone else struggling to logon to D3 with Afrihost, past few nights been using WebAfrica just to play games, just tested my Axxess account, same problem, moved over to Webafrica insta login.
So packet loss + terrible pings tonight again, LoL servers just lag and blizzard games I cant even connect to their servers, switched to web africa problem goes away and im playing again, I have been posting for almost 2 months now with this issue as well feels like nothing has changed and I keep having to buy cap from other ISP's.
Anyone else struggling to logon to D3 with Afrihost, past few nights been using WebAfrica just to play games, just tested my Axxess account, same problem, moved over to Webafrica insta login.
Why are there always so many problems on the system? It's very seldom that all systems are running smoothly without someone complaining about something going wrong here. IPC an issue?? It's almost like you guys are trying to over manage the traffic flow which is going wrong due to lack of Capacity.
I'm not aware of problems on D3 but I'll check with the guys if there are issues.
Just out of interest, are you using PPPoE passthrough or changing accounts on the router?
The only rules wrt unshaped capped accounts should be to give everyone a fair slice and not manage on the protocol level right?
Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=104ms TTL=58
Reply from 197.242.144.102: bytes=32 time=166ms TTL=58
Reply from 197.242.144.102: bytes=32 time=156ms TTL=58
Reply from 197.242.144.102: bytes=32 time=120ms TTL=58
Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 166ms, Average = 136ms
Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=31ms TTL=54
Reply from 197.242.144.102: bytes=32 time=37ms TTL=54
Reply from 197.242.144.102: bytes=32 time=33ms TTL=54
Reply from 197.242.144.102: bytes=32 time=31ms TTL=54
Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 37ms, Average = 33ms
Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 176 ms 82 ms 100 ms 41.181.221.253
4 41 ms 41 ms 43 ms 41.181.221.254
5 170 ms 245 ms 130 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 123 ms 100 ms 87 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 134 ms 141 ms 133 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 181 ms 136 ms 259 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
9 117 ms 124 ms 101 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
10 54 ms 99 ms 105 ms 196.30.1.39
11 128 ms 204 ms 157 ms 196.31.220.23
12 141 ms 142 ms 79 ms 196.31.63.206
13 104 ms 124 ms 114 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 60 ms 82 ms 74 ms www.afrihost.co.za [197.242.144.102]
Trace complete.
Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 74 ms 104 ms 94 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 32 ms 13 ms 15 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 12 ms 13 ms 18 ms 196.35.115.136
6 28 ms 21 ms 27 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
7 17 ms 11 ms 15 ms 168.209.6.131
8 67 ms 39 ms 43 ms mtnns-2.cinx.net.za [196.223.22.31]
9 23 ms 23 ms 13 ms 196.44.0.75
10 36 ms 37 ms 36 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
11 38 ms 52 ms 60 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
12 92 ms 50 ms 46 ms 196.31.220.10
13 36 ms 53 ms 34 ms 196.31.220.21
14 32 ms 38 ms 31 ms 196.31.63.202
15 44 ms 36 ms 40 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
16 61 ms 65 ms 120 ms www.afrihost.co.za [197.242.144.102]
Trace complete.
I have 4 accounts on the router, just easier to disconnect like that & connect again. @Davedes I am well aware that Axxess in owned by Afrihost but you wont believe the amount of times it worked when Afrihost didnt.
The quickest & easiest way IMO to check if your line is screwed or if its your isp is to have multiple isp accounts, its so easy now with everyone offering you a free 1GB account. I have yet to have an issue that was related to telkom being at fault over my isp excluding the exchange being down, I just sometimes wonder why you then get asked to post stuff like traceroots, speedtests etc if an alternative account works.
Hi All
Ran a couple of tests on my 4MB AH Capped Account and compared it with my Web Africa account.
Afrihost Ping
Code:Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data: Reply from 197.242.144.102: bytes=32 time=104ms TTL=58 Reply from 197.242.144.102: bytes=32 time=166ms TTL=58 Reply from 197.242.144.102: bytes=32 time=156ms TTL=58 Reply from 197.242.144.102: bytes=32 time=120ms TTL=58 Ping statistics for 197.242.144.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 104ms, Maximum = 166ms, Average = 136ms
WA Ping
Code:Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data: Reply from 197.242.144.102: bytes=32 time=31ms TTL=54 Reply from 197.242.144.102: bytes=32 time=37ms TTL=54 Reply from 197.242.144.102: bytes=32 time=33ms TTL=54 Reply from 197.242.144.102: bytes=32 time=31ms TTL=54 Ping statistics for 197.242.144.102: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 37ms, Average = 33ms
Afrihost Trace Route
Code:Tracing route to www.afrihost.co.za [197.242.144.102] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 [B]176 ms 82 ms 100 ms[/B] 41.181.221.253 4 41 ms 41 ms 43 ms 41.181.221.254 5 170 ms 245 ms 130 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19 8.188] 6 123 ms 100 ms 87 ms compj-cpt-1.mtnns.net [196.44.18.2] 7 134 ms 141 ms 133 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134] 8 181 ms 136 ms 259 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69] 9 117 ms 124 ms 101 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22 1] 10 54 ms 99 ms 105 ms 196.30.1.39 11 128 ms 204 ms 157 ms 196.31.220.23 12 141 ms 142 ms 79 ms 196.31.63.206 13 104 ms 124 ms 114 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133] 14 60 ms 82 ms 74 ms www.afrihost.co.za [197.242.144.102] Trace complete.
WA Trace Route
Code:Tracing route to www.afrihost.co.za [197.242.144.102] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.0.0.2 2 * * * Request timed out. 3 [B]74 ms 104 ms 94 ms [/B] cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194 ] 4 32 ms 13 ms 15 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193] 5 12 ms 13 ms 18 ms 196.35.115.136 6 28 ms 21 ms 27 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1 3] 7 17 ms 11 ms 15 ms 168.209.6.131 8 67 ms 39 ms 43 ms mtnns-2.cinx.net.za [196.223.22.31] 9 23 ms 23 ms 13 ms 196.44.0.75 10 36 ms 37 ms 36 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69] 11 38 ms 52 ms 60 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22 1] 12 92 ms 50 ms 46 ms 196.31.220.10 13 36 ms 53 ms 34 ms 196.31.220.21 14 32 ms 38 ms 31 ms 196.31.63.202 15 44 ms 36 ms 40 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133] 16 61 ms 65 ms 120 ms www.afrihost.co.za [197.242.144.102] Trace complete.
Now, even with my limited knowledge on this subject, I'd say that there is something very wrong with my AH account, correct?