South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Wonder if this is related to the issues http://www.afrihost.com/site/network_status

No offense but you really need to review your service level agreement with Telkom if they wont even return your calls regarding line faults.
I see a few posts on international speeds. As far as I am aware, EASSy is currently offline, so we're running on WACS and SAT3. When EASSy was restored, latencies did not seem to improve, and a decision was made to schedule major maintenance to ensure that when it comes back up, service and performance is back to what it should be. However, as I understand it, capacity on failover cables should be almost full capacity, so we should be experiencing any major drops in access level.
We'll have to take this back to our network guys and find out where and what is not firing as it should be![]()
I see a few posts on international speeds. As far as I am aware, EASSy is currently offline, so we're running on WACS and SAT3. When EASSy was restored, latencies did not seem to improve, and a decision was made to schedule major maintenance to ensure that when it comes back up, service and performance is back to what it should be. However, as I understand it, capacity on failover cables should be almost full capacity, so we should be experiencing any major drops in access level.
We'll have to take this back to our network guys and find out where and what is not firing as it should be![]()

Hi AfriMan - I just sent you a PM with my details as I am also affected by the issues in Somerset West.
Not sure if this tracert and speedtest result helps. Local ping times are really poor.
Tracing route to www.google.com [173.194.34.82]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 94 ms 108 ms 93 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.
8.193]
3 118 ms 115 ms 117 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 97 ms 97 ms 105 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 97 ms 97 ms 97 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 352 ms 286 ms 288 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]
7 248 ms 252 ms 243 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83
]
8 288 ms 286 ms 286 ms 195.66.224.125
9 308 ms 308 ms 310 ms 209.85.240.63
10 287 ms 286 ms 287 ms 209.85.253.92
11 292 ms 293 ms 292 ms 72.14.232.134
12 293 ms * 246 ms 72.14.238.43
13 * * * Request timed out.
14 295 ms * 294 ms lhr14s19-in-f18.1e100.net [173.194.34.82]
Trace complete.
Tracing route to www.myadsl.co.za [41.203.21.137]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 95 ms 95 ms 94 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.
8.193]
3 188 ms 149 ms 156 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 164 ms 126 ms 122 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.18
4.28]
5 162 ms 149 ms 148 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 156 ms 149 ms 148 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 127 ms 122 ms 120 ms rb-cr-1.za--ct-cr-2.za-b.mtnns.net [196.44.31.25
0]
8 141 ms 141 ms 119 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.22
1]
9 143 ms 139 ms 141 ms 196.30.1.39
10 151 ms 140 ms 140 ms tengigabitethernet1-1.gw21.jnb6.za.mtnbusiness.n
et [196.31.220.21]
11 * 142 ms * tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.ne
t [196.31.63.150]
12 120 ms 118 ms 117 ms core-router1.jnb2.host-h.net [196.30.213.108]
13 119 ms 120 ms 121 ms core-access-switch1-vlan1001.jnb.host-h.net [41.
72.136.53]
14 145 ms 139 ms 139 ms mybroadband.co.za [41.203.21.137]
Trace complete.
That sucks bro. You're in Telkom's hands it seems. Nothing any ISP can do about your exchange.
That is not at all encouraging as I still have not been able to test my new 10Mb line since Saturday.![]()
I see a few posts on international speeds. As far as I am aware, EASSy is currently offline, so we're running on WACS and SAT3. When EASSy was restored, latencies did not seem to improve, and a decision was made to schedule major maintenance to ensure that when it comes back up, service and performance is back to what it should be. However, as I understand it, capacity on failover cables should be almost full capacity, so we should be experiencing any major drops in access level.
According to Telkom's interrogation of your line, your SNR (Signal to Noise Ratio) is lower than optimal which could contribute to slow throughput. And SNR can be negatively effected by rain.
That being said, we are still trying to identify any other factors that may be causing the slow throughput you are experiencing.
Regards,
Afrihost Dev Team
I got this same bull**** story last week and was told it would probably be up before the end of last week. Don't give us this lame repetitive story.
We want an ETR on EASSy and also a reason why your back up service is pathetic.
EASSy dsnt even have a website that is updated yet you running with them. If they cant even maintain a website how can they fix/manage an undersea cable?
"We"? Best you clarify who you presume to speak for.