Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
djbrendan said:
ok so everything seems fine on telkoms hardware side

Your packet loss was 0%.
Your average ping was 16ms.
Your maximum ping was 22ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:


Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 22ms, Average = 16ms

but my average ping is above 70ms lately and packet loss is back again at 10%
At night my ping would even hit 200ms and stay there for a hour or two.. :/

this is it atm
View attachment 207778
Click to expand...

Looking at that ping test which is pinging the ESR Directly so it tests your router, line, exchange and ESR for congestion and packet loss (There is none)

The issue lies with afrihost and not with your line/exchange.
 
Orihalcon said:
You speak about trust and relationship with you clients. Fine. Loyalty and all that. I take myself as an example in this. If I had stuck to my "loyalty" I would STILL be having an unusable gaming and Mumble experience with Afrihost in the evenings when I need my connection to work. And this would have been week 15 since the problem was reported. How do you expect customer loyalty to trump that?

Yea...loyalty while having almost 3 months of a useless experience (and counting going by the posts here).

Please. I love you guys and what you do on this forum. The level of crap you have to deal with and just SOAK up from the rants and aggravated posts must require some the most ZEN mind control ever - but your product offering is not up to scratch at present. THAT is the problem.

Someone higher up on the totem pole needs to step up their game and get this resolved. Your reputation is taking a dive.
Click to expand...

I can't dispute that there have been a few issues that keep cropping up on some of our accounts, but this really does have the Higher-Ups full attention at the moment. A lot of work is being down in the background, and this isn't always obvious to us, myself included.

At no point do we want you guys to stop giving us feedback, the information that you provide really helps us a great deal in figuring out if there are issues, and what the issues are.
 
djbrendan said:
ok so everything seems fine on telkoms hardware side

Your packet loss was 0%.
Your average ping was 16ms.
Your maximum ping was 22ms.

Looking at your average ping, your line seems to be running perfectly.
It seems that your maximum ping is also good. If there are any issues, they most probably lie with your ISP

Detailed Report:


Pinging 155.239.255.250 with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=22ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=15ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=17ms TTL=63
Reply from 155.239.255.250: bytes=32 time=16ms TTL=63

Ping statistics for 155.239.255.250:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 22ms, Average = 16ms

but my average ping is above 70ms lately and packet loss is back again at 10%
At night my ping would even hit 200ms and stay there for a hour or two.. :/

this is it atm
View attachment 207778
Click to expand...

Which Team Speak server are you connecting to at the moment?

That ping of 70ms, is that on your local speedtests or to the Team Speak server?
 
Aaand back again..

4290831164.png


Yay
 
AfriGenie said:
Which Team Speak server are you connecting to at the moment?

That ping of 70ms, is that on your local speedtests or to the Team Speak server?
Click to expand...
It's not only TS,dota,battlefield they all just jump and stay there for a while ,while the packet loss as well just stays..
 
djbrendan said:
It's not only TS,dota,battlefield they all just jump and stay there for a while ,while the packet loss as well just stays..
Click to expand...

Are you able to test the latency and packet loss as they stand at this moment?

Do your connection speeds also drop when you see your latency spike to 200ms in the evenings?
 
Looks like any time past 7 (thats a gestimate time - But its always during peak evening times) pings go through the roof... Also most, or at least alot of the gaming servers, are hosted by gameservers.com which uses Mweb as far as i can remember...

So i would imagine that it is a switching/routing issue when trying to get to the mweb network...

I would take a look at where this "network switch" takes place and check the rules and policy's of those devices
The last device on afrihost network before it goes to the mweb network...

This is all just my brain logic working, i could be extremely wrong.
 
DJZassie said:
Looks like any time past 7 (thats a gestimate time - But its always during peak evening times) pings go through the roof... Also most, or at least alot of the gaming servers, are hosted by gameservers.com which uses Mweb as far as i can remember...

So i would imagine that it is a switching/routing issue when trying to get to the mweb network...

I would take a look at where this "network switch" takes place and check the rules and policy's of those devices
The last device on afrihost network before it goes to the mweb network...

This is all just my brain logic working, i could be extremely wrong.
Click to expand...

This is definitely something we are investigating, at the moment we're planning on testing those gaming servers during the periods that we seem to receive the most Users raising the latency and packet loss issue.

From what we've been able to figure out, it definitely is not an issue at all times, but mainly during the peak times you mentioned.
 
AfriGenie said:
This is definitely something we are investigating, at the moment we're planning on testing those gaming servers during the periods that we seem to receive the most Users raising the latency and packet loss issue.

From what we've been able to figure out, it definitely is not an issue at all times, but mainly during the peak times you mentioned.
Click to expand...

Iv seen jumpy or higher than normal ping to mweb based servers before that 8pm-10pm peak time when the ping is still stable to the IPC. In the week iv noticed it starts between 10am and 12pm and stabilizes at around 5pm and then the peak time hits and after that its fine again. I only get packetloss during the peak time however.
 
NNTP seems to have improved for now, but ONLY on paid server.

Afrihost news server (news.afrihost.co.za) is intermittent, one minute 0 KB/s or close to it, next minute almost normal, then back to slow or timeout.

Any update?
 
Loppas said:
Iv seen jumpy or higher than normal ping to mweb based servers before that 8pm-10pm peak time when the ping is still stable to the IPC. In the week iv noticed it starts between 10am and 12pm and stabilizes at around 5pm and then the peak time hits and after that its fine again. I only get packetloss during the peak time however.
Click to expand...

As you pointed out, I don't think it is related to IPC capacity, but rather the routing to specific MWeb servers during peak times. For the moment we're looking at the if there are any changes we can make that will improve this.
 
acp said:
NNTP seems to have improved for now, but ONLY on paid server.

Afrihost news server (news.afrihost.co.za) is intermittent, one minute 0 KB/s or close to it, next minute almost normal, then back to slow or timeout.

Any update?
Click to expand...

Our own NNTP server has been acting up recently, our Admins are making a few changes to that to get it running smoothly again. This appears to be separate to the limited NNTP that you guys have reported.

Has there been any other changes on your connection?
 
AfriGenie said:
As you pointed out, I don't think it is related to IPC capacity, but rather the routing to specific MWeb servers during peak times. For the moment we're looking at the if there are any changes we can make that will improve this.
Click to expand...

Possiblly a router maxing out somewhere causing a round about trip to the mweb servers? or causing a que to form thus latency to rise? :)
 
AfriGenie said:
Our own NNTP server has been acting up recently, our Admins are making a few changes to that to get it running smoothly again. This appears to be separate to the limited NNTP that you guys have reported.

Has there been any other changes on your connection?
Click to expand...

No changes to my connection. All running fine except for Afrihost NNTP.
 
acp said:
No changes to my connection. All running fine except for Afrihost NNTP.
Click to expand...

Thanks for checking!

Our Team seems to have found the cause, and they should have the News Server running along at full steam in no time!
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X