Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
DSL dead this side.

Synced and connected fine but nothing is working.

In Alberton.
 
For those affected, please confirm your area.
Queries coming in and monitoring only seems to indicate an issue on the North IPC.
 
KZN belly up, YouTube stuck at 1mbps on a 20mbps line

Tracing route to afrihost.com [104.20.31.244]
over a maximum of 30 hops:

1 * * * Request timed out.
2 214 ms 181 ms 227 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 115 ms 139 ms 96 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 148 ms 191 ms 205 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 256 ms 291 ms 276 ms 41.162.84.192
6 317 ms 324 ms 271 ms 172.18.1.162
7 390 ms 410 ms 421 ms cloudflare.ixp.joburg [196.46.25.198]
8 394 ms 373 ms 307 ms 104.20.31.244

Trace complete.

Tracing route to mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

1 * * * Request timed out.
2 22 ms 22 ms 22 ms dbn-up2.ip.adsl.co.za [169.1.5.173]
3 235 ms 227 ms 227 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 228 ms 28 ms 226 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 129 ms 2220 ms 221 ms optinet.ixp.durban [196.10.141.75]
6 250 ms 258 ms 255 ms 197-82-7-1.dbn.mweb.co.za [197.82.7.1]
7 153 ms 255 ms 251 ms te0-7-0-1.vic-p-2.optinet.net [197.84.4.44]
8 259 ms 259 ms 259 ms te0-0-0-0.cpt-p-1.optinet.net [197.84.4.34]
9 252 ms 251 ms 251 ms vl11.cpt-hscore-1.optinet.net [197.84.5.238]
10 189 ms 185 ms 146 ms 196.28.178.66
11 156 ms 279 ms 113 ms cte-core-sw2.vwol.net [196.41.144.35]
12 179 ms 162 ms 137 ms www.mweb.co.za [196.2.63.110]

Trace complete.

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=14ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
 
AfriGuy - just a heads up that I cannot get through to your call centre. I don't need to now that I know you guys are aware of the issue but you might want to have someone look into that :)
 
AfriGuy - just a heads up that I cannot get through to your call centre. I don't need to now that I know you guys are aware of the issue but you might want to have someone look into that :)

Thanks for the heads up. Saw a massive spike of a couple hundred calls, PBX is probably battling.
We should have an IVR up, if it isn't already.

Relaying feedback via our noticeboard, social and here as best we can in the mean time.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X