Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Well nothing has changed in the past 2 years other than I am no longer able to view video. What must I do to improve my situation
 
AfriGenie said:
Last night specifically, there was an issue with one of the links on the IPC dropping out, this has been resolved as far as I know, I'm not sure if this would have been the cause of the previously mentioned latency that was experienced.
Click to expand...

Will test tonight and see then, it started on Friday though.
 
dingaanone said:
Well nothing has changed in the past 2 years other than I am no longer able to view video. What must I do to improve my situation
Click to expand...

Was the line more stable at a lower line speed?
Also, have you tested another ISP to see if the experience is the same?

From the results you've posted here so far it does look like a line related issue though.
 
Sigh never ending disconnects, I have downgraded to 8Mbs, I don't know if it has been completed, I need to be moved to a different DSLAM or back to my old DSLAM.
 
dj2381 said:
Sigh never ending disconnects, I have downgraded to 8Mbs, I don't know if it has been completed, I need to be moved to a different DSLAM or back to my old DSLAM.
Click to expand...

Drop me a PM with your line number and I'll see what's happening :)
 
AfriGuy said:
Those are pretty dismal numbers :(
Do you know which IP you're pulling content from? Are other streaming services affected?
Click to expand...

Take your pick. I have the chrome extension installed that lets me pick my server region. Makes no difference.
 
image132 said:
Take your pick. I have the chrome extension installed that lets me pick my server region. Makes no difference.
Click to expand...

Twitch has always been tricky to nail down, we do our best to get the traffic through.
What do traceroutes/ pings look like to a destination IP?

A pretty big influence on why Twitch doesn't perform as well is due to the lack of a CDN/ node locally.
 
AfriGuy said:
Twitch has always been tricky to nail down, we do our best to get the traffic through.
What do traceroutes/ pings look like to a destination IP?

A pretty big influence on why Twitch doesn't perform as well is due to the lack of a CDN/ node locally.
Click to expand...

Tracing route to live.twitch.tv [23.160.0.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 23 ms 21 ms 21 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 22 ms 21 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 21 ms 21 ms 21 ms 41.164.52.40
6 22 ms 24 ms 21 ms if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 169 ms 169 ms 169 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
8 169 ms 171 ms 169 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 170 ms 169 ms 169 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 176 ms 175 ms 175 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
11 172 ms 172 ms 172 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
12 167 ms 167 ms 166 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 163 ms 164 ms 164 ms 195.219.83.102
14 163 ms 163 ms 162 ms ae-230-3606.edge4.London1.Level3.net [4.69.166.21]
15 * * * Request timed out.

I've been having this problem for over a year now.
 
image132 said:
Tracing route to live.twitch.tv [23.160.0.86]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 23 ms 21 ms 21 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 22 ms 21 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 21 ms 21 ms 21 ms 41.164.52.40
6 22 ms 24 ms 21 ms if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 169 ms 169 ms 169 ms if-ae-5-30.tcore2.PV9-Lisbon.as6453.net [80.231.159.85]
8 169 ms 171 ms 169 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
9 170 ms 169 ms 169 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 176 ms 175 ms 175 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
11 172 ms 172 ms 172 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
12 167 ms 167 ms 166 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 163 ms 164 ms 164 ms 195.219.83.102
14 163 ms 163 ms 162 ms ae-230-3606.edge4.London1.Level3.net [4.69.166.21]
15 * * * Request timed out.

I've been having this problem for over a year now.
Click to expand...

Doesn't look bad at all, throughput should definitely be better here.
Not sure how your Chrome extension works, I just ran a test on this stream which pulled content down from 192.16.64.219. I managed to stream on High without any issue.

I assume your Chrome extensions pulls data from an iftop type source?

EDIT: Just checked a few more streams, High quality completely saturates my line. The stream uses 1.1MB/s.
 
Last edited:
AfriGuy said:
Doesn't look bad at all, throughput should definitely be better here.
Not sure how your Chrome extension works, I just ran a test on this stream which pulled content down from 192.16.64.219. I managed to stream on High without any issue.

I assume your Chrome extensions pulls data from an iftop type source?

EDIT: Just checked a few more streams, High quality completely saturates my line. The stream uses 1.1MB/s.
Click to expand...

I sent you a PM.
 
And back to same old latency... again. As I said - clearly a trend depending on the time of connecting to the net. And outside of normal working hours its virtually impossible to get a proper connection via this Telkom exchange.

tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 1007 ms 1094 ms 924 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 903 ms 1070 ms 886 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 990 ms 965 ms 912 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 1148 ms 1179 ms 1245 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 1103 ms 1219 ms 1278 ms africainx.ixp.capetown [196.10.140.7]
7 1182 ms 1182 ms 1118 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-1.AINX.P2P.10G.za.africainx.net [41.84.13.196]
8 1151 ms 1183 ms 1050 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 1080 ms 1132 ms 1103 ms 104.20.30.244

Trace complete.
 
Johnatan56 said:
Android or iOS?
iOS is home and lock button at the same time, android is home and volume down key usually.
EDIT: Obviously it's android, sorry.
EDIT2: Plants vs Zombies is going at 350kB/s (I panicked, didn't know what app to pick off of the PlayStore :p). Note I am also downloading a file via skype at 250kB/s at the same time. My download rate on speedtests is about 8Mbps.
Click to expand...
Thank you. :)
 
DeSLAM said:
And back to same old latency... again. As I said - clearly a trend depending on the time of connecting to the net. And outside of normal working hours its virtually impossible to get a proper connection via this Telkom exchange.

tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 10.0.0.2
2 1007 ms 1094 ms 924 ms 169-0-44-1.ip.afrihost.co.za [169.0.44.1]
3 903 ms 1070 ms 886 ms cpt-up1.ip.adsl.co.za [169.1.5.105]
4 990 ms 965 ms 912 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
5 1148 ms 1179 ms 1245 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 1103 ms 1219 ms 1278 ms africainx.ixp.capetown [196.10.140.7]
7 1182 ms 1182 ms 1118 ms CORE.GP-ID-DCE-3.TO.GP-ID-MEC-1.AINX.P2P.10G.za.africainx.net [41.84.13.196]
8 1151 ms 1183 ms 1050 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africainx.net [41.66.181.59]
9 1080 ms 1132 ms 1103 ms 104.20.30.244

Trace complete.
Click to expand...

Looks like congestion.
Have you tested with another ISP?
 
AfriGuy said:
Looks like congestion.
Have you tested with another ISP?
Click to expand...

Yup using Telkom ISP account, I get 1230ms per hop...crazy.

Also the max Attainable Rate (Kbps) of the line has dropped to 3616 Kbps. It was much higher on the weekend.
 
Last edited:
DeSLAM said:
Yup using Telkom ISP account, I get 1230ms per hop...crazy.

Also the max Attainable Rate (Kbps) of the line has dropped to 3616 Kbps. It was much higher on the weekend.
Click to expand...

:(
Telkom will need to upgrade the infrastructure in the area to see the congestion eased here.

Remember that attainable rates are only estimations that the router uses based on the stats. So if your stats change, the attainable rates will change.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X