Afrihost New Network Feedback

Status
Not open for further replies.
sounds like it yes. Just said something about transmission link which needs to be installed. No timeline though :( so evenings ill just have to download what i want to watch, and leave the streaming for the day time for now

That's horrible. Hopefully it won't be too long until they fix this for you :(
 
Probably a ships anchor ripped through some undersea cable.. Now we all sit :whistle:

More like someone drove into a Telkom box. If the ship did it's thing all ISP's would be suffering

uZIxYo4.jpg
 
Ok so I've had traceroutes going for the past few hours to 5 different sites constantly and logging them and one trend has stayed constant, I will use twitch as an example.

Tracing route to ssl.cdn.twitch.tv.c.footprint.net [8.253.70.90]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 21 ms 20 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 19 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 20 ms 20 ms 19 ms 41.162.84.192
6 47 ms 28 ms 27 ms 172.18.1.162
7 38 ms 38 ms 28 ms if-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
8 202 ms 202 ms 203 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
9 193 ms 193 ms 193 ms if-ae-5-10.tcore2.pv9-lisbon.as6453.net [80.231.159.93]
10 189 ms 190 ms 188 ms if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
11 200 ms 201 ms 201 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
12 187 ms 187 ms 188 ms if-ae-19-2.tcore2.l78-london.as6453.net [80.231.138.22]
13 187 ms 187 ms 188 ms if-ae-2-2.tcore1.l78-london.as6453.net [80.231.131.2]
14 198 ms 199 ms 199 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
15 191 ms 191 ms 191 ms 195.219.83.102
16 * * * Request timed out.
17 188 ms 187 ms 187 ms 8.253.70.90

However if I ping that node
Pinging 41.206.178.2 with 32 bytes of data:
Reply from 41.206.178.2: bytes=32 time=46ms TTL=52
Reply from 41.206.178.2: bytes=32 time=45ms TTL=52
Reply from 41.206.178.2: bytes=32 time=45ms TTL=52
Reply from 41.206.178.2: bytes=32 time=46ms TTL=52

Or tracert to it
Tracing route to if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 21 ms 20 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 20 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 20 ms 19 ms 19 ms 41.162.84.192
6 28 ms 28 ms 28 ms 172.18.1.162
7 28 ms 27 ms 28 ms if-ae-7-0.tcore1.jso-johannesburg.as6453.net [41.206.178.29]
8 46 ms 45 ms 46 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]

Or tracert the next hop

Tracing route to if-ae-5-10.tcore2.pv9-lisbon.as6453.net [80.231.159.93]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 20 ms 20 ms 20 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 19 ms 20 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 20 ms 20 ms 19 ms 41.162.84.192
6 27 ms 27 ms 27 ms 172.18.1.162
7 29 ms 28 ms 28 ms if-ae-7-0.tcore2.jso-johannesburg.as6453.net [41.206.179.13]
8 28 ms 54 ms 29 ms if-ae-2-2.tcore1.jso-johannesburg.as6453.net [216.6.55.85]
9 47 ms 46 ms 47 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
10 160 ms 160 ms 160 ms if-ae-5-10.tcore2.pv9-lisbon.as6453.net [80.231.159.93]

Its fine.

Only when you break out of as6453 is the latency high at that local point

Tracing route to if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 19 ms 20 ms 19 ms dbn-up2.ip.adsl.co.za [169.1.5.174]
4 20 ms 20 ms 19 ms dbn-in1.ip.adsl.co.za [169.1.5.204]
5 19 ms 19 ms 20 ms 41.162.84.192
6 28 ms 28 ms 27 ms 172.18.1.162
7 * * * Request timed out.
8 50 ms 28 ms 28 ms if-ae-2-2.tcore1.jso-johannesburg.as6453.net [216.6.55.85]
9 47 ms 47 ms 47 ms if-ae-4-2.tcore1.klt-cape-town.as6453.net [41.206.178.2]
10 168 ms 168 ms 168 ms if-ae-5-2.tcore2.pv9-lisbon.as6453.net [80.231.159.129]
11 173 ms 168 ms * if-ae-2-2.tcore1.pv9-lisbon.as6453.net [80.231.158.5]
12 198 ms 205 ms 197 ms if-ae-1-3.tcore1.sv8-highbridge.as6453.net [80.231.158.30]
13 194 ms 195 ms 194 ms if-ae-19-2.tcore2.l78-london.as6453.net [80.231.138.22]
14 193 ms 194 ms 194 ms if-ae-2-2.tcore1.l78-london.as6453.net [80.231.131.2]
15 210 ms 207 ms 207 ms if-ae-17-2.tcore1.ldn-london.as6453.net [80.231.130.130]
 
Last edited:
I haven't had any disconnects for a while now. Hopefully things are back to normal. Especially considering that my backup 10GB ISPAfrika account is now used up.
 
Ok so I've had traceroutes going for the past few hours to 5 different sites constantly and logging them and one trend has stayed constant, I will use twitch as an example.



However if I ping that node


Or tracert to it


Or tracert the next hop



Its fine.

Only when you break out of as6453 is the latency high at that local point

Thanks for all the tests. Will pass onto the network guys
 
Well I get back home and now I have this

Last Result:
Download Speed: 255 kbps (31.9 KB/sec transfer rate)
Upload Speed: 857 kbps (107.1 KB/sec transfer rate)
Latency: 24 ms
Jitter: 263 ms
‎06‎/‎04‎/‎2016‎ ‎17‎:‎58

10MB Business account, I cannot work with a connection like this!
 
I can't even log onto my client zone to log a support issue, this is poor!

Why is this happening?

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 * 26 ms * cpt-up1.ip.adsl.co.za [169.1.5.105]
4 24 ms 24 ms 24 ms cpt-in1.ip.adsl.co.za [169.1.5.118]
5 23 ms 23 ms 27 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 * 23 ms * optinet.ct1.napafrica.net [196.10.140.15]
7 47 ms 47 ms 47 ms bu-ether1.cpt-p-1.optinet.net [197.84.7.33]
8 45 ms 47 ms * te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 44 ms 43 ms 44 ms 102.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.36]

10 43 ms 43 ms 43 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
11 45 ms 45 ms 44 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
12 44 ms * 44 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
13 44 ms 44 ms 44 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
14 43 ms * 43 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

Tracer to Afrihost, and it goes to mweb??
 
Last edited:
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X