Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
No errors whatsoever, that's the strange part.

Outlook just says "Send/Receive Complete", but the message just sits in the Outbox presumably due to some kind of a timeout. If I didn't know any better, I would have said Outlook was at fault, but both Vox and IS's Outgoing mail servers are working fine.

Very odd.
Does webmail also fail to send the mail?
 

Totempole

Expert Member
Joined
Sep 21, 2011
Messages
4,848
Very odd.
Does webmail also fail to send the mail?

I'm sure I can send fine using the Webmail of each email address.
One is a Vox Email and the other is with Afrihost.

Neither could send Via Outlook, so this isn't Webmail related. The problem is somewhere between Outlook and the Outgoing Mail server.
 

Tolstoy

Active Member
Joined
Aug 15, 2011
Messages
61
Servers pinging fine now. At least it's not high-latency for the normal 12 hours :)
 

LaraC

Honorary Master
Joined
Mar 11, 2014
Messages
42,675
I’ve used Zertop’s diagnostic tool do this test. Download speeds are great and latency is low.
Don’t know why so many have bad experiences but I like the performance I get on AfriGreen. :)

Code:
Local Tracert 

Tracing route to news24.co.za [41.86.110.143]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     *        *        *     Request timed out.
  3    46 ms    47 ms    46 ms  169-1-1-237.ip.afrihost.co.za [169.1.1.237] 
  4    51 ms    50 ms    50 ms  169-1-1-238.ip.afrihost.co.za [169.1.1.238] 
  5    51 ms    50 ms    52 ms  41.170.79.236 
  6    52 ms    51 ms    51 ms  mweb.jb1.napafrica.net [196.46.25.145] 
  7    67 ms    67 ms    68 ms  te0-7-0-3.vic-p-1.optinet.net [197.80.7.1] 
  8    66 ms    67 ms    67 ms  te0-0-0-0.cpt-p-2.optinet.net [197.84.4.46] 
  9    71 ms    70 ms    70 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
 10    71 ms    70 ms    68 ms  196.28.178.66 
 11    69 ms    68 ms    68 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 12    71 ms    70 ms    70 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 13    71 ms    70 ms    71 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 14    68 ms    69 ms    68 ms  41-86-110-143.mweb.co.za [41.86.110.143] 

Trace complete.
  
International Tracert 

Tracing route to thinkbroadband.com [80.249.99.130]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2     *        *        *     Request timed out.
  3    46 ms    46 ms    45 ms  169-1-1-249.ip.afrihost.co.za [169.1.1.249] 
  4    51 ms    49 ms    50 ms  169-1-1-250.ip.afrihost.co.za [169.1.1.250] 
  5    49 ms    49 ms    51 ms  41.170.79.236 
  6    51 ms    51 ms    51 ms  41.160.2.33 
  7    47 ms    45 ms    45 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37] 
  8   227 ms   227 ms   230 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2] 
  9   222 ms   204 ms   304 ms  if-1-0-0-4.core2.PV9-Lisbon.as6453.net [195.219.214.37] 
 10   230 ms   231 ms   230 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1] 
 11   230 ms   251 ms   231 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30] 
 12   226 ms   222 ms   222 ms  if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1] 
 13   224 ms   225 ms   225 ms  if-11-2.tcore1.L78-London.as6453.net [80.231.139.42] 
 14   227 ms   227 ms   227 ms  if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130] 
 15   227 ms   227 ms   235 ms  if-11-1.mse1.LVX-London.as6453.net [195.219.92.61] 
 16   225 ms   225 ms   225 ms  ix-11-2.mse1.LVX-London.as6453.net [195.219.92.34] 
 17   223 ms   223 ms   223 ms  te1-1-1-31.core-rs2.thdo.ncuk.net [80.249.97.85] 
 18   230 ms   230 ms   229 ms  www.thinkbroadband.com [80.249.99.130] 

Trace complete.
  
International Speedtest 
Downloaded 20.0 megabytes in 22 seconds. (923.02 KB/s)
  
Local Speedtest 
Downloaded 15.6 megabytes in 16 seconds. (982.02 KB/s)
  
  
  
  
Test End Timestamp 
2015-10-02 18:21:37.77
 

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,957
That's not cool at all :(
Do you have a traceroute that I can take a look at?

It's better now at ~250ms.
It's always the first hop on your network, don't have any latency issues on any other ISP.

Code:
Tracing route to 206-127-146-99.ncsoft.com [206.127.146.99]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    73 ms   109 ms    62 ms  169-1-1-237.ip.afrihost.co.za [169.1.1.237]
  4    47 ms    32 ms    45 ms  169-1-1-238.ip.afrihost.co.za [169.1.1.238]
  5    32 ms    32 ms    35 ms  41.170.79.236
  6    68 ms    37 ms    39 ms  41.160.2.33
  7    35 ms    37 ms    37 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  8   209 ms   208 ms   208 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
  9   179 ms   222 ms   329 ms  if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30]
 10   213 ms   214 ms   209 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   307 ms   217 ms   219 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   210 ms   209 ms   209 ms  if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 13   211 ms   210 ms   269 ms  if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 14   246 ms   288 ms   212 ms  if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 15   219 ms   208 ms   213 ms  195.219.83.102
 16   295 ms   234 ms   211 ms  ae-1-60.edge6.Frankfurt1.Level3.net [4.69.154.10]
 17   210 ms  ^C
 

AfriGenie

Afrihost
Company Rep
Joined
Oct 9, 2014
Messages
7,266
It's better now at ~250ms.
It's always the first hop on your network, don't have any latency issues on any other ISP.

Code:
Tracing route to 206-127-146-99.ncsoft.com [206.127.146.99]
over a maximum of 30 hops:

  1     3 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    73 ms   109 ms    62 ms  169-1-1-237.ip.afrihost.co.za [169.1.1.237]
  4    47 ms    32 ms    45 ms  169-1-1-238.ip.afrihost.co.za [169.1.1.238]
  5    32 ms    32 ms    35 ms  41.170.79.236
  6    68 ms    37 ms    39 ms  41.160.2.33
  7    35 ms    37 ms    37 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  8   209 ms   208 ms   208 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
  9   179 ms   222 ms   329 ms  if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30]
 10   213 ms   214 ms   209 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   307 ms   217 ms   219 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   210 ms   209 ms   209 ms  if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
 13   211 ms   210 ms   269 ms  if-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
 14   246 ms   288 ms   212 ms  if-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
 15   219 ms   208 ms   213 ms  195.219.83.102
 16   295 ms   234 ms   211 ms  ae-1-60.edge6.Frankfurt1.Level3.net [4.69.154.10]
 17   210 ms  ^C

Once the full IPC is deployed to the Cape, you should see that hiccup disappear for good! :)
 

dinkd

Well-Known Member
Joined
Oct 24, 2008
Messages
400
i find afri green to be unusable in the evenings.. p2p running at a whopping 60kb/s on an 8meg business uncapped line. like this every night for p2p and http and from around 1am the speed picks up to full speed.... think its time to move... my patience has run out with waiting.
 
Last edited:

Bryn

Doubleplusgood
Joined
Oct 29, 2010
Messages
16,894
The P2P performance on Afrigreen is becoming a serious pain in the arse. Does Afrigreen differentiate between capped/business and home users?
 

FatBoySlim

Expert Member
Joined
May 6, 2010
Messages
1,363
Gian must be laughing with his mouth full of teeth at these fools still testing this POC network, while he walked with millions.
 

al4bb

Well-Known Member
Joined
Nov 22, 2010
Messages
180
Last few days have not been too good:

Ping Test dropping out:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=56 time=24 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=56 time=23 ms
Request timeout for icmp_seq 3
64 bytes from 197.242.144.102: icmp_req=4 ttl=56 time=23 ms
64 bytes from 197.242.144.102: icmp_req=5 ttl=56 time=29 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=42 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=28 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=27 ms
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=28 ms

Not consistent - see lines 3 & 4

traceroute -n 197.242.144.102

1 192.168.1.1 1 ms 1 ms 1 ms
2 Request timed out * * *
3 169.1.1.2 26 ms 26 ms 123 ms
4 169.1.1.2 26 ms 70 ms 24 ms
5 41.170.79.2 19 ms 19 ms 19 ms
6 41.160.2.3 25 ms 26 ms 25 ms
7 196.223.14.3 49 ms 28 ms 29 ms
8 196.44.0.2 56 ms 50 ms
196.44.31.9 30 ms
9 196.44.31.9 31 ms
196.30.1.5 30 ms 28 ms
10 196.31.220.2 23 ms 23 ms 24 ms
11 196.31.63.2 24 ms 25 ms 24 ms
12 196.30.42.1 28 ms 29 ms 31 ms
13 197.242.144.1 24 ms 23 ms 24 ms
 
Last edited:

LaraC

Honorary Master
Joined
Mar 11, 2014
Messages
42,675
The P2P performance on Afrigreen is becoming a serious pain in the arse. Does Afrigreen differentiate between capped/business and home users?
Do I test at the correct times or am I just lucky?

Link.JPG
 

LaraC

Honorary Master
Joined
Mar 11, 2014
Messages
42,675
Last few days have not been too good:
/snip
Did the same test.
Code:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Users\Lara>ping 197.242.144.102

Pinging 197.242.144.102 with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56
Reply from 197.242.144.102: bytes=32 time=49ms TTL=56
Reply from 197.242.144.102: bytes=32 time=49ms TTL=56
Reply from 197.242.144.102: bytes=32 time=50ms TTL=56

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

C:\Users\Lara>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=46ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57
Reply from 8.8.8.8: bytes=32 time=44ms TTL=57
Reply from 8.8.8.8: bytes=32 time=45ms TTL=57

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 44ms, Maximum = 46ms, Average = 45ms
 
Status
Not open for further replies.
Top