Afrihost regular poor ping to local servers

whatever_sa

Well-Known Member
Joined
Feb 3, 2015
Messages
230
Reaction score
7
It seems afrihost does not even realize that every few days they have poor ping to local servers.

I just did a comparative test:

Afrihost: 157ms
Mweb : 8ms

I have only been with them a month and man, they just dont understand that web browser cookies have nothing to do with latency. I have sent them so much info (pings and trace routes to multiple servers), but i am sure at some point restarting my router repeatedly will fix their network.
 
I am on capped. They dont have poor ping all the time, it just happens every couple of days - sometimes it lasts an entire evening.
 
It seems afrihost does not even realize that every few days they have poor ping to local servers.

I just did a comparative test:

Afrihost: 157ms
Mweb : 8ms

I have only been with them a month and man, they just dont understand that web browser cookies have nothing to do with latency. I have sent them so much info (pings and trace routes to multiple servers), but i am sure at some point restarting my router repeatedly will fix their network.

Could you maybe post an MTR to the same server at the same time with both the accounts when the issue happens?
 
I do notice that pings to local server are greater on Afrihost than IS based ISP's.

For instance, I get 50ms on local and IS based could be 15-30ms.

It just the MTN network, it wont change. Overseas servers same thing, IS = 180-200ms - MTN = 250-300ms


This as always been the case, since the MTN move years ago
 
I do notice that pings to local server are greater on Afrihost than IS based ISP's.

For instance, I get 50ms on local and IS based could be 15-30ms.

It just the MTN network, it wont change. Overseas servers same thing, IS = 180-200ms - MTN = 250-300ms


This as always been the case, since the MTN move years ago

Where are you located? Durban?
The MTN backbone ISPs (Afrihost/Axxess) providers use the international line that lands in Cape Town, while IS uses the line that lands in Durban (most of the time, it also depends on the ISP routing).
 
FYI - here are pings and trace routes that i did when afrihost had latency again on 30 April. On that day, it was only around 100ms, and not over 200ms like other occurrences.

At the time of this test, mweb had about 8 to 12ms ping to local servers.

ping www.afrihost.co.za

Pinging www.afrihost.co.za [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=123ms TTL=58
Reply from 197.242.144.102: bytes=32 time=134ms TTL=58
Reply from 197.242.144.102: bytes=32 time=136ms TTL=58
Reply from 197.242.144.102: bytes=32 time=129ms 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 = 123ms, Maximum = 136ms, Average = 130ms


ping www.news24.co.za

Pinging x.24.com [41.86.110.143] with 32 bytes of data:
Reply from 41.86.110.143: bytes=32 time=81ms TTL=240
Reply from 41.86.110.143: bytes=32 time=92ms TTL=240
Reply from 41.86.110.143: bytes=32 time=104ms TTL=240
Reply from 41.86.110.143: bytes=32 time=79ms TTL=240

Ping statistics for 41.86.110.143:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 104ms, Average = 89ms



ping 197.80.200.164 (a local game server)

Pinging 197.80.200.164 with 32 bytes of data:
Reply from 197.80.200.164: bytes=32 time=91ms TTL=116
Reply from 197.80.200.164: bytes=32 time=86ms TTL=116
Reply from 197.80.200.164: bytes=32 time=94ms TTL=116
Reply from 197.80.200.164: bytes=32 time=87ms TTL=116

Ping statistics for 197.80.200.164:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 86ms, Maximum = 94ms, Average = 89ms


tracert www.afrihost.co.za

Tracing route to www.afrihost.co.za [197.242.144.102]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 115 ms 197 ms 129 ms 41.181.51.181
4 106 ms 108 ms 105 ms 41.181.51.182
5 62 ms 62 ms 63 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 67 ms 66 ms 68 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 93 ms * 84 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]

8 113 ms 119 ms 122 ms jh-cr-2.za--jh-cr-1.za-a.mtnns.net [196.44.31.255]
9 130 ms 122 ms 116 ms 196.44.31.99
10 84 ms 85 ms 87 ms 196.31.220.6
11 83 ms 83 ms 83 ms 196.31.220.23
12 92 ms 91 ms 91 ms 196.31.63.206
13 112 ms 111 ms 117 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
14 108 ms 107 ms 108 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.



tracert www.news24.co.za

Tracing route to x.24.com [41.86.110.143]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 222 ms 177 ms 149 ms 41.181.201.93
4 75 ms 75 ms 78 ms 41.181.201.94
5 51 ms 50 ms 52 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 66 ms 66 ms 67 ms compj-cpt-1.mtnns.net [196.44.18.2]
7 71 ms * 77 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 110 ms 110 ms 111 ms 196.44.0.74
9 129 ms 124 ms 123 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 55 ms 54 ms 54 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
11 87 ms 86 ms * vl-11-cpt-hscore-1.mweb.co.za [197.84.5.238]
12 67 ms 59 ms 59 ms 196.28.178.66
13 78 ms 79 ms 78 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 122 ms 113 ms 111 ms OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6]
15 80 ms 79 ms 79 ms 197-84-208-146.cpt.mweb.co.za [197.84.208.146]
16 108 ms 104 ms 102 ms 41-86-110-143.mweb.co.za [41.86.110.143]

Trace complete.




tracert 197.80.200.164 (a local game server)

Tracing route to 197-80-200-164.jhb.mweb.co.za [197.80.200.164]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms ZyXEL.Home [192.168.1.1]
2 * * * Request timed out.
3 207 ms 109 ms 230 ms 41.181.51.181
4 76 ms 80 ms 80 ms 41.181.51.182
5 83 ms 80 ms 82 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 83 ms 82 ms 83 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 96 ms 95 ms 101 ms 196.44.31.106
8 69 ms 68 ms 68 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
9 119 ms 117 ms 113 ms 1122.te0-0-0.cpt-pr-1.optinet.net [196.28.178.141]
10 134 ms 134 ms 141 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
11 114 ms 111 ms 106 ms tengig-0-0-0-0-vic-p-2.mweb.co.za [197.84.4.35]
12 106 ms 111 ms 109 ms tengig-0-0-0-0-102-vic-pe-1.mweb.co.za [197.80.7.41]
13 111 ms 109 ms 115 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]
14 101 ms 103 ms 101 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
15 103 ms 105 ms 107 ms 197-80-200-164.jhb.mweb.co.za [197.80.200.164]

Trace complete.



Suprise suprise, they still did not give me feedback on this. They never do.
 
Where are you located? Durban?
The MTN backbone ISPs (Afrihost/Axxess) providers use the international line that lands in Cape Town, while IS uses the line that lands in Durban (most of the time, it also depends on the ISP routing).

CPT
 
Can you run a ping to 155.239.255.250 and post the results here when you experience poor pings with afrihost.
 
while IS uses the line that lands in Durban (most of the time, it also depends on the ISP routing).

Not correct.

We, for example, route via the most appropriate international link in order to obtain the shortest distance (i.e. lowest pings) for the end user. So the international link used will be dependent on your location and a few other internal factors.
 
Perhaps I will try Crystal web if Afriman does not give me a really good response.

Hopefully Crystal web monitors local latency.
 
If you live in Cape Town DON'T USE AFRIHOST. I don't know what it is about them and Cape Town but high ping during peak and 10-50% loss is normal. At least for me.

I had been with AH for 5 years and the last few months were just too much, had to leave. Every night loss and high ping. Every morning Afriwhatever apologizing and saying "we are aware of the problem and implementing fixes". Rinse and repeat. Fast-forward a few months and nothing has changed.

The weird part is my friend who's in JHB has almost no problems with AH.
 
Top
Sign up to the MyBroadband newsletter
X