Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
wingnut771 said:
Hey there, seeing none of the reps are asking you this but can you please do this test from the command prompt (start, run, cmd):

ping -n 100 bras.afrihost.co.za (I think thats right) and post the results (right click, choose mark, highlight area, hit enter, paste into message).
Click to expand...

It's bras.afrihost.com :D

It's not my exchange, as I've always seen good results from pinging to the exchange
Code: 
ping -n 5 bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 10ms, Average = 9ms

With streaming services it's always a struggle with AH and most of the time the blame is put on the service "I'm not saying it's not their fault", which could be the case. It's frustrating that I'm needed to continually run tests to help optimise AH's network, if I don't run tests it's made to look like I don't want my experience to improve.
 
NewBiks said:
It's bras.afrihost.com :D

It's not my exchange, as I've always seen good results from pinging to the exchange
Code: 
ping -n 5 bras.afrihost.com

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=9ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63
Reply from 155.239.255.250: bytes=32 time=10ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 5, Received = 5, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 9ms, Maximum = 10ms, Average = 9ms

With streaming services it's always a struggle with AH and most of the time the blame is put on the service "I'm not saying it's not their fault", which could be the case. It's frustrating that I'm needed to continually run tests to help optimise AH's network, if I don't run tests it's made to look like I don't want my experience to improve.
Click to expand...

Thanks for correcting me :D

My advice? Submit cancellation and use ISP that works for you. Life is too short.
 
NewBiks said:
Was thinking about it but then I read Telkom are on strike plus it's the middle of the month :D
Click to expand...

T.I.A. :whistle:

EDIT: You can still hit the cancel button, nothing will happen until the end of the month, used to be before the 25th, now it's the 23rd ;)
 
NewBiks said:
Was thinking about it but then I read Telkom are on strike plus it's the middle of the month :D
Click to expand...

wingnut771 said:
T.I.A. :whistle:

EDIT: You can still hit the cancel button, nothing will happen until the end of the month, used to be before the 25th, now it's the 23rd ;)
Click to expand...

Any pending cancellation can be removed before 00h00 on the last day of the month as well.
 
My Afrihost account is fine, works flawlessly, Decent ping in games. The only problem I have is one day I can watch twitch on Source no problem but another i have to watch in medium or low otherwise it is constant buffering, but aside from that excellent performance. To my surprise even torrents downloaded fairly quick which i didn't expect
 
Kilerhotdog said:
My Afrihost account is fine, works flawlessly, Decent ping in games. The only problem I have is one day I can watch twitch on Source no problem but another i have to watch in medium or low otherwise it is constant buffering, but aside from that excellent performance. To my surprise even torrents downloaded fairly quick which i didn't expect
Click to expand...

Twitch has started switching over from Flash to HTML5, and this hasn't always been as smooth as expected. Do specific streams seem to be affected by the drop in performance or does it affect Twitch in general?
 
Last edited:
Kilerhotdog said:
My Afrihost account is fine, works flawlessly, Decent ping in games. The only problem I have is one day I can watch twitch on Source no problem but another i have to watch in medium or low otherwise it is constant buffering, but aside from that excellent performance. To my surprise even torrents downloaded fairly quick which i didn't expect
Click to expand...

I can relate to this.

You would think the switching from Flash to HTML5 could be the cause but I've always stuggled with Twitch even on High.
 
NewBiks said:
I can relate to this.

You would think the switching from Flash to HTML5 could be the cause but I've always stuggled with Twitch even on High.
Click to expand...

Twitch is a bit of a tricky service, as the server from which the content is being broadcast can very greatly depending on who the streamer is. Youtube for example will always serve the content from the server or CDN closest to the viewer, whereas Twitch will serve the content on the closest server to the streamer.

With your current DSL line though you shouldn't have too much of an issue streaming on Medium or High. Is there a specific stream that you have trouble with?
 
AfriGenie said:
Twitch has started making switching over from Flash to HTML5, and this hasn't always been as smooth as expected. Do specific streams seem to be affected by the drop in performance or does it affect Twitch in general?
Click to expand...

It was just twitch in general, but it is fine now the problems were last week-ish. watched the entire Saturday stream for Dota 2 international on 1080p60fps and buffered 2 times i think but for like 1 second.

What is weird for me is how some people has tons of problems, but some of us has none
 
AfriGenie said:
Twitch is a bit of a tricky service, as the server from which the content is being broadcast can very greatly depending on who the streamer is. Youtube for example will always serve the content from the server or CDN closest to the viewer, whereas Twitch will serve the content on the closest server to the streamer.

With your current DSL line though you shouldn't have too much of an issue streaming on Medium or High. Is there a specific stream that you have trouble with?
Click to expand...

It's Twitch in general, I've watched an SA based streamer at the last LAN here in CPT and it would still buffer/
But yes I know Twitch can be a hit and miss which is a real shame.

Also it doesn't depend on the streamer I watch, I've watched the same streamer across two days and have had varying performance differences.

What is AH doing (from your end) to help improve things for us?
 
NewBiks said:
It's Twitch in general, I've watched an SA based streamer at the last LAN here in CPT and it would still buffer/
But yes I know Twitch can be a hit and miss which is a real shame.

Also it doesn't depend on the streamer I watch, I've watched the same streamer across two days and have had varying performance differences.

What is AH doing (from your end) to help improve things for us?
Click to expand...

We'll do our best to optimize the routing to Twitch as much as possible, but the lack of any South African-based Twitch server or CDNs does hurt streaming performance quite a bit.

I've experimented with Twitch broadcasting a few times and it seems the closest server to us was in Hamburg which is far from ideal. The best thing we can all do is to support local Twitch Streamers as much as possible, the higher the local viewership the more likely it is for Twitch to put a local server in place.
 
Android updates again fluctuating wildly. On Afrihost account going from 200Kbps to 4Mbps then down to 10Kbps.

On Afrihost 1GB free account staying more stable, but stuck at no more than 3Mbps
Telkom account running at full speed and stable.

Pinging play.google.com on Afrihost Business account
Code: 
Pinging play.l.google.com [216.58.223.14] with 32 bytes of data:
Reply from 216.58.223.14: bytes=32 time=29ms TTL=53
Reply from 216.58.223.14: bytes=32 time=29ms TTL=53
Reply from 216.58.223.14: bytes=32 time=41ms TTL=53
Reply from 216.58.223.14: bytes=32 time=51ms TTL=53
Reply from 216.58.223.14: bytes=32 time=54ms TTL=53
Reply from 216.58.223.14: bytes=32 time=39ms TTL=53
Reply from 216.58.223.14: bytes=32 time=32ms TTL=53
Request timed out.
Reply from 216.58.223.14: bytes=32 time=36ms TTL=53
Reply from 216.58.223.14: bytes=32 time=29ms TTL=53
Reply from 216.58.223.14: bytes=32 time=173ms TTL=53
Reply from 216.58.223.14: bytes=32 time=172ms TTL=53
Reply from 216.58.223.14: bytes=32 time=54ms TTL=53
Reply from 216.58.223.14: bytes=32 time=169ms TTL=53
Reply from 216.58.223.14: bytes=32 time=30ms TTL=53
Reply from 216.58.223.14: bytes=32 time=43ms TTL=53
Reply from 216.58.223.14: bytes=32 time=53ms TTL=53
Reply from 216.58.223.14: bytes=32 time=177ms TTL=53
Reply from 216.58.223.14: bytes=32 time=32ms TTL=53
Reply from 216.58.223.14: bytes=32 time=29ms TTL=53

Ping statistics for 216.58.223.14:
    Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 177ms, Average = 66ms

Code: 
tracert play.google.com

Tracing route to play.l.google.com [216.58.223.14]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  wall.exa [10.0.0.254]
  2     *        *        *     Request timed out.
  3    13 ms    10 ms     8 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82]
  4    12 ms    10 ms     9 ms  cpt-net1.ip.adsl.co.za [169.1.5.128]
  5     8 ms     8 ms     7 ms  41.164.52.40
  6    29 ms    29 ms    29 ms  172.18.1.162
  7    35 ms    29 ms    29 ms  72.14.194.206
  8    58 ms    54 ms    51 ms  72.14.237.239
  9    41 ms    39 ms    61 ms  jnb01s07-in-f14.1e100.net [216.58.223.14]

Trace complete.

P2P also struggling. Trying to download Ubuntu torrent.
 
Pinging bras seems fine

Code: 
ping bras.afrihost.com -n 20

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=8ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=6ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63
Reply from 155.239.255.250: bytes=32 time=7ms TTL=63

Ping statistics for 155.239.255.250:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 6ms, Maximum = 21ms, Average = 7ms

Latency 9:00pm
Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3    10 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    54 ms    49 ms    48 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5     8 ms     8 ms     9 ms  optinet.ixp.capetown [196.10.140.145] 
  6     9 ms    11 ms    11 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  7    16 ms    17 ms    17 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8    27 ms    25 ms    28 ms  196.28.178.66 
  9    60 ms    62 ms    60 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10   184 ms    70 ms    45 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.

Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3     9 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4    89 ms   115 ms    91 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5     8 ms     8 ms     9 ms  optinet.ixp.capetown [196.10.140.145] 
  6    11 ms    12 ms    10 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  7    24 ms    23 ms    26 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8     9 ms     8 ms     9 ms  196.28.178.66 
  9    75 ms    65 ms    61 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 10     9 ms     8 ms     8 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11     9 ms     9 ms     9 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12     9 ms     8 ms    14 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

Latency 6:30pm
Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3     7 ms     8 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4     7 ms     7 ms     7 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5     8 ms     8 ms     8 ms  optinet.ixp.capetown [196.10.140.145] 
  6    12 ms    11 ms    11 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  7     8 ms     7 ms     8 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8     8 ms     8 ms     8 ms  196.28.178.66 
  9     8 ms     9 ms     7 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 10     9 ms     8 ms     8 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 11    12 ms     9 ms    10 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 12    10 ms     9 ms    10 ms  41-86-110-200.mweb.co.za [41.86.110.200] 

Trace complete.

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

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     *        *        *     Request timed out.
  3     9 ms     7 ms     7 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  4     7 ms     7 ms     9 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  5     9 ms     8 ms     8 ms  optinet.ixp.capetown [196.10.140.145] 
  6     9 ms    11 ms    12 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  7     8 ms     7 ms     8 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  8     9 ms     8 ms     8 ms  196.28.178.66 
  9     8 ms     8 ms     8 ms  cte-core-sw2.vwol.net [196.41.144.35] 
 10     9 ms     8 ms     9 ms  www.mweb.co.za [196.2.63.110] 

Trace complete.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X