Afrihost Uncapped ADSL Feedback

Status
Not open for further replies.
We've just had confirmation that there is a problem on the Cape Town IPC, which Telkom are investigating. The IPC is currently down and traffic is being rerouted via alternative paths to stabilise service while they find the problem.

For the moment, clients in Cape Town (and routing via CT) are experiencing very slow throughput and high latencies, but we expect this to stabilise once we reroute traffic.

I'll post updates as I receive them from MTN and Telkom. We're truly sorry for the inconvenience, we're hopeful that this can be resolved quickly.
 
AfriMan said:
We've just had confirmation that there is a problem on the Cape Town IPC, which Telkom are investigating. The IPC is currently down and traffic is being rerouted via alternative paths to stabilise service while they find the problem.

For the moment, clients in Cape Town (and routing via CT) are experiencing very slow throughput and high latencies, but we expect this to stabilise once we reroute traffic.

I'll post updates as I receive them from MTN and Telkom. We're truly sorry for the inconvenience, we're hopeful that this can be resolved quickly.
Click to expand...

Again? This is like the 3rd time Cape town has had these kind of issues in under a month?
 
Initial reports that we received are that some other ISP's also experienced a "blip" in connectivity in the region. Telkom and MTN are working on this, and it looks like everything should be back to normal very soon. We're being very cautious though, and making sure that everything is being done to permanently avoid these issues.
 
jeanres said:
Is IPC still down? pings to google.com is 1500ms +
Click to expand...

According to AH:

UPDATE 27 March 2013 10:00am Telkom and MTN have restored full connectivity and are monitoring the IPC to ensure that it remains stable. At present we do not have a full incident report on the cause of the problem, but reports are that several other ISP’s with Cape Town IPC were also affected. We will ensure we implement any measures on our side to prevent reoccurrence. We thank all affected clients for their patience and understanding.
Click to expand...
 
Cape Town - Tygervalley... latency remains very high, with frequent dropped packets...

Reply from 41.72.145.85: bytes=32 time=96ms TTL=55
Reply from 41.72.145.85: bytes=32 time=113ms TTL=55
Reply from 41.72.145.85: bytes=32 time=111ms TTL=55
Reply from 41.72.145.85: bytes=32 time=106ms TTL=55
Reply from 41.72.145.85: bytes=32 time=117ms TTL=55
Reply from 41.72.145.85: bytes=32 time=115ms TTL=55
Request timed out.
Reply from 41.72.145.85: bytes=32 time=68ms TTL=55
Reply from 41.72.145.85: bytes=32 time=121ms TTL=55
Reply from 41.72.145.85: bytes=32 time=97ms TTL=55
Reply from 41.72.145.85: bytes=32 time=110ms TTL=55
Reply from 41.72.145.85: bytes=32 time=102ms TTL=55
Reply from 41.72.145.85: bytes=32 time=102ms TTL=55
Reply from 41.72.145.85: bytes=32 time=85ms TTL=55
Reply from 41.72.145.85: bytes=32 time=120ms TTL=55
Reply from 41.72.145.85: bytes=32 time=108ms TTL=55
Reply from 41.72.145.85: bytes=32 time=92ms TTL=55
Reply from 41.72.145.85: bytes=32 time=136ms TTL=55
Reply from 41.72.145.85: bytes=32 time=126ms TTL=55
Reply from 41.72.145.85: bytes=32 time=118ms TTL=55
Reply from 41.72.145.85: bytes=32 time=150ms TTL=55
Reply from 41.72.145.85: bytes=32 time=114ms TTL=55
Reply from 41.72.145.85: bytes=32 time=82ms TTL=55
Reply from 41.72.145.85: bytes=32 time=104ms TTL=55
Reply from 41.72.145.85: bytes=32 time=99ms TTL=55
Reply from 41.72.145.85: bytes=32 time=107ms TTL=55
Reply from 41.72.145.85: bytes=32 time=119ms TTL=55
Reply from 41.72.145.85: bytes=32 time=108ms TTL=55
Reply from 41.72.145.85: bytes=32 time=121ms TTL=55
Request timed out.
Reply from 41.72.145.85: bytes=32 time=102ms TTL=55
Reply from 41.72.145.85: bytes=32 time=108ms TTL=55
Reply from 41.72.145.85: bytes=32 time=119ms TTL=55
Reply from 41.72.145.85: bytes=32 time=119ms TTL=55
Reply from 41.72.145.85: bytes=32 time=38ms TTL=55
Reply from 41.72.145.85: bytes=32 time=112ms TTL=55

Normal latency is 30-35ms... traceroute doesn't show much:

Tracing route to 41.72.145.85
over a maximum of 30 hops:

1 18 ms 3 ms 1 ms 192.168.0.1
2 92 ms 89 ms 104 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 124 ms 99 ms 81 ms ipc-recieve-tb-2a.mtnbusiness.net [41.181.54.86]
4 211 ms 142 ms 162 ms tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 116 ms 126 ms 136 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 123 ms 173 ms 164 ms rb-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 143 ms 219 ms 141 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.21]
8 173 ms 243 ms 171 ms ge11-0-0.gw2.jnb6.za.mtnbusiness.net [196.30.1.22]
9 * 134 ms 117 ms vlan9.hr3.jnb6.za.mtnbusiness.net [196.30.156.136]
10 140 ms 153 ms 220 ms core-router1.jnb2.host-h.net [196.30.213.108]
11 201 ms 151 ms 173 ms firewall3.jnb2.host-h.net [41.72.136.76]
12 178 ms 156 ms 228 ms 41.72.145.85

Trace complete.

This issue is definitely not remedied Afriman!
 
I'm in the East Rand (Joburg), and something is still wrong with international:

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 6 ms 6 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1.65]
3 8 ms 8 ms 8 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
4 15 ms 8 ms 7 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 8 ms 8 ms 8 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 186 ms 186 ms 186 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
7 187 ms 187 ms 187 ms core2.ams.net.google.com [195.69.145.100]
8 190 ms 186 ms 186 ms 209.85.254.95
9 187 ms 187 ms 187 ms 209.85.255.72
10 186 ms 186 ms 185 ms 209.85.240.29
11 182 ms 186 ms 182 ms 209.85.253.197
12 182 ms 183 ms 183 ms 209.85.253.175
13 182 ms 182 ms 183 ms lhr14s22-in-f23.1e100.net [173.194.34.183]

compared to my tracert of the afrihost website:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 7 ms 105-236-1-65-esr-lo.mtnbusiness.co.za [105.236.1.65]
3 8 ms 8 ms 8 ms ipc-recieve-jh-1a.za.mtnbusiness.net [41.181.178.5]
4 8 ms 7 ms 8 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 8 ms 7 ms 7 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 9 ms 9 ms 9 ms jh-cr-2.za--jh-dca-2.za-a.mtnns.net [196.44.0.224]
7 10 ms 10 ms 9 ms 196.44.31.99
8 9 ms 10 ms 10 ms 196.30.1.39
9 10 ms 9 ms 9 ms tengigabitethernet1-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.23]
10 9 ms 10 ms 9 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
11 9 ms 9 ms 9 ms cms-gm.afrihost.com [197.242.144.102]
 
Last edited:
Somewhere something is very wrong... google ping:

1 2 ms 3 ms 7 ms 192.168.0.1
2 90 ms 83 ms 89 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 74 ms * 90 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 159 ms * * tb-dca-2.za--qux-a.za.mtnbusiness.net [41.181.184.28]
5 175 ms 75 ms 38 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 254 ms 242 ms 245 ms am-cr-2.nl--am-cr-nl-b.mtnns.net [196.44.31.171]
7 272 ms 274 ms 254 ms ls-cr-1.uk--am-cr-2.nl-b.mtnns.net [196.44.31.155]
8 * 239 ms 236 ms am-cr-2.nl--am-tpr-1.nl-a.mtn.net [209.212.111.218]
9 229 ms * 238 ms core2.ams.net.google.com [195.69.145.100]
10 245 ms 252 ms 236 ms 209.85.254.95
11 237 ms 231 ms 224 ms 209.85.255.60
12 239 ms * 262 ms 209.85.243.32
13 237 ms 231 ms 233 ms 209.85.253.197
14 231 ms * 221 ms 209.85.253.115
15 228 ms 230 ms 237 ms lhr14s21-in-f23.1e100.net [173.194.34.151]

Afrihost web server:
1 1 ms 1 ms 3 ms 192.168.0.1
2 81 ms 67 ms 80 ms 105-236-8-193-esr-lo.mtnbusiness.co.za [105.236.8.193]
3 * 86 ms 79 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 * * * Request timed out.
5 86 ms 104 ms 206 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 116 ms 113 ms 110 ms rb-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 130 ms 94 ms 123 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
8 98 ms 103 ms 104 ms ge10-1-9sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.12]
9 135 ms 143 ms 108 ms tengigabitethernet9-1.gw20.jnb6.za.mtnbusiness.net [196.31.220.25]
10 127 ms 99 ms 103 ms tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.net [196.31.63.198]
11 107 ms 124 ms 110 ms cms-gm.afrihost.com [197.242.144.102]

Note the request timed out somewhere on the MTN network!
 
3 * 86 ms 79 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
Nah that's still IPC issues, I'm afraid.
 
Sinbad said:
3 * 86 ms 79 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
Nah that's still IPC issues, I'm afraid.
Click to expand...

Yip, seems to be the case. What annoys me is that Afrihost are giving me the run around... port reset done... them exchange congestion... while clearly it's the IPC! I've pretty much had it with Afrihost & MTN, too many problems, too frequently, too many excuses!
 
BGE said:
Yip, seems to be the case. What annoys me is that Afrihost are giving me the run around... port reset done... them exchange congestion... while clearly it's the IPC! I've pretty much had it with Afrihost & MTN, too many problems, too frequently, too many excuses!
Click to expand...
So they're doing what's in their power to try to make things better, but you've had it anyway?

Glad you're not my customer.
 
Sinbad said:
So they're doing what's in their power to try to make things better, but you've had it anyway?

Glad you're not my customer.
Click to expand...

:) We've had some "issues" in Cpt for some time now. I can understand the frustration. It is getting better though. Slowly.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X