Afrihost New Network Feedback

Status
Not open for further replies.
I thought it might be my laptop, but international is definitely on the go slow. Switched to Mweb and everything 100%.

Even mybb is slow, takes ages to load a thread.

Speedtest and latency both normal though.
 
Johnatan56 said:
Agreed that it isn't ISP related. I have posted pings from a phone, a laptop and both desktops on this thread. I have also tried using my old modem, same results (I only swapped the old one out due to poor WiFi performance, 802.11g) using only LAN.

I have currently 2 Desktops, 1 laptop and 3 phones connected, all the other devices I switched off. There were no problems this morning or any time before that with the exception of yesterday evening. Any pings to router are fine, LAN is <1ms and WiFi 1-2ms.

This is from the laptop bras.afrihost.com ping:
Code: 
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.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=1042ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2011ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2694ms TTL=63
Reply from 155.239.255.250: bytes=32 time=75ms TTL=63
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.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2571ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
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.
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.
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.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=2045ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3568ms TTL=63
Reply from 155.239.255.250: bytes=32 time=24ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Reply from 155.239.255.250: bytes=32 time=3072ms TTL=63
Reply from 155.239.255.250: bytes=32 time=26ms TTL=63
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Click to expand...

Response times to the modem don't necessarily mean that the modem or router is functioning perfectly on all protocols. Nor does it mean it is routing efficiently on all protocols. It just means that ICMP is routing fine. TCP and UDP traffic operate a little differently, so always best to test thoroughly when this sort of thing happens. Pinging bras is fine but it doesn't show the step before, and in addition an ICMP response time may be different to TCP packets or UDP packets traversing the same route (majority of the data you consume is TCP and UDP protocol). So I'd suggest, in the efforts of going the extra mile here to rule out all other possibilities, to test with another modem with the splitter off the line, and see if you can replicate. If you can, it sounds to me like rather odd exchange congestion or a line fault. If the results are not replicated, you can very easily identify the modem/router as the culprit...
 
AfriFella said:
Very well put DJ. :) Apologies for my jump to conclusion
Click to expand...

It's easy to do. In this case with the speeds being fine but latencies being a problem (while browsing is perfect) it doesn't sound like your typical exchange congestion fault, unless Telkom are implementing port shaping/queing at exchanges now, which would be a massive announcement and something that would result in numerous lawsuits. On 3500ms latency and majority packets loss along the route, you're going to find massive slow-downs in speed and browsing will hardly work.

One thing to take note of is that numerous Zyxel modems have some firmware issues and they are not relaying ICMP packets properly in our testing. If the client is using a Zyxel modem we're by and large suggesting to test with another modem as there are big issues there right now. In short, they're crap until they get their firmware working properly. Even other modems are suffering a bit where log files are set to record everything and the log itself is consuming all router memory, meaning the router acts rather weirdly, randomly reboots, or just freezes up entirely. It's no isolated to Zyxels but it's a very common issue with some of them. They report perfect response times during this time but are in fact having a little stroke internally (and not the good kind)...
 
DJ... said:
Response times to the modem don't necessarily mean that the modem or router is functioning perfectly on all protocols. Nor does it mean it is routing efficiently on all protocols. It just means that ICMP is routing fine. TCP and UDP traffic operate a little differently, so always best to test thoroughly when this sort of thing happens. Pinging bras is fine but it doesn't show the step before, and in addition an ICMP response time may be different to TCP packets or UDP packets traversing the same route (majority of the data you consume is TCP and UDP protocol). So I'd suggest, in the efforts of going the extra mile here to rule out all other possibilities, to test with another modem with the splitter off the line, and see if you can replicate. If you can, it sounds to me like rather odd exchange congestion or a line fault. If the results are not replicated, you can very easily identify the modem/router as the culprit...
Click to expand...

I managed to isolate it to an android phone I missed when going over all the devices, didn't a family member didn't take it with. It's most definitely an app on it, turn WiFi off on it, all pings/tracerts are fine, turn it on and anything latency related dies. Instant DC from WoW/LoL. Just not sure which app is the cause, going to check more thoroughly tomorrow morning.
 
Johnatan56 said:
I managed to isolate it to an android phone I missed when going over all the devices, didn't a family member didn't take it with. It's most definitely an app on it, turn WiFi off on it, all pings/tracerts are fine, turn it on and anything latency related dies. Instant DC from WoW/LoL. Just not sure which app is the cause, going to check more thoroughly tomorrow morning.
Click to expand...
Is it a Huawei? If so it's not an app but the phone itself. Experienced this myself with Huawei phones. Glad you found the culprit. It certainly didn't sound like congestion to me. If it is an app please let me know so I can add it to our internal KB...
 
DJ... said:
Is it a Huawei? If so it's not an app but the phone itself. Experienced this myself with Huawei phones. Glad you found the culprit. It certainly didn't sound like congestion to me. If it is an app please let me know so I can add it to our internal KB...
Click to expand...

LG G3 Beat, I have the same phone as well, not a problem. The phones been in use for over a year and never had any issues till today.
 
May have updated firmware or it certainly could be an app then. Would like to know what it is...
 
Of course you can...

images
 
DJ... said:
One thing to take note of is that numerous Zyxel modems have some firmware issues and they are not relaying ICMP packets properly in our testing. If the client is using a Zyxel modem we're by and large suggesting to test with another modem as there are big issues there right now.
Click to expand...

1173.gif



Just my luck. I have a Zyxel SBG3300-N waiting in my study for when my fibre gets installed.

img_sbg3300-n000_p_380.jpg
 
I am currently on the Home Uncapped DSL 2Mbps. I want to change to Premium Uncapped 2 Mbps DSL. If I change it on the client zone will it be effective immediately?
 
Didnt tead the thread for quite a while but when is the when is the connectivity tan in client zone gona stop showing both afrigreen and afrihost tabs?
 
Johnatan56 said:
I am going to keep it running, anyone know how to set up a netgear WN2000RPT as a WiFi Device, so that it receives it through an ethernet cable? I used to have it set up as a repeater.

EDIT: Plug and paly it seems.

EDIT2: So if I daisy chain LAN cables torrents work, but via WiFi of the extender, not. This is strange. Going to see if any latency games work.

EDIT3: And the latency affected games work fine over WiFi. Just going to go get a new router this week, should solve it I think. And torrents have started working now. (on WiFi). I think maybe the router had enough of too many devices (when everyone is home it's 15-20 devices).

EDIT4:


Me too. Not glad about having to get a new router.

EDIT5: I hate this s**t. Getting the high pings on this router as well now. LAN, not WiFI.
Code: 
Reply from 155.239.255.250: bytes=32 time=471ms TTL=63
Reply from 155.239.255.250: bytes=32 time=724ms TTL=63
Reply from 155.239.255.250: bytes=32 time=646ms TTL=63
Reply from 155.239.255.250: bytes=32 time=549ms TTL=63
Reply from 155.239.255.250: bytes=32 time=652ms TTL=63
Reply from 155.239.255.250: bytes=32 time=528ms TTL=63
Reply from 155.239.255.250: bytes=32 time=535ms TTL=63
Reply from 155.239.255.250: bytes=32 time=505ms TTL=63
Reply from 155.239.255.250: bytes=32 time=315ms TTL=63
Reply from 155.239.255.250: bytes=32 time=318ms TTL=63
Reply from 155.239.255.250: bytes=32 time=355ms TTL=63
Reply from 155.239.255.250: bytes=32 time=317ms TTL=63
Reply from 155.239.255.250: bytes=32 time=383ms TTL=63
Reply from 155.239.255.250: bytes=32 time=540ms TTL=63

Must be something on the WiFi then, the moment I disconnect the extender all is fine.

EDIT6: Notice where I connect/disconnect the Netgear/WiFi.
Code: 
Reply from 155.239.255.250: bytes=32 time=563ms TTL=63
Reply from 155.239.255.250: bytes=32 time=581ms TTL=63
Reply from 155.239.255.250: bytes=32 time=565ms TTL=63
Reply from 155.239.255.250: bytes=32 time=511ms TTL=63
Reply from 155.239.255.250: bytes=32 time=609ms TTL=63
Reply from 155.239.255.250: bytes=32 time=689ms TTL=63
Reply from 155.239.255.250: bytes=32 time=493ms TTL=63
Reply from 155.239.255.250: bytes=32 time=548ms TTL=63
Reply from 155.239.255.250: bytes=32 time=519ms TTL=63
Reply from 155.239.255.250: bytes=32 time=515ms TTL=63
Reply from 155.239.255.250: bytes=32 time=550ms TTL=63
Reply from 155.239.255.250: bytes=32 time=512ms TTL=63
Reply from 155.239.255.250: bytes=32 time=391ms TTL=63
Reply from 155.239.255.250: bytes=32 time=186ms TTL=63
Reply from 155.239.255.250: bytes=32 time=531ms TTL=63
Reply from 155.239.255.250: bytes=32 time=550ms TTL=63
Reply from 155.239.255.250: bytes=32 time=32ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=20ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=21ms TTL=63
Reply from 155.239.255.250: bytes=32 time=23ms TTL=63
Reply from 155.239.255.250: bytes=32 time=217ms TTL=63
Reply from 155.239.255.250: bytes=32 time=356ms TTL=63
Reply from 155.239.255.250: bytes=32 time=407ms TTL=63
Reply from 155.239.255.250: bytes=32 time=519ms TTL=63
Reply from 155.239.255.250: bytes=32 time=530ms TTL=63
Reply from 155.239.255.250: bytes=32 time=635ms TTL=63
Reply from 155.239.255.250: bytes=32 time=542ms TTL=63
Reply from 155.239.255.250: bytes=32 time=576ms TTL=63
Reply from 155.239.255.250: bytes=32 time=429ms TTL=63
Reply from 155.239.255.250: bytes=32 time=323ms TTL=63
Reply from 155.239.255.250: bytes=32 time=317ms TTL=63
Reply from 155.239.255.250: bytes=32 time=456ms TTL=63
Reply from 155.239.255.250: bytes=32 time=442ms TTL=63
Reply from 155.239.255.250: bytes=32 time=365ms TTL=63
Reply from 155.239.255.250: bytes=32 time=298ms TTL=63
Reply from 155.239.255.250: bytes=32 time=340ms TTL=63
Reply from 155.239.255.250: bytes=32 time=363ms TTL=63
Reply from 155.239.255.250: bytes=32 time=374ms TTL=63
Reply from 155.239.255.250: bytes=32 time=386ms TTL=63
Reply from 155.239.255.250: bytes=32 time=349ms TTL=63
Reply from 155.239.255.250: bytes=32 time=305ms TTL=63
Reply from 155.239.255.250: bytes=32 time=412ms TTL=63
Reply from 155.239.255.250: bytes=32 time=263ms TTL=63

EDIT Might have found the cause. It was an errant phone using both e-mail and facebook, the e-mail was trying to resend a failed e-mail constantly and facebook was uploading/downloading. Moment I click save the ping spikes -.-
Most definitely that device, moment I turn off it's WiFi connection everything is stable.

EDIT hopefully final. Went back to the pace router, everything is good. Back to 20ms to bras.afrihost.com. Was the rogue android device I missed when turning off all the WiFi devices.

EDIT I can log into WoW, Smite, LoL, HotS, etc. which I couldn't do before. Thanks for the help everyone. First rogue device I've ever had on my network :D

View attachment 338418
Click to expand...

Is there a MyBB award for most edits in a single post? Haha, love it :)

Glad you sorted this out :)
 
ABCpt said:
So, again facebook, gmail and my vps server is slow. Connect via Webafrica backup account and everything is instant. On Afrihost pings seem fine, it's just getting the actual content which is frustratingly slow.
Click to expand...

That is definitely concerning. What sort of throughput are you getting?
 
blunt said:
Yeah, international is ridic at the moment, sites barely load - can barely get my pop/imap email.
Click to expand...

Can you post a traceroute?

We did run some changes to improve our DNS routing, so this may have momentarily affected performance, but we should not be seeing this now :(
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X