Afrihost POC Network - Afrigreen Feedback

Status
Not open for further replies.
@Afriman: Sadly no. My setup at home pushes my little 2mb line to the max and if there is a slight hiccup then things go pear shaped. My wife streams while I game (this time it was Guild Wars 2) and everything is stable. Latency is stable etc. On Afrigreen the weekend the latency seesawed a lot. Going back to the normal one the stability returned.

Sadly no tests. Just the story :)
 
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!

These tests all show inconsistency at your exchange, before you hop onto our network. This is probably why your results don't seem consistent with general experience. If you were testing at the time when others did have a poor experience, your already congested exchange would have just made your experience worse :(
 
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.

From what I recall you said you do have a dodgy exchange though. If that's the case, it's going to show up on all the tests you submit :(
 
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!

Other reports from KZN seem mostly normal. I wonder if this isn't the same exchange router problem you had with the one IP performing well and the other performing terribly :(
 
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.

Can you please post the traceroutes for those stats? Would be great to see where the latency starts.
 
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.

5r3jdOd.png


This is clearly network based and not an infrastructure fault.

It's important to remember that any local network latency is going to be compounded when added to additional network latency. This will also vary when using different routing, depending on the peering relationship with the host network. While we do our best to keep latency consistent where we can, the nature of all the moving parts in every request makes it difficult to guarantee, and having local IPC removes a big chunk of those variables.
 
Please explain why Afrireps request account details, and then you never hear a word? I have to beg for a proper service, beg for support, what am I paying for each month?
 
Please explain why Afrireps request account details, and then you never hear a word? I have to beg for a proper service, beg for support, what am I paying for each month?

I don't think you have to beg for anything at all. If you were asked to provide details, then we either use those details for testing or we use them to get in touch with you, that would have been made clear by the rep in question. If you sent a message to a rep long after their shift ended, then obviously they would only get back to you when they picked up your PM, we do not have access to each other's private messages to pick up on messages in that way, which is why we lock our mailboxes when any of us go on leave.
 
I don't think you have to beg for anything at all. If you were asked to provide details, then we either use those details for testing or we use them to get in touch with you, that would have been made clear by the rep in question. If you sent a message to a rep long after their shift ended, then obviously they would only get back to you when they picked up your PM, we do not have access to each other's private messages to pick up on messages in that way, which is why we lock our mailboxes when any of us go on leave.

Well from where I am sitting it feels like I am begging, I sent my details to AfriFella on Thursday last week due to speed issues, never got a response. I cannot wait 4-5 days for a response.
 
Well from where I am sitting it feels like I am begging, I sent my details to AfriFella on Thursday last week due to speed issues, never got a response. I cannot wait 4-5 days for a response.

As I mentioned, if he asked for details to test with, he would have made that clear. I'll check with him when he gets in :)
 
This seems mostly OK for international. What was speedtest showing you in terms of throughput?

Didn't check the speedtests, but latency was fine. Just really slow loading pages, no one was using the internet besides me.
No problems this morning though.
 
Didn't check the speedtests, but latency was fine. Just really slow loading pages, no one was using the internet besides me.
No problems this morning though.

Not sure what happened yesterday but seemed like a few reports along those lines. We've kicked all that info up to the network team for investigation.
 
We seem to see that traceroutes show higher latency than normal but a direct ping shows better results. We're not sure why this is, but generally speaking the ping result is a little more reliable, especially a constant ping over time.

Perhaps, but when I want to queue for a Dota game it asks me for which region, because my SA ping is in the high 600ms constantly.
 
Perhaps, but when I want to queue for a Dota game it asks me for which region, because my SA ping is in the high 600ms constantly.

Looks much higher than it should be. I passed your username onto one of our network guys so he can test and see if he can replicate :(
 
Had a terrible early morning in KZN but all is going well presently (after a couple of router resets). Couldn't post results as everything timed-out.
Here's what it's looking like at the moment. Best latency for the region thus far.
276888807.png
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X