Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
Hey guys,

Been moved over to Afrigreen yesterday (due to the auth issues on the old Afrihost network). However, I do have a question that I cant answer for myself.

:confused: Since this is a new network that was planned with enough capacity for now (and next year) and (AFAIK) the complete Afrihost user pool is still not on it (as Afriman said in Post 6310) and it should be as fast as possible, why am I seeing higher latency on a tracert done minutes apart? Specifically looking at ping responce times, not routes. Routes is another question alltogether.
Not complaining, only asking.

WEBAFRICA:

1 <1 ms <1 ms <1 ms aggregator.mikrotik.thingy [192.x.x.x]
2 <1 ms <1 ms <1 ms my.local.blinking.light.device [192.x.x.x]
3 12 ms 11 ms 11 ms 196-210-158-129.dynamic.isadsl.co.za [196.210.158.129]
4 22 ms 20 ms 31 ms 196.38.72.229
5 30 ms 25 ms 25 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 44 ms 33 ms 28 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 26 ms 26 ms 27 ms 168.209.1.169
8 20 ms 25 ms 20 ms mi-za-rba-epe1-te2-2-304.ip.isnet.net [168.209.86.250]
9 30 ms 25 ms 20 ms 197.96.148.73
10 31 ms 25 ms 25 ms 196.34.90.125
11 21 ms 20 ms 19 ms CORE.GP-MR-HER-MEE-1.TO.GP-RV-DFA-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.83]
12 28 ms 28 ms 28 ms 41.66.152.58
13 34 ms 29 ms 29 ms cp03-pta.za-dns.com [196.46.186.130]

Trace complete.

AFRIGREEN:

1 <1 ms <1 ms <1 ms aggregator.mikrotik.thingy [192.x.x.x]
2 1 ms 1 ms 1 ms local.security.device [192.x.x.x]
3 3 ms 2 ms 1 ms other.local.blinking.light.device[192.x.x.x]
4 271 ms 267 ms 222 ms 169-0-31-1.ip.afrihost.co.za [169.0.31.1]
5 356 ms 280 ms 348 ms 169-1-5-5.ip.afrihost.co.za [169.1.5.5]
6 289 ms 418 ms 321 ms 169-1-5-6.ip.afrihost.co.za [169.1.5.6]
7 314 ms 207 ms 172 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52]
8 364 ms 427 ms 298 ms aitonline1.jb1.napafrica.net [196.46.25.211]
9 207 ms 196 ms 295 ms cp03-pta.za-dns.com [196.46.186.130]

Trace complete.
 
Last edited:
Hey guys,
Experiencing major issues on AfriGreen at the moment.
Hop 3 is showing major issues.
Been dropped off work calls multiple times - this is NOT good.
Please advise.

Code: 
Target Name: www.afrihost.com
         IP: 41.181.185.18
  Date/Time: 19/10/2015 10:51:00 to 19/10/2015 10:51:38

Hop Sent Err  PL% Min  Max  Avg  Host Name / [IP]
 1    16   0  0.0   1   78   15  home.gateway.home.gateway [192.168.1.254]
 2    16   0  0.0   9  213   25  169-0-62-1.ip.afrihost.co.za [169.0.62.1]
[B] 3    14   2 14.3  15 2849 1680  169-1-5-105.ip.afrihost.co.za [169.1.5.105]
[/B] 4    16   0  0.0  12  127   34  169-1-5-106.ip.afrihost.co.za [169.1.5.106]
 5    16   0  0.0  11  101   28  169-1-5-128.ip.afrihost.co.za [169.1.5.128]
 6    16   0  0.0  12  127   25  [41.164.52.40]
 7    16   0  0.0  33  156   65  [172.18.16.3]
 8    15   0  0.0  35  182   70  mtnns-2.jinx.net.za [196.223.14.31]
 9    15   0  0.0  35  176   58  jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10    15   0  0.0  35  156   65  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11    16   0  0.0  36  125   58  www.afrihost.com [41.181.185.18]

Seeing the same on bras.afrihost.com
Code: 
Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 19/10/2015 11:02:28 to 19/10/2015 11:03:16

Hop Sent Err   PL% Min  Max Avg  Host Name / [IP]
 1    20   0   0.0   1   13   2  home.gateway.home.gateway [192.168.1.254]
 2    20   0   0.0   9   13  10  169-0-62-1.ip.afrihost.co.za [169.0.62.1]
 3    20   0   0.0  11 1082 209  169-1-5-105.ip.afrihost.co.za [169.1.5.105]
 4    20   0   0.0  12   17  13  169-1-5-118.ip.afrihost.co.za [169.1.5.118]
 5    20   0   0.0  11   69  16  169-1-5-128.ip.afrihost.co.za [169.1.5.128]
 6    20   0   0.0  12   32  13  [41.164.52.40]
 7    20   0   0.0  32   39  33  [172.18.1.162]
 8    20   0   0.0  32   44  34  [41.160.2.69]
 9    20   0   0.0  32   40  35  rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
10    20  20 100.0   0    0   0   [-]
11    20  20 100.0   0    0   0   [-]
12    20  20 100.0   0    0   0   [-]
13    20  20 100.0   0    0   0   [-]
14    20  20 100.0   0    0   0   [-]
15    20  20 100.0   0    0   0   [-]
16    20  20 100.0   0    0   0   [-]
17    20  20 100.0   0    0   0   [-]
18    20  20 100.0   0    0   0   [-]
19    20  20 100.0   0    0   0   [-]
20    20  20 100.0   0    0   0   [-]
21    20  20 100.0   0    0   0   [-]
22    20  20 100.0   0    0   0   [-]
23    20  20 100.0   0    0   0   [-]
24    20  20 100.0   0    0   0   [-]
25    20  20 100.0   0    0   0   [-]
26    20  20 100.0   0    0   0   [-]
27    20  20 100.0   0    0   0   [-]
28    20  20 100.0   0    0   0   [-]
29    20  20 100.0   0    0   0   [-]
30    20  20 100.0   0    0   0   [-]
31    20  20 100.0   0    0   0   [-]
32    20  20 100.0   0    0   0   [-]
33    20  20 100.0   0    0   0   [-]
34    20  20 100.0   0    0   0   [-]
35    20  20 100.0   0    0   0   [-]

Destination not reached in 35 hops
 
Last edited:
abjater said:
Hey guys,

Been moved over to Afrigreen yesterday (due to the auth issues on the old Afrihost network). However, I do have a question that I cant answer for myself.

:confused: Since this is a new network that was planned with enough capacity for now (and next year) and (AFAIK) the complete Afrihost user pool is still not on it (as Afriman said in Post 6310) and it should be as fast as possible, why am I seeing higher latency on a tracert done minutes apart? Specifically looking at ping responce times, not routes. Routes is another question alltogether.
Not complaining, only asking.

WEBAFRICA:

1 <1 ms <1 ms <1 ms aggregator.mikrotik.thingy [192.x.x.x]
2 <1 ms <1 ms <1 ms my.local.blinking.light.device [192.x.x.x]
3 12 ms 11 ms 11 ms 196-210-158-129.dynamic.isadsl.co.za [196.210.158.129]
4 22 ms 20 ms 31 ms 196.38.72.229
5 30 ms 25 ms 25 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
6 44 ms 33 ms 28 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]
7 26 ms 26 ms 27 ms 168.209.1.169
8 20 ms 25 ms 20 ms mi-za-rba-epe1-te2-2-304.ip.isnet.net [168.209.86.250]
9 30 ms 25 ms 20 ms 197.96.148.73
10 31 ms 25 ms 25 ms 196.34.90.125
11 21 ms 20 ms 19 ms CORE.GP-MR-HER-MEE-1.TO.GP-RV-DFA-MEE-1.DFA.P2P.10G.za.africainx.net [41.84.12.83]
12 28 ms 28 ms 28 ms 41.66.152.58
13 34 ms 29 ms 29 ms cp03-pta.za-dns.com [196.46.186.130]

Trace complete.

AFRIGREEN:

1 <1 ms <1 ms <1 ms aggregator.mikrotik.thingy [192.x.x.x]
2 1 ms 1 ms 1 ms local.security.device [192.x.x.x]
3 3 ms 2 ms 1 ms other.local.blinking.light.device[192.x.x.x]
4 271 ms 267 ms 222 ms 169-0-31-1.ip.afrihost.co.za [169.0.31.1]
5 356 ms 280 ms 348 ms 169-1-5-5.ip.afrihost.co.za [169.1.5.5]
6 289 ms 418 ms 321 ms 169-1-5-6.ip.afrihost.co.za [169.1.5.6]
7 314 ms 207 ms 172 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52]
8 364 ms 427 ms 298 ms aitonline1.jb1.napafrica.net [196.46.25.211]
9 207 ms 196 ms 295 ms cp03-pta.za-dns.com [196.46.186.130]

Trace complete.
Click to expand...

Looks like you are routing these tests differently, possibly using pass through. It would be best to test these accounts by using the router settings, rather than passthrough. Accounts on passthrough generally perform differently, and it can be a misleading test :(
 
@ steel_dog

Why is the latency on your home network so high? I've been told that it should be close to 0ms.
 
steel_dog said:
Hey guys,
Experiencing major issues on AfriGreen at the moment.
Hop 3 is showing major issues.
Been dropped off work calls multiple times - this is NOT good.
Please advise.

Code: 
Target Name: www.afrihost.com
         IP: 41.181.185.18
  Date/Time: 19/10/2015 10:51:00 to 19/10/2015 10:51:38

Hop Sent Err  PL% Min  Max  Avg  Host Name / [IP]
 1    16   0  0.0   1   78   15  home.gateway.home.gateway [192.168.1.254]
 2    16   0  0.0   9  213   25  169-0-62-1.ip.afrihost.co.za [169.0.62.1]
[B] 3    14   2 14.3  15 2849 1680  169-1-5-105.ip.afrihost.co.za [169.1.5.105]
[/B] 4    16   0  0.0  12  127   34  169-1-5-106.ip.afrihost.co.za [169.1.5.106]
 5    16   0  0.0  11  101   28  169-1-5-128.ip.afrihost.co.za [169.1.5.128]
 6    16   0  0.0  12  127   25  [41.164.52.40]
 7    16   0  0.0  33  156   65  [172.18.16.3]
 8    15   0  0.0  35  182   70  mtnns-2.jinx.net.za [196.223.14.31]
 9    15   0  0.0  35  176   58  jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10    15   0  0.0  35  156   65  jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
11    16   0  0.0  36  125   58  www.afrihost.com [41.181.185.18]

Seeing the same on bras.afrihost.com
Code: 
Target Name: bras.afrihost.com
         IP: 155.239.255.250
  Date/Time: 19/10/2015 11:02:28 to 19/10/2015 11:03:16

Hop Sent Err   PL% Min  Max Avg  Host Name / [IP]
 1    20   0   0.0   1   13   2  home.gateway.home.gateway [192.168.1.254]
 2    20   0   0.0   9   13  10  169-0-62-1.ip.afrihost.co.za [169.0.62.1]
 3    20   0   0.0  11 1082 209  169-1-5-105.ip.afrihost.co.za [169.1.5.105]
 4    20   0   0.0  12   17  13  169-1-5-118.ip.afrihost.co.za [169.1.5.118]
 5    20   0   0.0  11   69  16  169-1-5-128.ip.afrihost.co.za [169.1.5.128]
 6    20   0   0.0  12   32  13  [41.164.52.40]
 7    20   0   0.0  32   39  33  [172.18.1.162]
 8    20   0   0.0  32   44  34  [41.160.2.69]
 9    20   0   0.0  32   40  35  rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za [196.43.25.137]
10    20  20 100.0   0    0   0   [-]
11    20  20 100.0   0    0   0   [-]
12    20  20 100.0   0    0   0   [-]
13    20  20 100.0   0    0   0   [-]
14    20  20 100.0   0    0   0   [-]
15    20  20 100.0   0    0   0   [-]
16    20  20 100.0   0    0   0   [-]
17    20  20 100.0   0    0   0   [-]
18    20  20 100.0   0    0   0   [-]
19    20  20 100.0   0    0   0   [-]
20    20  20 100.0   0    0   0   [-]
21    20  20 100.0   0    0   0   [-]
22    20  20 100.0   0    0   0   [-]
23    20  20 100.0   0    0   0   [-]
24    20  20 100.0   0    0   0   [-]
25    20  20 100.0   0    0   0   [-]
26    20  20 100.0   0    0   0   [-]
27    20  20 100.0   0    0   0   [-]
28    20  20 100.0   0    0   0   [-]
29    20  20 100.0   0    0   0   [-]
30    20  20 100.0   0    0   0   [-]
31    20  20 100.0   0    0   0   [-]
32    20  20 100.0   0    0   0   [-]
33    20  20 100.0   0    0   0   [-]
34    20  20 100.0   0    0   0   [-]
35    20  20 100.0   0    0   0   [-]

Destination not reached in 35 hops
Click to expand...

I am seeing your first tests showing a max of 78ms to the router, which is very troubling. It could be compound, cos I see that the second hop is pretty high as well.

Your BRAS ping seems a little better, but we're definitely not seeing this in general. YOu are being routed to the correct IPC, so all check out as it should.

Can you please PM your username, let's get you on the phone and figure out what could be happening here :)
 
LaraC said:
@ steel_dog

Why is the latency on your home network so high? I've been told that it should be close to 0ms.
Click to expand...

Anything around 1ms is acceptable. You sometimes see around 5ms max on WiFi connections. Anything above that would be an issue of concern :(
 
Afrigreen broken in Pietermaritzburg

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=1361 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=1517 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=1853 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=2881 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=3796 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=2744 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=1156 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=2678 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=3592 ms



Afrihost:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=33 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=31 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=34 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=32 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=55 time=26 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=55 time=26 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=55 time=25 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=55 time=26 ms

Better, but still getting timeouts
 
AfriMan said:
Anything around 1ms is acceptable. You sometimes see around 5ms max on WiFi connections. Anything above that would be an issue of concern :(
Click to expand...

@LaraC / AfriMan - Agree. With this Billion router (8800NXL) WAN latency plays back into WLAN latency. Billion can't answer why, but it's noted through their 8800 range. Anyway here's a tracert from a LAN connection. Same problem.

@Afriman - PM sent.

Code: 
                                                       My traceroute  [v0.85]
N54L (0.0.0.0)                                                                                             Mon Oct 19 11:20:07 2015
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                       Packets               Pings
 Host                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. home.gateway.home.gateway                                         0.0%    12    0.4   0.6   0.4   0.9   0.0
 2. 169-0-62-1.ip.afrihost.co.za                                      0.0%    12    8.6   8.8   8.5   9.5   0.0
[B] 3. 169-1-5-105.ip.afrihost.co.za                                     9.1%    11  1449. 802.7 347.3 1449. 399.7
[/B] 4. 169-1-5-118.ip.afrihost.co.za                                     0.0%    11   11.9  11.7  11.3  12.5   0.0
 5. 169-1-5-128.ip.afrihost.co.za                                     0.0%    11   10.7  10.9  10.6  11.4   0.0
 6. 41.164.52.40                                                      0.0%    11   12.0  11.8  11.3  12.6   0.0
 7. 172.18.1.162                                                      0.0%    11   31.6  31.7  31.3  32.5   0.0
 8. 41.160.2.69                                                       0.0%    11   32.8  33.0  32.2  35.8   0.8
 9. rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za                    0.0%    11   32.0  32.6  32.0  33.4   0.0
10. ???

Another trace to bras. Formatting better :)
Code: 
Start: Mon Oct 19 11:27:49 2015
HOST: N54L                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- home.gateway.home.gateway                       0.0%   100    0.7   0.6   0.4   0.9   0.0
  2.|-- 169-0-62-1.ip.afrihost.co.za                    0.0%   100    8.6   8.8   8.2   9.4   0.0
  3.|-- 169-1-5-105.ip.afrihost.co.za                   0.0%   100   11.5 225.6  10.7 3296. 632.4
  4.|-- 169-1-5-118.ip.afrihost.co.za                   0.0%   100   11.7  11.8  11.0  13.5   0.3
  5.|-- 169-1-5-128.ip.afrihost.co.za                   0.0%   100   11.0  11.6  10.2  35.2   3.7
  6.|-- 41.164.52.40                                    0.0%   100   11.5  11.7  11.2  12.2   0.0
  7.|-- 172.18.1.162                                    0.0%   100   32.1  31.7  31.0  36.2   0.5
  8.|-- 41.160.2.69                                     0.0%   100   32.6  32.7  31.7  36.8   0.8
  9.|-- rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za  0.0%   100   32.4  32.7  31.8  35.9   0.6
 10.|-- ???                                            100.0   100    0.0   0.0   0.0   0.0   0.0
 
Last edited:
For the last few weeks, I have had numerous posts/complaints regarding the poor performance from AH between the 6-11pm slots on a daily basis.

BUT.......

So far since Thursday I have had no issues at all. Usenet was working at full speed. Diablo III was playing like at a dream, although slightly slower than a few months ago. Currently at about 250ms. In past it was between 198-208ms.

Thanks Guys
 
al4bb said:
Afrigreen broken in Pietermaritzburg

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=55 time=1361 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=55 time=1517 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=55 time=1853 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=55 time=2881 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=57 time=3796 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=57 time=2744 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=57 time=1156 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=57 time=2678 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=57 time=3592 ms



Afrihost:

Ping Test:

ping 197.242.144.102

64 bytes from 197.242.144.102: icmp_req=1 ttl=58 time=33 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=58 time=31 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=58 time=34 ms
Request timeout for icmp_seq 4
64 bytes from 197.242.144.102: icmp_req=5 ttl=58 time=32 ms


ping 8.8.8.8

64 bytes from 8.8.8.8: icmp_req=1 ttl=55 time=26 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=55 time=26 ms
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_req=4 ttl=55 time=25 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=55 time=26 ms

Better, but still getting timeouts
Click to expand...

Can I see the whole traceroute from AfriGreen?
 
steel_dog said:
@LaraC / AfriMan - Agree. With this Billion router (8800NXL) WAN latency plays back into WLAN latency. Billion can't answer why, but it's noted through their 8800 range. Anyway here's a tracert from a LAN connection. Same problem.

@Afriman - PM sent.

Code: 
                                                       My traceroute  [v0.85]
N54L (0.0.0.0)                                                                                             Mon Oct 19 11:20:07 2015
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                                       Packets               Pings
 Host                                                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. home.gateway.home.gateway                                         0.0%    12    0.4   0.6   0.4   0.9   0.0
 2. 169-0-62-1.ip.afrihost.co.za                                      0.0%    12    8.6   8.8   8.5   9.5   0.0
[B] 3. 169-1-5-105.ip.afrihost.co.za                                     9.1%    11  1449. 802.7 347.3 1449. 399.7
[/B] 4. 169-1-5-118.ip.afrihost.co.za                                     0.0%    11   11.9  11.7  11.3  12.5   0.0
 5. 169-1-5-128.ip.afrihost.co.za                                     0.0%    11   10.7  10.9  10.6  11.4   0.0
 6. 41.164.52.40                                                      0.0%    11   12.0  11.8  11.3  12.6   0.0
 7. 172.18.1.162                                                      0.0%    11   31.6  31.7  31.3  32.5   0.0
 8. 41.160.2.69                                                       0.0%    11   32.8  33.0  32.2  35.8   0.8
 9. rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za                    0.0%    11   32.0  32.6  32.0  33.4   0.0
10. ???

Another trace to bras. Formatting better :)
Code: 
Start: Mon Oct 19 11:27:49 2015
HOST: N54L                                           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- home.gateway.home.gateway                       0.0%   100    0.7   0.6   0.4   0.9   0.0
  2.|-- 169-0-62-1.ip.afrihost.co.za                    0.0%   100    8.6   8.8   8.2   9.4   0.0
  3.|-- 169-1-5-105.ip.afrihost.co.za                   0.0%   100   11.5 225.6  10.7 3296. 632.4
  4.|-- 169-1-5-118.ip.afrihost.co.za                   0.0%   100   11.7  11.8  11.0  13.5   0.3
  5.|-- 169-1-5-128.ip.afrihost.co.za                   0.0%   100   11.0  11.6  10.2  35.2   3.7
  6.|-- 41.164.52.40                                    0.0%   100   11.5  11.7  11.2  12.2   0.0
  7.|-- 172.18.1.162                                    0.0%   100   32.1  31.7  31.0  36.2   0.5
  8.|-- 41.160.2.69                                     0.0%   100   32.6  32.7  31.7  36.8   0.8
  9.|-- rrba-ip-lir-1-gig-0-0-0-102.telkom-ipnet.co.za  0.0%   100   32.4  32.7  31.8  35.9   0.6
 10.|-- ???                                            100.0   100    0.0   0.0   0.0   0.0   0.0
Click to expand...

Got your details - we'll get someone on the horn to help you out :)
 
HP_Exarkun said:
For the last few weeks, I have had numerous posts/complaints regarding the poor performance from AH between the 6-11pm slots on a daily basis.

BUT.......

So far since Thursday I have had no issues at all. Usenet was working at full speed. Diablo III was playing like at a dream, although slightly slower than a few months ago. Currently at about 250ms. In past it was between 198-208ms.

Thanks Guys
Click to expand...

Awesome :)
 
Network probs atm?

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\Users\Igor III>ping google.com

Pinging google.com [197.80.128.54] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 197.80.128.54:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Igor III>ping telkom.co.za -t

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=64ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=15ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=22ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=15ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=15ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=15ms TTL=244
Reply from 196.43.22.222: bytes=32 time=22ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=26ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=27ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=27ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=22ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=21ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=15ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=22ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=18ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=24ms TTL=244
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=16ms TTL=244
Reply from 196.43.22.222: bytes=32 time=22ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=20ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244
Reply from 196.43.22.222: bytes=32 time=19ms TTL=244
Reply from 196.43.22.222: bytes=32 time=29ms TTL=244
Reply from 196.43.22.222: bytes=32 time=25ms TTL=244
Reply from 196.43.22.222: bytes=32 time=17ms TTL=244

Ping statistics for 196.43.22.222:
Packets: Sent = 84, Received = 74, Lost = 10 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 64ms, Average = 19ms
Control-C
^C
C:\Users\Igor III>
 
AfriMan said:
Can I see the whole traceroute from AfriGreen?
Click to expand...

I didn't post the traceroute as every node timeout.

Here's a current one however:

C:\Windows\system32>tracert www.afrihost.co.za

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 2165 ms 2818 ms 2829 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 2936 ms 3190 ms 3939 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 * 3476 ms 431 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 1352 ms 2546 ms 2958 ms 41.162.84.192
7 * 3830 ms 2442 ms 172.18.1.59
8 1908 ms 1912 ms 2273 ms mtnns-2.jinx.net.za [196.223.14.31]
9 2446 ms 2782 ms 3074 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 * * * Request timed out.
11 1660 ms 263 ms 365 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
al4bb said:
I didn't post the traceroute as every node timeout.

Here's a current one however:

C:\Windows\system32>tracert www.afrihost.co.za

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

1 <1 ms 1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 2165 ms 2818 ms 2829 ms 169-1-5-173.ip.afrihost.co.za [169.1.5.173]
4 2936 ms 3190 ms 3939 ms 169-1-5-174.ip.afrihost.co.za [169.1.5.174]
5 * 3476 ms 431 ms 169-1-5-204.ip.afrihost.co.za [169.1.5.204]
6 1352 ms 2546 ms 2958 ms 41.162.84.192
7 * 3830 ms 2442 ms 172.18.1.59
8 1908 ms 1912 ms 2273 ms mtnns-2.jinx.net.za [196.223.14.31]
9 2446 ms 2782 ms 3074 ms jh-cr-1.za-jh-pr-1.za-a.mtnns.net [196.44.0.73]
10 * * * Request timed out.
11 1660 ms 263 ms 365 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
Click to expand...

Can you please send me a PM with your Afrigreen username quickly, the Team wants to look into this quickly.

EDIT: Would you mind also pinging bras.afrihost.com and posting the results here.
 
Last edited:
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X