Hmm, if something seems too good to be true, it probably isn't. Are the wheels falling off?
No ways
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Hmm, if something seems too good to be true, it probably isn't. Are the wheels falling off?
Sure.Could you perhaps post a trace route up so we can see where the added latency is being introduced?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Gavin>tracert telkom.co.za
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.0.0.2
2 10 ms 10 ms 10 ms 105-236-2-65-esr-lo.mtnbusiness.co.za [105.236.2
.65]
3 92 ms 91 ms 102 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178
.17]
4 82 ms 79 ms 78 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 67 ms 78 ms 66 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 76 ms 80 ms 79 ms 41.181.139.109
7 77 ms 73 ms 74 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 162 ms 157 ms 156 ms 196.43.25.137
9 161 ms 162 ms 162 ms 196.43.39.162
10 154 ms 153 ms 151 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 146 ms 149 ms 153 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
12 151 ms 153 ms 153 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]
Trace complete.
C:\Documents and Settings\Gavin>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Gavin>tracert afrihost.co.za
Tracing route to 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 10 ms 10 ms 11 ms 105-236-2-65-esr-lo.mtnbusiness.co.za [105.236.2
.65]
3 95 ms 97 ms 135 ms ipc-recieve-jh-2a.za.mtnbusiness.net [41.181.178
.17]
4 70 ms 70 ms 74 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 78 ms 76 ms 77 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 66 ms 67 ms 66 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.198]
7 66 ms 68 ms 67 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.198]
8 88 ms 86 ms 85 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
C:\Documents and Settings\Gavin>
That's not specific, that's the same generic response as before. I feel like we are going around in circles. Can Afriman be more specific or does he also lack the mandate?Our engineers and Management team are working on this as top priority. As to what exactly is being done I'm not 100% sure. When I do have feedback I'll be sure to let everyone know.
For now, we're doing what we can to normalise latency as best as possible.
Could you perhaps post a trace route up so we can see where the added latency is being introduced?
Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=83ms TTL=59
Reply from 197.242.144.102: bytes=32 time=79ms TTL=59
Reply from 197.242.144.102: bytes=32 time=84ms TTL=59
Reply from 197.242.144.102: bytes=32 time=85ms TTL=59
Ping statistics for 197.242.144.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 85ms, Average = 82ms
tracert afrihost.com
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:
1 7 ms 7 ms 7 ms 105-236-*.*-esr-lo.mtnbusiness.co.za [105.236
.*.*]
2 93 ms 89 ms 87 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
3 100 ms 97 ms 94 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
4 111 ms * 85 ms jh-cr-2.za--rb-cr-1.za-b.mtnns.net [196.44.31.17
1]
5 158 ms 99 ms 102 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 92 ms 84 ms 90 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.198]
7 88 ms 80 ms 77 ms cms-gm.afrihost.com [197.242.144.102]
Trace complete.
That's not specific, that's the same generic response as before. I feel like we are going around in circles. Can Afriman be more specific or does he also lack the mandate?
That's not specific, that's the same generic response as before. I feel like we are going around in circles. Can Afriman be more specific or does he also lack the mandate?
Any feedback on the latency issues? I posted the trace route as per AfriGuy's request.
Thank you for taking the time with yet another "no answer" to my question.It's not a question of mandate and authority, we cannot give you unconfirmed information until we have timeframes and data to announce. Our mandate is to engage with our clients and reassure them that this is being addressed at the highest levels of our company. I can assure you that we as a company as as concerned (if not more concerned) about how this affects our clients and the level of experience we are seeing.
As soon as I know that there is a confirmed announcement, we will make this public here and to our other clients.
Thank you for taking the time with yet another "no answer" to my question.
While latency is still unacceptably high, throughput, as in the case with froot, is good. Particularly pleasing is the performance downloading torrents...
![]()
Hoping to get a round or 2 of battlefield in tonight. So hope there is no latency when I get home (well except for the latency to my exchange that is still there now and then)
Out of interest, what's your streaming like at the moment? While downloads are quite network resource heavy, they aren't very reliant on latency. Odd I know, but I've seen guys torrent until they're blue in the face with 1500ms+ to their exchange o.0
Pretty damn good. Little to no buffering 720p, youtube. Usually I download material using IDM though and watch once it's down...
![]()
Browsing is painful today though, on account of the latency...
That's properly awesome to hear, browsing barred obviously
I must say, I'm quite surprised that streaming is performing so well on your end as it's heavily dependant on a pretty stable latency.

While latency is still unacceptably high, throughput, as in the case with froot, is good. Particularly pleasing is the performance downloading torrents...
![]()
That's properly awesome to hear, browsing barred obviously
I must say, I'm quite surprised that streaming is performing so well on your end as it's heavily dependant on a pretty stable latency.