Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Would you mind testing it with MyBB Speed Test? I'm also getting higher latency when testing with Speedtest.net.

Interesting:

300056293.png

And on SAIX:

Last Result:
Download Speed: 1790 kbps (223.8 KB/sec transfer rate)
Upload Speed: 428 kbps (53.5 KB/sec transfer rate)
Latency: 60 ms
10/19/2015, 5:53:27 PM
 
That definitely shouldn't be the case... Which services have you tried out?

Twitch and Ustream mostly. It's been better than usual lately, but it's still nowhere near how good something like WebAfrica is (where I can stream source 1080p60 with no buffering).

D2AqAsy.jpg
^This was on the homepage, so it's probably on their best servers.

MTN Business speed test:
Download Speed: 6809 kbps (851.1 KB/sec transfer rate)
Upload Speed: 918 kbps (114.8 KB/sec transfer rate)
Latency: 35 ms
Jitter: 1 ms
19/10/2015, 17:44:44

MyBB Cape Town
Download Speed: 6817 kbps (852.1 KB/sec transfer rate)
Upload Speed: 922 kbps (115.3 KB/sec transfer rate)
Latency: 48 ms
Jitter: 5 ms
19/10/2015, 17:46:21

As you can see, the line is more than capable, but, for some reason, the stream refuses to use the available bandwidth and just lags.

EDIT: Oh and after a while the streams just stop sometimes.
 
Last edited:
i think this got lost in the speedtests, could one of Afri* people confirm if DNS is down again please? Not getting any response from 169.1.1.1/2 for a good half hour now...
 
Here you go. :)
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>tracert mybroadband.co.uk

Tracing route to mybroadband.co.uk [72.52.4.91]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    32 ms    31 ms    31 ms  cpt-up1.net.afrihost.co.za [169.1.5.81]
  4    32 ms    31 ms    31 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5    24 ms    23 ms    24 ms  cpt-net1.net.afrihost.co.za [169.1.5.128]
  6    23 ms    24 ms    24 ms  41.164.52.40
  7    52 ms    52 ms    51 ms  172.18.16.3
  8    70 ms    50 ms    50 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  9   212 ms   212 ms   212 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10   303 ms   169 ms   169 ms  if-1-0-0-5.core2.PV9-Lisbon.as6453.net [195.219.214.53]
 11   216 ms   215 ms   215 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 12   202 ms   201 ms   202 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   210 ms   211 ms   211 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 14   205 ms   204 ms   204 ms  if-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
 15   205 ms   205 ms   205 ms  if-19-2.thar1.LD5-Slough.as6453.net [80.231.48.30]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20  ^C

from what i can see, they peer with their upstream provider in JHB... - so traffic will go from CPT to JHB into their upstream's network, who then sends it back to CPT to send out through whatever cable they're using....

This is an issue that we are aware of, and have brought to the attention of our Upstream provider, it will be corrected on our side. :)
 
from what i can see, they peer with their upstream provider in JHB... - so traffic will go from CPT to JHB into their upstream's network, who then sends it back to CPT to send out through whatever cable they're using....

Interesting... Hop 9 looks a bit weird to me ...

Code:
Tracing route to nc1.eu [178.62.201.239]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms     7 ms  169-0-29-1.ip.afrihost.co.za [169.0.29.1]
  3     *        *        *     Request timed out.
  4    23 ms    22 ms    22 ms  cpt-rx1.net.afrihost.co.za [169.1.5.94]
  5    22 ms    21 ms    22 ms  169-1-5-128.ip.afrihost.co.za [169.1.5.128]
  6    23 ms    23 ms    22 ms  41.164.52.40
  7    50 ms    50 ms    50 ms  172.18.16.3
  8    42 ms    42 ms    41 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  9   213 ms   213 ms   213 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
 10   210 ms   170 ms   184 ms  if-1-0-0-4.core2.PV9-Lisbon.as6453.net [195.219.214.37]
 11   202 ms   204 ms   203 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 12   213 ms   213 ms   220 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 13   209 ms   209 ms   208 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 14   203 ms   203 ms   203 ms  if-8-2.tcore2.AV2-Amsterdam.as6453.net [80.231.131.6]
 15   199 ms   199 ms   199 ms  if-11-2.tcore1.AD1-Amsterdam.as6453.net [80.231.152.26]
 16   208 ms   208 ms   207 ms  80.231.80.6
 17   204 ms   205 ms   204 ms  5.101.110.230
 18   207 ms   207 ms   207 ms  do1.nc1.eu [178.62.201.239]

Trace complete.

@Lara, thanks.
 
i think this got lost in the speedtests, could one of Afri* people confirm if DNS is down again please? Not getting any response from 169.1.1.1/2 for a good half hour now...
Pinged it and it worked.

Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 169.1.1.1

Pinging 169.1.1.1 with 32 bytes of data:
Reply from 169.1.1.1: bytes=32 time=46ms TTL=59
Reply from 169.1.1.1: bytes=32 time=46ms TTL=59
Reply from 169.1.1.1: bytes=32 time=46ms TTL=59
Reply from 169.1.1.1: bytes=32 time=46ms TTL=59

Ping statistics for 169.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 46ms, Average = 46ms

C:\Users\Lara>ping 169.1.1.2

Pinging 169.1.1.2 with 32 bytes of data:
Reply from 169.1.1.2: bytes=32 time=44ms TTL=59
Reply from 169.1.1.2: bytes=32 time=43ms TTL=59
Reply from 169.1.1.2: bytes=32 time=43ms TTL=59
Reply from 169.1.1.2: bytes=32 time=43ms TTL=59

Ping statistics for 169.1.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 43ms, Maximum = 44ms, Average = 43ms
 
Pinged it and it worked.

yes, i could also ping it, and i could also telnet to port 53 and get a response.. it was resolving anything though....

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to ns1.afrihost.co.za timed-out


BUT it just seems to have started working again.....
 
AfriGenie, can you confirm if all CPT people have been moved to Afrigreen? I have a few clients I wanted to move over, but that makes no sense if its all been done already...

I just had a quick login with the @afrihost.co.za account and that's still going through MTN....
 
Sorry I switched to the vanilla account to test and did not switch back.

Its only a 2mb line 100gb Capped account

Here is my Afrigreen account on MyBB Speedtest
 
Sorry I switched to the vanilla account to test and did not switch back.

Its only a 2mb line 100gb Capped account

Here is my Afrigreen account on MyBB Speedtest

That still looks like its a legacy @afrihost.co.za account... Did your Afrigreen account authenticate at all?
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X