Afrihost - Pure Fibre Feedback Thread

Status
Not open for further replies.
Woke up a few minutes ago to discover that the internet is out. Router says cannot connect even after a reboot. This is Openserve in PE. What gives?


Update: Nevermind. I see the notice on the status page now. Oh well.
 
Last edited:
"We are aware of the current service disruptions in Summerstrand. Technicians are in the process of procuring the necessary equipment in order to resolve this issue. However, due to the festive season, equipement will, unfortunately, only be received early in the new year. We’ll continue to keep you updated as we progress and sincerely apologise for the inconvenience caused. Thank you for your patience during this time."

LOL? A whole month without fibre...
 
Happening again tonight. Is it congestion on AH's side?

Had someone run tests for us in CPT with Octotel:

PING hawkesworthappliancetesting.co.uk (139.162.220.124): 56 data bytes
64 bytes from 139.162.220.124: icmp_seq=0 ttl=57 time=168.450 ms
64 bytes from 139.162.220.124: icmp_seq=1 ttl=57 time=175.404 ms
64 bytes from 139.162.220.124: icmp_seq=2 ttl=57 time=176.406 ms
64 bytes from 139.162.220.124: icmp_seq=3 ttl=57 time=177.960 ms
64 bytes from 139.162.220.124: icmp_seq=4 ttl=57 time=166.219 ms
64 bytes from 139.162.220.124: icmp_seq=5 ttl=57 time=177.410 ms
64 bytes from 139.162.220.124: icmp_seq=6 ttl=57 time=166.740 ms
64 bytes from 139.162.220.124: icmp_seq=7 ttl=57 time=166.450 ms
64 bytes from 139.162.220.124: icmp_seq=8 ttl=57 time=159.370 ms
64 bytes from 139.162.220.124: icmp_seq=9 ttl=57 time=173.425 ms

--- hawkesworthappliancetesting.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 159.370/170.783/177.960/5.891 ms

Definitely looking pretty good, so we don't think it's a network issue. This was in the evening, around 9:30PM or so.
 
Woke up a few minutes ago to discover that the internet is out. Router says cannot connect even after a reboot. This is Openserve in PE. What gives?


Update: Nevermind. I see the notice on the status page now. Oh well.

We did some maintainence and upgrades on our IPC. Should all be back to normal now :)
 
Had someone run tests for us in CPT with Octotel:

PING hawkesworthappliancetesting.co.uk (139.162.220.124): 56 data bytes
64 bytes from 139.162.220.124: icmp_seq=0 ttl=57 time=168.450 ms
64 bytes from 139.162.220.124: icmp_seq=1 ttl=57 time=175.404 ms
64 bytes from 139.162.220.124: icmp_seq=2 ttl=57 time=176.406 ms
64 bytes from 139.162.220.124: icmp_seq=3 ttl=57 time=177.960 ms
64 bytes from 139.162.220.124: icmp_seq=4 ttl=57 time=166.219 ms
64 bytes from 139.162.220.124: icmp_seq=5 ttl=57 time=177.410 ms
64 bytes from 139.162.220.124: icmp_seq=6 ttl=57 time=166.740 ms
64 bytes from 139.162.220.124: icmp_seq=7 ttl=57 time=166.450 ms
64 bytes from 139.162.220.124: icmp_seq=8 ttl=57 time=159.370 ms
64 bytes from 139.162.220.124: icmp_seq=9 ttl=57 time=173.425 ms

--- hawkesworthappliancetesting.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 159.370/170.783/177.960/5.891 ms

Definitely looking pretty good, so we don't think it's a network issue. This was in the evening, around 9:30PM or so.

We'll agree to disagree on this point I guess. That ping sequence is showing a significant amount of fluctuation in latency, and some of those results are up to 37ms above where they should be from Cape Town. This also seems to be happening mainly at night - which is odd? Are you saying it's an Octotel issue, or something on your network which you're fine with? MTR from right now for your test:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   11 |   11 |    0 |    0 |    0 |    0 |
|         165-73-101-65.ip.afrihost.co.za -    0 |   11 |   11 |    1 |    1 |    1 |    1 |
|            169-1-21-1.ip.afrihost.co.za -    0 |   11 |   11 |    1 |    1 |    1 |    1 |
|                            196.25.26.65 -    0 |   11 |   11 |    2 |    3 |   11 |    2 |
|                             10.189.30.2 -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|be5956.rcr21.b023101-0.lon01.atlas.cogentco.com -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|  be12499.ccr21.lon01.atlas.cogentco.com -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           109.74.207.11 -    0 |   11 |   11 |  143 |  143 |  144 |  143 |
|                          d15.fcomet.com -    0 |   11 |   11 |  142 |  142 |  143 |  143 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Had someone run tests for us in CPT with Octotel:

PING hawkesworthappliancetesting.co.uk (139.162.220.124): 56 data bytes
64 bytes from 139.162.220.124: icmp_seq=0 ttl=57 time=168.450 ms
64 bytes from 139.162.220.124: icmp_seq=1 ttl=57 time=175.404 ms
64 bytes from 139.162.220.124: icmp_seq=2 ttl=57 time=176.406 ms
64 bytes from 139.162.220.124: icmp_seq=3 ttl=57 time=177.960 ms
64 bytes from 139.162.220.124: icmp_seq=4 ttl=57 time=166.219 ms
64 bytes from 139.162.220.124: icmp_seq=5 ttl=57 time=177.410 ms
64 bytes from 139.162.220.124: icmp_seq=6 ttl=57 time=166.740 ms
64 bytes from 139.162.220.124: icmp_seq=7 ttl=57 time=166.450 ms
64 bytes from 139.162.220.124: icmp_seq=8 ttl=57 time=159.370 ms
64 bytes from 139.162.220.124: icmp_seq=9 ttl=57 time=173.425 ms

--- hawkesworthappliancetesting.co.uk ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 159.370/170.783/177.960/5.891 ms

Definitely looking pretty good, so we don't think it's a network issue. This was in the evening, around 9:30PM or so.
lol - i see a 159ms-177ms variance over 10 packets, if it was good they would all be the same, not jumping around, come on, had to use vpn again last night.
758364
 
We'll agree to disagree on this point I guess. That ping sequence is showing a significant amount of fluctuation in latency, and some of those results are up to 37ms above where they should be from Cape Town. This also seems to be happening mainly at night - which is odd? Are you saying it's an Octotel issue, or something on your network which you're fine with? MTR from right now for your test:

Code:
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   11 |   11 |    0 |    0 |    0 |    0 |
|         165-73-101-65.ip.afrihost.co.za -    0 |   11 |   11 |    1 |    1 |    1 |    1 |
|            169-1-21-1.ip.afrihost.co.za -    0 |   11 |   11 |    1 |    1 |    1 |    1 |
|                            196.25.26.65 -    0 |   11 |   11 |    2 |    3 |   11 |    2 |
|                             10.189.30.2 -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|be5956.rcr21.b023101-0.lon01.atlas.cogentco.com -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|  be12499.ccr21.lon01.atlas.cogentco.com -    0 |   11 |   11 |  142 |  142 |  143 |  142 |
|                   No response from host -  100 |    2 |    0 |    0 |    0 |    0 |    0 |
|                           109.74.207.11 -    0 |   11 |   11 |  143 |  143 |  144 |  143 |
|                          d15.fcomet.com -    0 |   11 |   11 |  142 |  142 |  143 |  143 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Our NOC are saying that it's within range for high demand periods, and they believe the internet experience should still be good even with minor additional latency.
 
lol - i see a 159ms-177ms variance over 10 packets, if it was good they would all be the same, not jumping around, come on, had to use vpn again last night.
View attachment 758364

That's an 18ms variance, which I don't believe could siginificantly impact any internet service. Unless there is a specific service which we could test.
 
That's an 18ms variance, which I don't believe could siginificantly impact any internet service. Unless there is a specific service which we could test.

It's an 18ms variance on latency which is already up 20-30ms from daytime values. The general "internet experience" is still good - but the internet experience also includes online gaming, where latency plays a huge role. An 18ms variance is noticeable, especially when it's constantly fluctuating. A 40-50ms difference in latency is VERY noticeable.
 
What did you use to run that test?

ping.pe

How are things on Websquad? Always wondered, but they never offered packages on Octotel. I see now that they do.

Im not actually on websquad, i just used one of their looking glass ips to test from. They seem to be the golden ISP atm, no one has issues on them and their routing to eu is excellent. I'm planning on switching to them once they start offering 200/100 on openserve (coming start of 2020 apparently).

If you are interested in seeing what the latencies are like with them here is their looking glass: http://lg.as328137.net/
 
It's an 18ms variance on latency which is already up 20-30ms from daytime values. The general "internet experience" is still good - but the internet experience also includes online gaming, where latency plays a huge role. An 18ms variance is noticeable, especially when it's constantly fluctuating. A 40-50ms difference in latency is VERY noticeable.

I get what you are saying. From a network perspective, I guess when demand is high it is difficult to guarantee latencies without implementing shaping or throttling, so I am guessing they have an acceptable range before drastic measures are called for. Will chat to them about how they see it. Ultimately, we want clients to have the best experience, so we'll look at any areas where we can optimise always.
 
ping.pe



Im not actually on websquad, i just used one of their looking glass ips to test from. They seem to be the golden ISP atm, no one has issues on them and their routing to eu is excellent. I'm planning on switching to them once they start offering 200/100 on openserve (coming start of 2020 apparently).

If you are interested in seeing what the latencies are like with them here is their looking glass: http://lg.as328137.net/

Thanks - latencies seem to be surprisingly similar to AH - except that they're originating from JHB, so I'm assuming there's some added latency there, or do they go direct to EU?

They are a fair amount cheaper than AH. My problem with the "golden ISPs" is that they're only golden until they gain traction and people start migrating to them. AH has actually been rock solid for me for everything except online gaming, due to the latency issues.
 
@AfriMan, I don't really want to jump on the bandwagon, I saw your post from a few days ago where you mentioned that you guys are still tweaking things, so I'm inclined to wait a little while longer to see if things improve. However, please understand the client's point of view as well, that if we need to pay extra each month for a VPN just to get our latency down to a more usable level, then why not just move to a slightly more expensive ISP that already does the routing for us, making it one less thing we need to worry about?

For interest sake, here are my results when I ping the latest IP in the thread -

Pinging 139.162.220.124 with 32 bytes of data:
Reply from 139.162.220.124: bytes=32 time=192ms TTL=53
Reply from 139.162.220.124: bytes=32 time=201ms TTL=53
Reply from 139.162.220.124: bytes=32 time=172ms TTL=53
Reply from 139.162.220.124: bytes=32 time=185ms TTL=53

Ping statistics for 139.162.220.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 201ms, Average = 187ms
 
Thanks - latencies seem to be surprisingly similar to AH - except that they're originating from JHB, so I'm assuming there's some added latency there, or do they go direct to EU?

If you are referring to cape town routing, then yes it does go direct to london. You can select between their different nodes at the top (cpt, joburg or durban), by default its set to joburg.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X