South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
And once we have your line at the 20 / 40 Mbps profile I will make sure we credit you out fully.
@Afrigenie.
Am I going to wait another week?
I'll chat to AfriGenie and our team, we'll do our best to have the line sorted out ASAP.
Im sorry to all the people experiancing issues but moving to Afrihost was awesome for me.
Full line speed and 450gb free data. Love you guys
@afriman and afrigenie - i finally claimed the elusive one
![]()
ETA please.
Enjoy it dude!
Is there any reliable bandwidth speed benchmarking site other than speedtest? I ask, because, although my AH speedtest results are good at the moment, the actual experience is not, and if I test download a file hosted on a remote dedicated server (with a large pipe at a datacentre) using AH the speed is max 50-60KBs but using another ISP is near max line speed, so while I don't mean to cast any aspersions, it seems that speedtest.net is becoming increasgly detached from reality.
The latency is far too high, could you paste up a traceroute here please? I'd like to see where the latency is being introduced.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Melvin>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 192.168.1.1
2 260 ms 255 ms 270 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.
3.193]
3 362 ms 411 ms 461 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 472 ms 460 ms 443 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 403 ms 398 ms 424 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 419 ms 467 ms 451 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 404 ms 421 ms 456 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 443 ms 400 ms 403 ms rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [
196.43.25.137]
9 385 ms 438 ms 463 ms 196.43.39.166
10 567 ms 504 ms 505 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 * 500 ms 479 ms nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
12 495 ms * 626 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]
Trace complete.
C:\Users\Melvin>
Are you running any services in the background here? Looks like the latency is being introduced at the exchange, possibly indicating congestion![]()
Hi,
there is no background services running what should I do?
Log a call with Telkom indicating exchange congestion. Note down the time, the latency etc and give all that to the person logging the fault.
Then you go and slaughter 2 cats, 1 chicken, half a cow and dance naked bathed in the sweat of 23 male virgins on the 3rd full moon of the 8th month....
Or you'll have to wait till your exchange falls in their upgrade fiscal quarterly planning. :-/
Sad but true. Nothing any ISP can do about it. All up to Telkom and their timelines.