Afrihost New Network Feedback

Status
Not open for further replies.
I have the 'Get Automatically from ISP' option ticked, haven't changed to 169.1.2.2 or 169.1.2.1 in a while.

Yesterday it performed much better, still had to reload the video feed a few times as the Latency to Broadcaster and Latency to Encoder were so high.

We're continuing to test and troubleshoot here. Hopefully we can make more adjustments to improve overall performance.
 
Not sure if I am still the only one, but ............

packet loss on hops 3 and 8 is still pretty much annoying and creates severe lag issues in game.


C:\Users\Igor III>tracert 95.172.91.23

Tracing route to 95.172.91.23 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 26 ms 24 ms 29 ms jhb-in2.ip.adsl.co.za [169.1.5.30]
5 23 ms 23 ms 23 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
6 23 ms 26 ms 23 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
7 25 ms 25 ms 25 ms 41.169.57.216
8 * * * Request timed out.
9 186 ms 185 ms 185 ms if-ae-6-2.tcore2.KLT-Cape-Town.as6453.net [41.20
6.179.10]
10 203 ms 209 ms 210 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.20
6.164.253]
11 194 ms 192 ms 191 ms if-ae-5-80.tcore2.PV9-Lisbon.as6453.net [80.231.
159.57]
12 192 ms 193 ms 196 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.1
58.5]
13 192 ms 197 ms 185 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.2
31.158.30]
14 197 ms * * if-ae-19-2.tcore2.L78-London.as6453.net [80.231.
138.22]
15 199 ms 208 ms 199 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.1
31.2]
16 199 ms 197 ms 197 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.
130.130]
17 196 ms 204 ms 196 ms 195.219.83.186
18 193 ms 194 ms 199 ms ae-4.r23.londen03.uk.bb.gin.ntt.net [129.250.5.4
0]
19 199 ms 197 ms 200 ms ae-2.r24.amstnl02.nl.bb.gin.ntt.net [129.250.5.2
]
20 197 ms 192 ms 191 ms ae-1.r02.amstnl02.nl.bb.gin.ntt.net [129.250.2.1
13]
21 195 ms 211 ms 193 ms ae-0.internap.amstnl02.nl.bb.gin.ntt.net [81.20.
69.230]
22 193 ms 196 ms 209 ms border4.ae2-bbnet2.ams004.pnap.net [95.172.78.71
]
23 190 ms 191 ms 194 ms edge2.ae1-edgenet.ams004.pnap.net [208.146.38.22
]
24 200 ms 211 ms 197 ms perfectworldent-7.edge2.ams004.pnap.net [95.172.
88.94]
25 194 ms 195 ms 193 ms 95.172.91.1
26 199 ms 198 ms 247 ms 95.172.91.23

Trace complete.

C:\Users\Igor III>

View attachment 362062

The timeouts are not necessarily packet loss, it could be that the network kit gives low priority to ICMP pings and might not respond if the router is busy. You might see more accurate results using MTR or tests run over time.
 
I have a similar problem to Hummercellc. Facebook is a useful site to test with, so here are some results. The ping test is fine though:

$ ping -c 3 www.facebook.com
PING star-mini.c10r.facebook.com (31.13.91.36) 56(84) bytes of data.
64 bytes from edge-star-mini-shv-01-ams3.facebook.com (31.13.91.36): icmp_seq=1 ttl=79 time=179 ms
64 bytes from edge-star-mini-shv-01-ams3.facebook.com (31.13.91.36): icmp_seq=2 ttl=79 time=180 ms
64 bytes from edge-star-mini-shv-01-ams3.facebook.com (31.13.91.36): icmp_seq=3 ttl=79 time=182 ms

--- star-mini.c10r.facebook.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 179.879/181.060/182.894/1.359 ms

the traceroute shows that traffic follows multiple routes:

$ traceroute www.facebook.com
traceroute to www.facebook.com (31.13.91.36), 30 hops max, 60 byte packets
1 adsl.wfeet.za.net (192.168.1.1) 1.634 ms 1.766 ms 1.981 ms
2 * * *
3 cpt-up2.ip.adsl.co.za (169.1.5.106) 39.015 ms 40.883 ms 42.788 ms
4 cpt-net1.ip.adsl.co.za (169.1.5.128) 45.977 ms 47.615 ms 50.262 ms
5 41.164.52.40 (41.164.52.40) 53.402 ms 55.231 ms 58.983 ms
6 if-ae-7-0.tcore1.KLT-Cape-Town.as6453.net (41.206.164.53) 72.173 ms 70.802 ms if-ae-7-0.tcore2.KLT-Cape-Town.as6453.net (41.206.165.25) 87.575 ms
7 if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net (41.206.164.253) 213.574 ms if-ae-5-80.tcore2.PV9-Lisbon.as6453.net (80.231.159.57) 180.898 ms if-p-6.core2.PV9-Lisbon.as6453.net (41.206.164.6) 155.901 ms
8 if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net (80.231.158.1) 189.136 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net (80.231.158.5) 190.084 ms if-p-6.core2.PV9-Lisbon.as6453.net (41.206.164.6) 156.073 ms
9 if-ae-2-2.tcore1.PV9-Lisbon.as6453.net (80.231.158.5) 197.721 ms 188.385 ms 199.825 ms
10 if-ae-1-3.tcore1.SV8-Highbridge.as6453.net (80.231.158.30) 174.556 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net (80.231.139.1) 206.370 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net (80.231.158.30) 174.115 ms
11 if-ae-2-2.tcore2.SV8-Highbridge.as6453.net (80.231.139.1) 186.686 ms 173.538 ms if-ae-11-2.tcore1.L78-London.as6453.net (80.231.139.42) 179.495 ms
12 if-ae-2-2.tcore1.L78-London.as6453.net (80.231.131.2) 183.871 ms if-ae-17-2.tcore1.LDN-London.as6453.net (80.231.130.130) 172.587 ms if-ae-11-2.tcore1.L78-London.as6453.net (80.231.139.42) 185.533 ms
13 195.219.83.186 (195.219.83.186) 175.436 ms 175.236 ms 173.966 ms
14 ae-4.r23.londen03.uk.bb.gin.ntt.net (129.250.5.40) 172.650 ms 180.001 ms 173.017 ms
15 ae-2.r24.amstnl02.nl.bb.gin.ntt.net (129.250.5.2) 177.968 ms 179.732 ms 182.303 ms
16 ae-2.r24.amstnl02.nl.bb.gin.ntt.net (129.250.5.2) 183.550 ms ae-2.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.211) 174.110 ms ae-1.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.113) 177.404 ms
17 ae-2.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.211) 180.369 ms ae-1.r02.amstnl02.nl.bb.gin.ntt.net (129.250.2.113) 173.501 ms ae-2.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.211) 173.514 ms
18 81.20.67.198 (81.20.67.198) 172.995 ms ae-0.facebook.amstnl02.nl.bb.gin.ntt.net (81.20.64.22) 177.438 ms ae1.bb02.ams2.tfbnw.net (31.13.29.90) 182.699 ms
19 be8.bb01.ams3.tfbnw.net (31.13.27.67) 175.307 ms ae1.bb01.ams2.tfbnw.net (31.13.29.86) 173.415 ms psw01b.ams3.tfbnw.net (173.252.66.204) 184.482 ms
20 edge-star-mini-shv-01-ams3.facebook.com (31.13.91.36) 216.035 ms 337.487 ms 339.891 ms

I had a look at the page load times using Chrome's Developer Tools and they are, during the problem time (which seems to be between 6 and 8 pm especially) extreme. The url https://www.facebook.com took 1.2 minutes to load in one test. The page appears piece by piece - first the basic frame and then components like the chat interface and so on. The problem doesn't seem to be related to simple latency or packet loss, there is more than that going on here.

There were some issues we picked up with Facebook, which seemed to be mostly around how traffic was being routed, but we'll have to investigate further to see if the cause was on our side or how they manage traffic through CDN's.
 
Yip, Internet is in the toilet tonight, everything is slow.
Yet speedtests, trace routes and pings are showing zero problems.
Almost as if ICMP is prioritised as well as http. Teamviewer not working at all, Facebook took over 2 minutes to open and Skype is horrid. I give up.

We definitely don't prioritise ICMP or use proxy's or any other method to make speedtests or traceroutes look better. We want clients to be able to run effective testing and troubleshooting so we can be more effective in improving their experience. Skewing the tests would ultimately hamper our support efforts. :(
 
Thank you. Similar to my problem as well.This is really getting pretty annoying. Tomorrow will be asked for some tests or how other downloads were or what dns I am using.

To answer:

1. Sick of tests.
2. Other downloads (http) are also up and down. XBox One updates were slow yesterday. Google play store updates up and down.
3. Using auto dns assigned by isp (looks to be 169.1.1.4 & 154.0.174.82)

EDIT: 4 mbps Business Uncapped

I honestly reckon these are the ipc issues that come up every so often. For me these are similar symptoms as in the past.

We're not seeing consistent load on our IPC, so we do believe that we have sufficient capacity. These issues seem to be related more to routing and content networking, which we're busy trying to work out with the CDN providers and our upstream providers, etc.
 
Everyday at 22:00 streaming performance drops drastically

I'm watching a stream and the latency jumps from an already HIGH latency of 15 seconds all the way to 24 seconds, after a lot of buffering. :(

Really do not feel like posting tests everyday as this happens so much.

That's odd though, because by 10pm the load on the network is usually dramatically tapering off.

Are you talking about seconds or milliseconds here? If you're talking about seconds, then it sounds like it's a problem either way and we need to see where this latency is coming from :(
 
Maybe time to look at a more reliable upstream international provider?
International has never been great since the start of Afrigreen. The most annoying thing is the dropped connections to international services. Which happens regardless of the time of day.

I think we need to investigate further, cos that is different to the experiences we have testing in CT, JHB and DBN. International is generally good for me, and we're also peering at the most optimal point at NAPAfrica for cached international content and best route overseas. The more we can identify potential issues through testing that our network team can either monitor or recreate, then we can make the network better and better.

I know it's a pain to submit tests, but these are definitely appreciated and do translate into hard results when we can use them to make informed changes.
 
I'm sorry that this happened, this is generally not the case at all.

With Telkom's new Holding Pool system, the process can complete in a matter of hours, but delays in moving the line into the holding pool generally cause delays. We do our best to push from our side for this to happen.

I'd be happy to look into this for you, though I see you've said you've already cancelled everything. Since you've already gone through the hard part, I'd be grateful if we could chat about how we can turn this experience around :(

Problem is I don't know what is going on, there is zero communication from Afrihost's side wrt the migration. The only communication that has been occurring is when I logged a support ticket through the Clientzone to make an enquiry and to relay my concerns that we would like to minimise any possible downtime since this would affect my wife's consultancy work. Afrihost subsequently promised to push the migration through quickly once I let them know ASAP once the line has gone in the holding pool which I have done. My line has been on PENDING status through the entire process. Why can't this be more transparent? Why would your company make promises if they don't mean anything... Should I make contingency plans in case my ISP don't keep their end of the bargain? Is this how you earn customers trust? Disappointed
 
Last edited:
Unfortunately I can tell from the connection stats. We'll need to check the DSLAM and SP restrictions in your area.

I can do that from your landline number- just drop me a PM.
PM inbound.
 
Problem is I don't know what is going on, there is zero communication from Afrihost's side wrt the migration. The only communication that has been occurring is when I logged a support ticket through the Clientzone to make an enquiry and to relay my concerns that we would like to minimise any possible downtime since this would affect my wife's consultancy work. Afrihost subsequently promised to push the migration through quickly once I let them know ASAP once the line has gone in the holding pool which I have done. My line has been on PENDING status through the entire process. Why can't this be more transparent? Why would your company make promises if they don't mean anything... Should I make contingency plans in case my ISP don't keep their end of the bargain? Is this how you earn customers trust? Disappointed

I understand your disappointment here, and I do think there is always room to improve communication.

If you are happy to PM me, let me find out what is happening and get this squared away ASAP :(
 
The timeouts are not necessarily packet loss, it could be that the network kit gives low priority to ICMP pings and might not respond if the router is busy. You might see more accurate results using MTR or tests run over time.

I guess you could be right, how would one then explain in game latency that sits around 1745ms ?

Or are you in agreement with the advice I received from AH Support, regarding the sudden high latency issues and packet loss I am experiencing of late?

This is the reply I got, after noting that in game latency is ~ 1.7K ms

Quote:

"If the server is based in the UK, those milliseconds are fine.

Intermittent problems of this kind can be particularly difficult to resolve because if it's just a simple Configuration issue, you tend to get consistency, even if that consistency manifests itself in poor results.

We hope that by using this process of elimination we are able to find the cause of the Intermittent Connectivity issue you are experiencing.

a.) Please disconnect all equipment from the router: including wireless printers, tablets, cell phones, gaming devices etc..

b.) Disable the wireless completely on the router and connect directly with cable to your PC. (Test with just one PC connected directly to the cable) Leave only the router connected for an hour. If that is stable begin to add on 1 device every 30 minutes to see which device is causing the disconnection.

1. Router/Modem
If the front-facing LED lights are solid and flashing green, in general terms this means that the device is working well. If it flashes Red, please contact us for further diagnostics.

Here are three ways to test your router so as to verify if it is functioning well :

1.1. Take the router to the store at which you purchased it, and ask them to test it for you (there is no fee for this).

1.2. Swap your current router with a router which is known to be functioning properly.

1.3 Take your router to a family member/friends home and test it there.

It is also important to check your micro filters by:

2. Filters
Ensure that all filters have not been accidentally moved or disconnected. Filters generally don't need replacement, however to test them, disconnect the
phone lines one at a time to see if the problem persists. If so, replace the filter/s.

Unplugging everything from your telephone line and connect your router directly to your master telephone socket .

If this rectifies the problem, then something which you had unplugged, was the cause. Find it by reconnecting your devices systematically and checking for problems after each one.

If this doesn't fix the problem, try another micro filter.

3. Weather
If your intermittent ADSL connectivity began shortly after poor weather (heavy rains, hail, etc).
If normal wear and tear corroded, or weather damaged the wiring is suspected, you may want to check for dilapidated telephone wires in the exposed areas outside of your home.

4.Hardware
Viruses, Trojans and operating system updates can change the configuration of your operating system.

You can download Super Anti Spyware( there is a free version available). Install it on the PC , perform an update and then a complete scan on the PC’s to remove viruses) .

5. Frequency emitting devices.
A high tech alarm system, electric fencing, cordless phones ,wireless devices or any other frequency emitting device which may be near your network can cause intermittent connectivity. Change the frequency of these devices if you suspect this."

PS: I wanted to burst out laughing when I read the reply to my fault log, as I have seen this exact same generic "copy and paste" reply last year when AH's service went downhill (before AH admitted they had a problem and introduced the POC and later the new network).

Sadly I realised that the AH Support member honestly believed that the generic response was helpful to my problem, so I ended up crying.

Please note that I do not log/report the occasional lag spike/problem immediately when it occurs. I normally live with it for a week or two. Only when it consistently repeats itself do I seek assistance. Judging by the posts on this thread of late, I am convinced that I am not the only one experiencing problem with the service provided by AH.

Is it honestly AH's opinion that the root cause is indeed on my end (e.g. my router, my PC, my Telkom ADSL connection, etc)?
 
Last edited:
I understand your disappointment here, and I do think there is always room to improve communication.

If you are happy to PM me, let me find out what is happening and get this squared away ASAP :(

Many thanks Afriman for the assistance with escalating the issue and especially also to Nkosi from Afrihost Critical Care for sorting out the migration and line speed this morning. The quick turnaround to get everything sorted has really made my day!
 
Last edited:

I hate to throw a fellow team member under the bus but I do think sometimes we try to swat a fly with a shotgun. the possible causes of latency can literally be anywhere along the chain, but systematic troubleshooting will show you exactly where that link in the chain is. A traceroute and speedtest are always a great place to start, but I think this predefined reply is designed to eliminate as much possible interference on the client side before they potentially colour the tests that come through.
 
Many thanks Afriman for the assistance with escalating the issue and especially also to Nkosi from Afrihost Critical Care for sorting out the migration and line speed this morning. The quick turnaround to get everything sorted has really made my day!

Fantastic - really glad to hear that you got sorted :)
 
I hate to throw a fellow team member under the bus but I do think sometimes we try to swat a fly with a shotgun. the possible causes of latency can literally be anywhere along the chain, but systematic troubleshooting will show you exactly where that link in the chain is. A traceroute and speedtest are always a great place to start, but I think this predefined reply is designed to eliminate as much possible interference on the client side before they potentially colour the tests that come through.

I do get the "generic" replies, but ......... even via this forum have I pasted the results of so many tests AH requested of me (a mere search against my user name will reflect the results), yet ...... here I am, an AH client with definite AH service related problems (imo anyways).

As you are aware, I have even conducted the same tests requested of me (using the exact same equipment), but merely switching ISP's and the results are different.

How much longer will AH remain in the denial stage, before AH investigate the problem on their end. I am pretty confident that by now I have ruled out the possibility that the root cause is without a doubt not on my end.

Towards the end of last year, when I experienced exactly the same phenomenon, I was handed over to the CC team, shortly after that, the symptoms disappeared after more and more AH clients logged similar experiences and the case was closed. Which leaves me with the impression that AH remains in denial for a few months on negative client experiences and continually claim that it is caused by everything outside of AH control. After a very long time, when clients persistently log these issues, will AH eventually look internally for a root cause and hopefully provide a solution.

Alternately, please provide me with some more hoops to jump through, so that a solution can be found for this problem (mainly because it is most certainly taking the "joy" out of my internet experience).

Kind regards
 
Last edited:
I do get the "generic" replies, but ......... even via this forum have I pasted the results of so many tests AH requested of me (a mere search against my user name will reflect the results), yet ...... here I am, an AH client with definite AH service related problems (imo anyways).

As you are aware, I have even conducted the same tests requested of me (using the exact same equipment), but merely switching ISP's and the results are different.

How much longer will AH remain in the denial stage, before AH investigate the problem on their end. I am pretty confident that by now I have ruled out the possibility that the root cause is without a doubt not on my end.

Alternately, please provide me with some more hoops to jump through, so that a solution can be found for this problem (mainly because it is most certainly taking the "joy" out of my internet experience).

Kind regards

We definitely investigate on our side and try to replicate the results we get. I think it's also reasonable to understand that once we make major changes to address a problem, previous tests have little or no value anymore and we need to run fresh test to see if the same issue occurs or if new artefacts may arise.

I know that some significant changes were made in light of the reports late last week and over the weekend, so we'd definitely like people who had a problem over that time to retest and report back.
 
So my question remains the same - what test do you want me to run to convince you that I do have an issue?

Yesterday I ran ping tests and trace route tests, after confirming packet loss with ping plotter. I even posted a screenshot of in-game latency to an european server, reflecting the ~1.7K ping.

As noted, the reply I got on these tests is that "If the server is based in the UK, those milliseconds are fine."

Somehow, I believe that 1.7K ms to anywhere on this planet is "not" fine.
 
So my question remains the same - what test do you want me to run to convince you that I do have an issue?

Yesterday I ran ping tests and trace route tests, after confirming packet loss with ping plotter. I even posted a screenshot of in-game latency to an european server, reflecting the ~1.7K ping.

As noted, the reply I got on these tests is that "If the server is based in the UK, those milliseconds are fine."

Somehow, I believe that 1.7K ms to anywhere on this planet is "not" fine.

Can you please run the same tests again, now that the changes have been put into effect, and then mail them to me on [email protected] along with your contact details and I'll make sure we work with you to find the cause of the issue.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X