Afrihost Uncapped ADSL Feedback (Pt3)

Status
Not open for further replies.
Can confirm that mumble for the most part works perfectly when shaping is active EARLY in the day...

Once it comes to evening and a lot of people are using services then it goes to pot. Just adding my 2c.

Sure it's the software that is the issue here as when using capped or turbo charging resolves the problem - though a little packet still remains even on capped.

I've already switch anyway. Oh well. Afrihost capped will become my secondary back up. I'll be back using you folks once your network management has matured.
 
Orihalcon said:
Can confirm that mumble for the most part works perfectly when shaping is active EARLY in the day...

Once it comes to evening and a lot of people are using services then it goes to pot. Just adding my 2c.

Sure it's the software that is the issue here as when using capped or turbo charging resolves the problem - though a little packet still remains even on capped.

I've already switch anyway. Oh well. Afrihost capped will become my secondary back up. I'll be back using you folks once your network management has matured.
Click to expand...

I think the biggest issue was the we started seeing a lot of P2P traffic being marked as VOIP traffic over the past few weeks, and this may have caused our network management software to start treating VOIP traffic slightly differently as it now had to inspect individual packets, so whilst it isn't truly shaping P2P it was increasing the latency and delay on VOIP.
 
AfriGenie said:
I think the biggest issue was the we started seeing a lot of P2P traffic being marked as VOIP traffic over the past few weeks, and this may have caused our network management software to start treating VOIP traffic slightly differently as it now had to inspect individual packets, so whilst it isn't truly shaping P2P it was increasing the latency and delay on VOIP.
Click to expand...
A sound argument. See what I did there? Badum-tsh. I'll see myself out.
 
Things are looking up. I have been able to steam YT at 480p without any issue for the last little while. This 16:30 to 17:30 frame always seems to be high traffic, even without network issues, so this makes me happy.

There does seem to be a slight bit of latency on http and https, but a ping test to London came back at a blistering 165ms, I am used to 180-190ms. I'll feedback on TS tomorrow morning, hopefully the management system can differentiate between VoIP and P2P with its new rules.
 
I haven't dropped connection from TS this evening, which is an improvement, but my ping through to a US server is 340ms, which I would expect to be in the 260-280 range.
 
CapetonianMike said:
I haven't dropped connection from TS this evening, which is an improvement, but my ping through to a US server is 340ms, which I would expect to be in the 260-280 range.
Click to expand...

That's definitely as good as we'd like it. Is the connection stable or giving you issues in game?
 
AfriMan said:
That's definitely as good as we'd like it. Is the connection stable or giving you issues in game?
Click to expand...

I ended up having to switch over to a different ISP early hours of the morning (ie 2am) because of ping jumps on TS that made it an issue (I was doing something "critical", and internet space ships is real, so no playing around). I switched over to Axxess and saw similar spikes but not as bad, so maybe it wasn't an AH specific thing. I was playing Eve Online and that has been mostly fine on my AH account this entire episode.

I have a few WebExs scheduled for this afternoon with a client's Boston and London offices, I'll let you know if I have any issues on those.
 
Can an AH rep please help me, I am having crazy issues with billing in an attempted upgrade. Just tell me what info you need and I will provide it, I have been trying to get into contact but I cant use the phone everytime. I AM ASKING PLEASE
 
DrAnch said:
Can an AH rep please help me, I am having crazy issues with billing in an attempted upgrade. Just tell me what info you need and I will provide it, I have been trying to get into contact but I cant use the phone everytime. I AM ASKING PLEASE
Click to expand...

I am soon leaving for the weekend, I would recommend sending AfriGuy a PM with either your ADSL username or your Afrihost Account number. He is still here for awhile, and will definitely be able to assist with the billing issue.

EDIT: Can you actually send me those details, I'll have a quick look before I leave.
 
Mumble is erratic. From clear to completely unusable. Clears up immediately if I connect to a VPN.


Pinging sortedmumble.cybersense.co.za [152.111.192.233] with 32 bytes of data:
Reply from 152.111.192.233: bytes=32 time=103ms TTL=51
Reply from 152.111.192.233: bytes=32 time=165ms TTL=51
Reply from 152.111.192.233: bytes=32 time=36ms TTL=51
Reply from 152.111.192.233: bytes=32 time=62ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=84ms TTL=51
Reply from 152.111.192.233: bytes=32 time=41ms TTL=51
Reply from 152.111.192.233: bytes=32 time=85ms TTL=51
Reply from 152.111.192.233: bytes=32 time=76ms TTL=51
Reply from 152.111.192.233: bytes=32 time=133ms TTL=51
Reply from 152.111.192.233: bytes=32 time=12ms TTL=51
Reply from 152.111.192.233: bytes=32 time=157ms TTL=51
Reply from 152.111.192.233: bytes=32 time=108ms TTL=51
Reply from 152.111.192.233: bytes=32 time=75ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=68ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=57ms TTL=51
Reply from 152.111.192.233: bytes=32 time=134ms TTL=51
Reply from 152.111.192.233: bytes=32 time=65ms TTL=51
Reply from 152.111.192.233: bytes=32 time=172ms TTL=51
Reply from 152.111.192.233: bytes=32 time=55ms TTL=51
Reply from 152.111.192.233: bytes=32 time=89ms TTL=51
Reply from 152.111.192.233: bytes=32 time=84ms TTL=51
Reply from 152.111.192.233: bytes=32 time=113ms TTL=51
Reply from 152.111.192.233: bytes=32 time=53ms TTL=51
Reply from 152.111.192.233: bytes=32 time=64ms TTL=51

Ping statistics for 152.111.192.233:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 172ms, Average = 87ms
Control-C

Tracing route to sortedmumble.cybersense.co.za [152.111.192.233]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 15 ms 8 ms 105-236-234-65-esr-lo.mtnbusiness.co.za [105.236.234.65]
3 199 ms 150 ms 25 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 10 ms 10 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 128 ms 171 ms 207 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 114 ms 114 ms 129 ms 196.44.31.106
7 143 ms 234 ms 239 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 125 ms 80 ms 150 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 135 ms 49 ms 44 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 53 ms 39 ms 158 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 48 ms 12 ms 13 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 162 ms 125 ms 48 ms 196.41.144.34
13 120 ms 42 ms 25 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 136 ms 109 ms 145 ms 152.111.192.233

Trace complete.

Ping and TraceRt Information.
 
Playing SMITE with little to no lag. Check Clientzone - No Shaping policy applied.
While playing, lag becomes unbearable. Check Clientzone - Shaping policy 18.5 / 6.25...
 
I find it very sad that even with all this additional IPC, and promises that things will get better, Afrihost still need to shape uncapped clients to 18.8% Download/ 6.25% P2P on a Sunday morning.

And if you check the website, the DSL status is green. So this is working as intended :(
 
Sazelza said:
Mumble is erratic. From clear to completely unusable. Clears up immediately if I connect to a VPN.


Pinging sortedmumble.cybersense.co.za [152.111.192.233] with 32 bytes of data:
Reply from 152.111.192.233: bytes=32 time=103ms TTL=51
Reply from 152.111.192.233: bytes=32 time=165ms TTL=51
Reply from 152.111.192.233: bytes=32 time=36ms TTL=51
Reply from 152.111.192.233: bytes=32 time=62ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=84ms TTL=51
Reply from 152.111.192.233: bytes=32 time=41ms TTL=51
Reply from 152.111.192.233: bytes=32 time=85ms TTL=51
Reply from 152.111.192.233: bytes=32 time=76ms TTL=51
Reply from 152.111.192.233: bytes=32 time=133ms TTL=51
Reply from 152.111.192.233: bytes=32 time=12ms TTL=51
Reply from 152.111.192.233: bytes=32 time=157ms TTL=51
Reply from 152.111.192.233: bytes=32 time=108ms TTL=51
Reply from 152.111.192.233: bytes=32 time=75ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=68ms TTL=51
Reply from 152.111.192.233: bytes=32 time=93ms TTL=51
Reply from 152.111.192.233: bytes=32 time=57ms TTL=51
Reply from 152.111.192.233: bytes=32 time=134ms TTL=51
Reply from 152.111.192.233: bytes=32 time=65ms TTL=51
Reply from 152.111.192.233: bytes=32 time=172ms TTL=51
Reply from 152.111.192.233: bytes=32 time=55ms TTL=51
Reply from 152.111.192.233: bytes=32 time=89ms TTL=51
Reply from 152.111.192.233: bytes=32 time=84ms TTL=51
Reply from 152.111.192.233: bytes=32 time=113ms TTL=51
Reply from 152.111.192.233: bytes=32 time=53ms TTL=51
Reply from 152.111.192.233: bytes=32 time=64ms TTL=51

Ping statistics for 152.111.192.233:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 172ms, Average = 87ms
Control-C

Tracing route to sortedmumble.cybersense.co.za [152.111.192.233]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 15 ms 8 ms 105-236-234-65-esr-lo.mtnbusiness.co.za [105.236.234.65]
3 199 ms 150 ms 25 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
4 10 ms 10 ms 9 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 128 ms 171 ms 207 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 114 ms 114 ms 129 ms 196.44.31.106
7 143 ms 234 ms 239 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 125 ms 80 ms 150 ms 196-28-178-141.adsl.mweb.co.za [196.28.178.141]
9 135 ms 49 ms 44 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 53 ms 39 ms 158 ms vl-12-cpt-hscore-2.mweb.co.za [197.84.5.254]
11 48 ms 12 ms 13 ms vp-02-14.bb.ctn.c27.za.net [196.28.178.70]
12 162 ms 125 ms 48 ms 196.41.144.34
13 120 ms 42 ms 25 ms gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234]
14 136 ms 109 ms 145 ms 152.111.192.233

Trace complete.

Ping and TraceRt Information.
Click to expand...

Very strange results here, there's a latency spike up on the 3rd hop, after your exchange and on our network.
Do all your traceroutes look like this?
 
Sazelza said:
Playing SMITE with little to no lag. Check Clientzone - No Shaping policy applied.
While playing, lag becomes unbearable. Check Clientzone - Shaping policy 18.5 / 6.25...
Click to expand...

Odd :(
Do you know what protocols the game uses? If it relies on P2P the traffic may be getting mis-classified.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X