Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Oh dear. Are you guys sure you are ready to load this network up tomorrow? This is my 10Mbps line running on Afrigreen at the moment.

The new Durban IPC seems to have had little effect or am I mistaken?

300913327.png
 
PeerBlock doesn't like your address. :D

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

C:\Users\Lara>ping nc1.eu

Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=194ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43

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

haha, that's my gaming server.
 
PeerBlock doesn't like your address. :D

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

C:\Users\Lara>ping nc1.eu

Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=194ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43

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

I look at your results as the best result that someone can have on Afrigreen :p
 
Oh dear. Are you guys sure you are ready to load this network up tomorrow? This is my 10Mbps line running on Afrigreen at the moment.

The new Durban IPC seems to have had little effect or am I mistaken?

View attachment 308224

Oh, and here is the trace route. Pings all good but what are those timeouts? With such good latency why is the throughput less than 10% of line capacity?

Trace Test:

traceroute -n 197.242.144.102

1 192.168.1.1 * * *
2 Request timed out * * *
3 169.1.5.162 12.76 ms 10.654 ms 9.871 ms
4 169.1.5.204 8.834 ms 8.95 ms 9.562 ms
5 41.162.84.192 9.542 ms 9.74 ms 10.273 ms
6 172.18.1.59 18.558 ms 18.234 ms 58.271 ms
7 196.223.14.31 20.601 ms 136.872 ms 19.984 ms
8 196.44.0.223 32.368 ms 22.327 ms
Request timed out *
9 196.44.31.99 22.372 ms 21.586 ms
Request timed out *
10 196.30.1.53 22.083 ms
196.31.220.6 21.825 ms
Request timed out *
11 196.31.220.27 22.694 ms 22.619 ms
196.31.220.21 22.43 ms
12 196.31.63.202 21.157 ms 21.539 ms
Request timed out *
13 196.30.42.132 21.285 ms 25.182 ms 22.814 ms
14 197.242.144.102 22.466 ms 21.019 ms 22.132 ms


traceroute -n 8.8.8.8

1 192.168.1.1 * * *
2 Request timed out * * *
3 169.1.5.162 9.231 ms 8.477 ms 10.456 ms
4 169.1.5.204 9.126 ms 8.376 ms 10.558 ms
5 41.162.84.192 9.746 ms 11.875 ms 11.996 ms
6 172.18.1.162 18.204 ms 17.63 ms 17.552 ms
7 72.14.194.206 18.457 ms 19.43 ms
Request timed out *
8 72.14.239.53 22.51 ms
72.14.239.117 19.476 ms 19.45 ms
9 8.8.8.8 18.662 ms 18.52 ms 21.407 ms
 
PeerBlock doesn't like your address. :D

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

C:\Users\Lara>ping nc1.eu

Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=194ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43
Reply from 178.62.201.239: bytes=32 time=195ms TTL=43

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

I beat yours :)


Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=192ms TTL=46
Reply from 178.62.201.239: bytes=32 time=188ms TTL=46
Reply from 178.62.201.239: bytes=32 time=188ms TTL=46
Reply from 178.62.201.239: bytes=32 time=187ms TTL=46

Ping statistics for 178.62.201.239:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 187ms, Maximum = 192ms, Average = 188ms
 
Afrigreen not performing as well today as the last few days.

Downloads slightly bit slower today. Browsing while downloading (issue that I was having before) is now back too. Can't stream videos on Facebook, Vimeo or youtube while download is running.

Edit*

Just tried watching video on vimeo with no download running and I can't even watch video without pausing it and letting it buffer. A 2minute video has taken me 15 minutes to watch.

Traceroute and speed tests all look fine though.

What are you general connection stats like? We're not really making changes to the network, the guys are mostly prepping for cutover.
 
Oh dear. Are you guys sure you are ready to load this network up tomorrow? This is my 10Mbps line running on Afrigreen at the moment.

The new Durban IPC seems to have had little effect or am I mistaken?

View attachment 308224

The Durban IPC is live and should be working well. That's definitely not looking good. Will check in with the team :(
 
Last edited:
@ AfriMan

Why is there a difference in speed between the different speed test sites?
 
I look at your results as the best result that someone can have on Afrigreen :p
I beat yours :)


Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=192ms TTL=46
Reply from 178.62.201.239: bytes=32 time=188ms TTL=46
Reply from 178.62.201.239: bytes=32 time=188ms TTL=46
Reply from 178.62.201.239: bytes=32 time=187ms TTL=46

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


Code:
C:\WINDOWS\System32>ping nc1.eu

Pinging nc1.eu [178.62.201.239] with 32 bytes of data:
Reply from 178.62.201.239: bytes=32 time=169ms TTL=48
Reply from 178.62.201.239: bytes=32 time=169ms TTL=48
Reply from 178.62.201.239: bytes=32 time=168ms TTL=48
Reply from 178.62.201.239: bytes=32 time=168ms TTL=48

Ping statistics for 178.62.201.239:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 168ms, Maximum = 169ms, Average = 168ms
I like Cape Town ...
 
The Durban IPC is live and should be working well. That's definitely not looking good. Will check in with the team :(

Thanks Afriman. Best to get to the bottom of the problem before a whole lot of people turn up on the same network.

Just run a SAIX speedtest which gives a similar result:

Last Result:
Download Speed: 709 kbps (88.6 KB/sec transfer rate)
Upload Speed: 480 kbps (60 KB/sec transfer rate)
Latency: 22 ms
20 October 2015 at 5:05:35 PM SAST
 
OK so apparently there’s an advanced network menu somewhere under network on the settings tab

the advanced option is only for network settings like auto network or manual settings. There is no option that has to do with in game latency.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X