Afrihost POC Network - Afrigreen Feedback

Slaught3r · Sep 20, 2015

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 366 ms 366 ms 278 ms 169-0-5-1-access.afrihost.co.za [169.0.5.1]
3 229 ms 239 ms 252 ms 41.170.79.230
4 334 ms 307 ms 364 ms 41.170.79.236
5 468 ms 469 ms 468 ms google.jb1.napafrica.net [196.46.25.166]
6 454 ms 467 ms 409 ms 72.14.237.239
7 223 ms 232 ms 275 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Then:

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 8 ms 8 ms 169-0-5-1-access.afrihost.co.za [169.0.5.1]
3 12 ms 13 ms 36 ms 41.170.79.230
4 14 ms 10 ms 11 ms 41.170.79.236
5 425 ms 460 ms 462 ms google.jb1.napafrica.net [196.46.25.166]
6 479 ms 516 ms 509 ms 72.14.237.239
7 684 ms 518 ms 558 ms jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Francois Marais · Sep 20, 2015

P2P dead. Tried a full iOS9 download as my one iPad ran on a Beta, and nothing worked.
Always a good feeling when you return to find that the business uncapped account you pay for works like a cheap ass users account.

Johnatan56 · Sep 20, 2015

Browsing really, really slow.

Code:

Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    33 ms    30 ms    32 ms  41.170.79.229
  4    32 ms    29 ms    30 ms  41.170.79.230
  5    42 ms    51 ms    45 ms  41.170.79.236
  6    31 ms    32 ms    31 ms  41.160.2.33
  7    35 ms    32 ms    39 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  8   208 ms   205 ms   209 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
  9   176 ms   176 ms   178 ms  if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30]
 10   203 ms   203 ms   203 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   209 ms   208 ms   209 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   208 ms   209 ms   207 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 13   206 ms   205 ms   205 ms  if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
 14   208 ms   209 ms   208 ms  80.231.62.6
 15   219 ms   223 ms   220 ms  nl-ams05a-rd2-xe-4-1-0.aorta.net [84.116.130.9] 
 16   221 ms   221 ms   222 ms  uk-lon01a-ri4-ge-4-0-0.aorta.net [84.116.132.18]
 17   216 ms   216 ms   216 ms  uk-lon01b-rd1-xe-7-1-2.aorta.net [84.116.134.229]
 18   216 ms   217 ms   217 ms  ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]
 19   232 ms   227 ms   227 ms  62-179-117-106.ch-zrh01a-ra1.aorta.net [62.179.117.106]
 20   222 ms   221 ms   222 ms  gi0-0-1-74-asr1k-2-swz1.net.tele.net [194.183.142.142]
 21   227 ms   227 ms   227 ms  service.tele.net [194.183.128.94]

Trace complete.

Johnatan56 · Sep 20, 2015

Browsing really, really slow.

Code:

Tracing route to vienna.at [194.183.128.94]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  home.gateway.pace.net [192.168.1.1]
  2     *        *        *     Request timed out.
  3    33 ms    30 ms    32 ms  41.170.79.229
  4    32 ms    29 ms    30 ms  41.170.79.230
  5    42 ms    51 ms    45 ms  41.170.79.236
  6    31 ms    32 ms    31 ms  41.160.2.33
  7    35 ms    32 ms    39 ms  ix-0-3-0-0.tcore1.JSO-Johannesburg.as6453.net [216.6.55.37]
  8   208 ms   205 ms   209 ms  if-4-2.tcore1.KLT-Cape-Town.as6453.net [41.206.178.2]
  9   176 ms   176 ms   178 ms  if-1-0-0-2.core2.PV9-Lisbon.as6453.net [195.219.214.30]
 10   203 ms   203 ms   203 ms  if-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
 11   209 ms   208 ms   209 ms  if-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
 12   208 ms   209 ms   207 ms  if-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
 13   206 ms   205 ms   205 ms  if-15-2.tcore2.LDN-London.as6453.net [80.231.131.118]
 14   208 ms   209 ms   208 ms  80.231.62.6
 15   219 ms   223 ms   220 ms  nl-ams05a-rd2-xe-4-1-0.aorta.net [84.116.130.9] 
 16   221 ms   221 ms   222 ms  uk-lon01a-ri4-ge-4-0-0.aorta.net [84.116.132.18]
 17   216 ms   216 ms   216 ms  uk-lon01b-rd1-xe-7-1-2.aorta.net [84.116.134.229]
 18   216 ms   217 ms   217 ms  ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]
 19   232 ms   227 ms   227 ms  62-179-117-106.ch-zrh01a-ra1.aorta.net [62.179.117.106]
 20   222 ms   221 ms   222 ms  gi0-0-1-74-asr1k-2-swz1.net.tele.net [194.183.142.142]
 21   227 ms   227 ms   227 ms  service.tele.net [194.183.128.94]

Trace complete.

Francois Marais · Sep 20, 2015

http://netgauge.ookla.com/share/276431060.png
2MB Business Account
Pinging google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=240ms TTL=57
Reply from 216.58.223.35: bytes=32 time=158ms TTL=57
Reply from 216.58.223.35: bytes=32 time=258ms TTL=57
Reply from 216.58.223.35: bytes=32 time=352ms TTL=57
Reply from 216.58.223.35: bytes=32 time=169ms TTL=57
Reply from 216.58.223.35: bytes=32 time=268ms TTL=57
Reply from 216.58.223.35: bytes=32 time=218ms TTL=57
Reply from 216.58.223.35: bytes=32 time=286ms TTL=57
Reply from 216.58.223.35: bytes=32 time=159ms TTL=57
Reply from 216.58.223.35: bytes=32 time=281ms TTL=57
Reply from 216.58.223.35: bytes=32 time=163ms TTL=57
Reply from 216.58.223.35: bytes=32 time=274ms TTL=57
Reply from 216.58.223.35: bytes=32 time=335ms TTL=57
Reply from 216.58.223.35: bytes=32 time=168ms TTL=57
Reply from 216.58.223.35: bytes=32 time=314ms TTL=57
Reply from 216.58.223.35: bytes=32 time=145ms TTL=57
Reply from 216.58.223.35: bytes=32 time=308ms TTL=57
Reply from 216.58.223.35: bytes=32 time=399ms TTL=57
Reply from 216.58.223.35: bytes=32 time=191ms TTL=57
Reply from 216.58.223.35: bytes=32 time=389ms TTL=57
Reply from 216.58.223.35: bytes=32 time=174ms TTL=57
Reply from 216.58.223.35: bytes=32 time=359ms TTL=57
Reply from 216.58.223.35: bytes=32 time=354ms TTL=57

Ping statistics for 216.58.223.35:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 399ms, Average = 259ms

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 193 ms 244 ms 277 ms 169-0-15-1-access.afrihost.co.za [169.0.15.1]
3 384 ms 329 ms 295 ms ipc-rx-b-access.afrihost.co.za [169.1.1.238]
4 203 ms 105 ms 99 ms 41.170.79.236
5 218 ms 241 ms 254 ms google.jb1.napafrica.net [196.46.25.166]
6 283 ms 195 ms 156 ms 72.14.239.129
7 312 ms 285 ms 202 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
Tracing route to up.ac.za [137.215.10.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 132 ms 150 ms 187 ms 169-0-15-1-access.afrihost.co.za [169.0.15.1]
3 277 ms 326 ms 311 ms 41.170.79.230
4 258 ms 211 ms 138 ms 41.170.79.236
5 210 ms 185 ms 164 ms tenet.jb1.napafrica.net [196.46.25.216]
6 293 ms 310 ms 253 ms ae0-isd1-pe1.tenet.ac.za [155.232.15.106]
7 282 ms 320 ms 306 ms 155.232.15.105
8 290 ms 282 ms 231 ms te0-8-0-2-pta1-p1-n.tenet.ac.za [155.232.29.2]
9 306 ms 353 ms 376 ms te9-4-pta1-pe1.tenet.ac.za [155.232.6.138]
10 240 ms 289 ms 349 ms thermopylae-tenet.up.ac.za [137.215.99.2]
11 324 ms 295 ms 371 ms adupdc01.up.ac.za [137.215.10.70]

Trace complete.

C:\Users\François Marais>ping up.ac.za -t

Pinging up.ac.za [137.215.10.70] with 32 bytes of data:
Reply from 137.215.10.70: bytes=32 time=208ms TTL=51
Reply from 137.215.10.70: bytes=32 time=261ms TTL=51
Reply from 137.215.10.70: bytes=32 time=269ms TTL=51
Reply from 137.215.10.70: bytes=32 time=293ms TTL=51
Reply from 137.215.10.70: bytes=32 time=274ms TTL=51
Reply from 137.215.10.70: bytes=32 time=200ms TTL=51
Reply from 137.215.10.70: bytes=32 time=342ms TTL=51
Reply from 137.215.10.70: bytes=32 time=272ms TTL=51
Reply from 137.215.10.70: bytes=32 time=309ms TTL=51
Reply from 137.215.10.70: bytes=32 time=197ms TTL=51
Request timed out.
Reply from 137.215.10.70: bytes=32 time=243ms TTL=51
Reply from 137.215.10.70: bytes=32 time=246ms TTL=51
Reply from 137.215.10.70: bytes=32 time=345ms TTL=51
Reply from 137.215.10.70: bytes=32 time=264ms TTL=51
Reply from 137.215.10.70: bytes=32 time=220ms TTL=51
Reply from 137.215.10.70: bytes=32 time=269ms TTL=51
Reply from 137.215.10.70: bytes=32 time=378ms TTL=51
Reply from 137.215.10.70: bytes=32 time=176ms TTL=51
Reply from 137.215.10.70: bytes=32 time=331ms TTL=51
Reply from 137.215.10.70: bytes=32 time=313ms TTL=51
Reply from 137.215.10.70: bytes=32 time=314ms TTL=51
Reply from 137.215.10.70: bytes=32 time=251ms TTL=51
Reply from 137.215.10.70: bytes=32 time=284ms TTL=51
Reply from 137.215.10.70: bytes=32 time=286ms TTL=51
Reply from 137.215.10.70: bytes=32 time=268ms TTL=51
Reply from 137.215.10.70: bytes=32 time=298ms TTL=51

Ping statistics for 137.215.10.70:
Packets: Sent = 27, Received = 26, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 378ms, Average = 273ms

P2P has gone Afrihost (aka ****) and browsing does not work to most sites.

iOS9 download that I have been atempting to get from Friday.... Can't get to the site. And tomorrow everything else will be blamed but the AH network.
I tried switching to the other useless network to see if P2P works on that, and also dead. So AH, I expect to see a reduction in my bill this month, because you can't get the full amount of money you get every month, because I AM NOT GETTING THE SERVICE I PAY FOR EVERY MONTH!

DonaldMickey · Sep 20, 2015

Francois Marais said:
http://netgauge.ookla.com/share/276431060.png
2MB Business Account
Pinging google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=240ms TTL=57
Reply from 216.58.223.35: bytes=32 time=158ms TTL=57
Reply from 216.58.223.35: bytes=32 time=258ms TTL=57
Reply from 216.58.223.35: bytes=32 time=352ms TTL=57
Reply from 216.58.223.35: bytes=32 time=169ms TTL=57
Reply from 216.58.223.35: bytes=32 time=268ms TTL=57
Reply from 216.58.223.35: bytes=32 time=218ms TTL=57
Reply from 216.58.223.35: bytes=32 time=286ms TTL=57
Reply from 216.58.223.35: bytes=32 time=159ms TTL=57
Reply from 216.58.223.35: bytes=32 time=281ms TTL=57
Reply from 216.58.223.35: bytes=32 time=163ms TTL=57
Reply from 216.58.223.35: bytes=32 time=274ms TTL=57
Reply from 216.58.223.35: bytes=32 time=335ms TTL=57
Reply from 216.58.223.35: bytes=32 time=168ms TTL=57
Reply from 216.58.223.35: bytes=32 time=314ms TTL=57
Reply from 216.58.223.35: bytes=32 time=145ms TTL=57
Reply from 216.58.223.35: bytes=32 time=308ms TTL=57
Reply from 216.58.223.35: bytes=32 time=399ms TTL=57
Reply from 216.58.223.35: bytes=32 time=191ms TTL=57
Reply from 216.58.223.35: bytes=32 time=389ms TTL=57
Reply from 216.58.223.35: bytes=32 time=174ms TTL=57
Reply from 216.58.223.35: bytes=32 time=359ms TTL=57
Reply from 216.58.223.35: bytes=32 time=354ms TTL=57

Ping statistics for 216.58.223.35:
Packets: Sent = 23, Received = 23, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 399ms, Average = 259ms

Tracing route to google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 193 ms 244 ms 277 ms 169-0-15-1-access.afrihost.co.za [169.0.15.1]
3 384 ms 329 ms 295 ms ipc-rx-b-access.afrihost.co.za [169.1.1.238]
4 203 ms 105 ms 99 ms 41.170.79.236
5 218 ms 241 ms 254 ms google.jb1.napafrica.net [196.46.25.166]
6 283 ms 195 ms 156 ms 72.14.239.129
7 312 ms 285 ms 202 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.
Tracing route to up.ac.za [137.215.10.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 132 ms 150 ms 187 ms 169-0-15-1-access.afrihost.co.za [169.0.15.1]
3 277 ms 326 ms 311 ms 41.170.79.230
4 258 ms 211 ms 138 ms 41.170.79.236
5 210 ms 185 ms 164 ms tenet.jb1.napafrica.net [196.46.25.216]
6 293 ms 310 ms 253 ms ae0-isd1-pe1.tenet.ac.za [155.232.15.106]
7 282 ms 320 ms 306 ms 155.232.15.105
8 290 ms 282 ms 231 ms te0-8-0-2-pta1-p1-n.tenet.ac.za [155.232.29.2]
9 306 ms 353 ms 376 ms te9-4-pta1-pe1.tenet.ac.za [155.232.6.138]
10 240 ms 289 ms 349 ms thermopylae-tenet.up.ac.za [137.215.99.2]
11 324 ms 295 ms 371 ms adupdc01.up.ac.za [137.215.10.70]

Trace complete.

C:\Users\François Marais>ping up.ac.za -t

Pinging up.ac.za [137.215.10.70] with 32 bytes of data:
Reply from 137.215.10.70: bytes=32 time=208ms TTL=51
Reply from 137.215.10.70: bytes=32 time=261ms TTL=51
Reply from 137.215.10.70: bytes=32 time=269ms TTL=51
Reply from 137.215.10.70: bytes=32 time=293ms TTL=51
Reply from 137.215.10.70: bytes=32 time=274ms TTL=51
Reply from 137.215.10.70: bytes=32 time=200ms TTL=51
Reply from 137.215.10.70: bytes=32 time=342ms TTL=51
Reply from 137.215.10.70: bytes=32 time=272ms TTL=51
Reply from 137.215.10.70: bytes=32 time=309ms TTL=51
Reply from 137.215.10.70: bytes=32 time=197ms TTL=51
Request timed out.
Reply from 137.215.10.70: bytes=32 time=243ms TTL=51
Reply from 137.215.10.70: bytes=32 time=246ms TTL=51
Reply from 137.215.10.70: bytes=32 time=345ms TTL=51
Reply from 137.215.10.70: bytes=32 time=264ms TTL=51
Reply from 137.215.10.70: bytes=32 time=220ms TTL=51
Reply from 137.215.10.70: bytes=32 time=269ms TTL=51
Reply from 137.215.10.70: bytes=32 time=378ms TTL=51
Reply from 137.215.10.70: bytes=32 time=176ms TTL=51
Reply from 137.215.10.70: bytes=32 time=331ms TTL=51
Reply from 137.215.10.70: bytes=32 time=313ms TTL=51
Reply from 137.215.10.70: bytes=32 time=314ms TTL=51
Reply from 137.215.10.70: bytes=32 time=251ms TTL=51
Reply from 137.215.10.70: bytes=32 time=284ms TTL=51
Reply from 137.215.10.70: bytes=32 time=286ms TTL=51
Reply from 137.215.10.70: bytes=32 time=268ms TTL=51
Reply from 137.215.10.70: bytes=32 time=298ms TTL=51

Ping statistics for 137.215.10.70:
Packets: Sent = 27, Received = 26, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 378ms, Average = 273ms

P2P has gone Afrihost (aka ****) and browsing does not work to most sites.

iOS9 download that I have been atempting to get from Friday.... Can't get to the site. And tomorrow everything else will be blamed but the AH network.
I tried switching to the other useless network to see if P2P works on that, and also dead. So AH, I expect to see a reduction in my bill this month, because you can't get the full amount of money you get every month, because I AM NOT GETTING THE SERVICE I PAY FOR EVERY MONTH!

Your exchange will be blamed due to high latency on your second hop.

Vorastra · Sep 20, 2015

Getting "connection reset" errors every so often. Just before coming to report I had a reset error getting on MyBB.

Code:

Tracing route to www.google.com [216.58.223.4]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  home.gateway.home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3    21 ms    20 ms    21 ms  41.170.79.229
  4    19 ms    54 ms    18 ms  41.170.79.230
  5    21 ms    19 ms    19 ms  41.170.79.236
  6    20 ms    20 ms    21 ms  google.jb1.napafrica.net [196.46.25.166]
  7    19 ms    19 ms    19 ms  72.14.237.239
  8    19 ms    18 ms    19 ms  jnb01s07-in-f4.1e100.net [216.58.223.4]

Trace complete.

Dianysis · Sep 20, 2015

DonaldMickey said:
Your exchange will be blamed due to high latency on your second hop.

I also wonder how many of the problems I face are due to my exchange vs AH.
EVERY SINGLE PROBLEM I FACE IS BLAMED ON MY EXCHANGE - WITHOUT FAIL.

Francois Marais · Sep 20, 2015

AH for FUDGE!

Hummercellc · Sep 20, 2015

Latency is spiking to every server, and connections are also dropping.

I said I wouldn't use Afrigreen again. But I did and can see no improvement what so ever!

leto · Sep 20, 2015

I switched to the Afrigreen account because the normal Afrihost account (uncapped 4mb) was averaging at around 1000ms to South African servers for over a week. Now the same thing is happening again.

Alien0 · Sep 20, 2015

Afrigreen working great here in Durbs - streaming all weekend, no problems

8-BALL · Sep 20, 2015

AfriGreen was looking queasy with really poor throughput:

Yet speedtest says differently.

So off to Afripacketloss I went, Youtube maxing at 1Mb/s and generally unpleasant to use due to the packetloss.

Undoubtedly we will have the Afriguys here tomorrow with comments of "Mine was fine, so clearly its not us, its your exchange" ugh really do feel that we aren't seeing what we are paying for.

So any idea where those greener pastures may be guys?

Devilish · Sep 20, 2015

8-BALL said:
So any idea where those greener pastures may be guys?

The grass is always greener on the other side until you get there.

8-BALL · Sep 20, 2015

Devilish said:
The grass is always greener on the other side until you get there.

So so true, one can but hope for lower latencies and less packet loss

Devilish · Sep 20, 2015

8-BALL said:
So so true, one can but hope for lower latencies and less packet loss

You do know that AfriGreen doesn't have IPC in Cape Town yet and as such your traffic is routed via Johannesburg which results in higher latency. The packet loss is worrying.

8-BALL · Sep 20, 2015

Devilish said:
You do know that AfriGreen doesn't have IPC in Cape Town yet and as such your traffic is routed via Johannesburg which results in higher latency. The packet loss is worrying.

Yes I am well aware of their not being IPC in Cape Town, however if you look at the variance in latency's on Afrigreen where at times on local hardware its spiked to insane levels. Afrired doesn't display this variance in latency but suffers from incredible packet loss.

Afrigreen on the other hand has next to no packet loss but varied latency and throughput.

This is clearly network based and not an infrastructure fault.

mR Yellow · Sep 20, 2015

Arfrihost has really been **** of late. Even my wife is complaining.

8-BALL · Sep 20, 2015

mR Yellow said:
Arfrihost has really been **** of late. Even my wife is complaining.

Oh my, when the boss talks....

Devilish · Sep 20, 2015

8-BALL said:
This is clearly network based and not an infrastructure fault.

Did a Trace route to 188.65.200.200 which was blocked by PeerBlock.

Code:

Tracing route to ns345728.ip-188-165-200.eu [188.165.200.200]
over a maximum of 30 hops:

  1  General failure.

Trace complete.

Join the MyBroadband community

Get started

Afrihost POC Network - Afrigreen Feedback

Expert Member

Senior Member

Honorary Master

Honorary Master

Senior Member

Well-Known Member

Honorary Master

Expert Member

Senior Member

Expert Member

Member

Well-Known Member

Senior Member

Well-Known Member

Senior Member

Well-Known Member

Senior Member

Well-Known Member

Senior Member

Well-Known Member