Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
Unhappy438 said:
You were more or less until yesterday.



This again :erm:, im not trying to get personal, maybe its just the way you interpret my post style but its not my intention . Its about you guys approaching problems differently and you might be able to fix them in a timeous manner. They do say admittance is the first step of recovery, so at least Afrihost has taken its first step and i hope you're able to get through the next steps of fixing the issues quickly.
Click to expand...

We're having things followed up with our team again around QUIC, but for now - a fix is to disable it in Chrome itself.
 
AfriMan said:
From this test (and the previous tests I recall seeing in your posts):

Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.2
2 * * * Request timed out.
3 13 ms 76 ms 81 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194
]
4 11 ms 12 ms 25 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 26 ms 12 ms 12 ms 196.35.115.136
6 11 ms 12 ms 12 ms mi-za-cpt-p8-te0-0-0-0.ip.isnet.net [168.209.6.1
3]
7 19 ms 16 ms 13 ms css1-ctn-gi0-1.ip.isnet.net [168.209.2.10]
8 11 ms 10 ms 11 ms 196.36.84.154
9 38 ms 29 ms 29 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.13.66]
10 29 ms 29 ms 29 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
11 32 ms 30 ms 30 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 32 ms 38 ms 31 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 28 ms 29 ms 35 ms www.mybroadband.co.za [197.242.89.170]

Trace complete.

This jump in latency tells me something is not great here. Looking at the rest of the trace, it could be a very mild spike in intermittent latency. But if you compound this with testing on our network when latency is poor, I think it could be more pronounced.

Generally I wouldn't be very concerned, but I would expect that you would see similar results on our network when there are no known latency problems.
Click to expand...

So the "*" hop is the Exchange and the highlighted hop is the IS IPC Hop?
 
AfriGuy said:
We're having things followed up with our team again around QUIC, but for now - a fix is to disable it in Chrome itself.
Click to expand...

Disabling QUIC stops the apparent throttling, but when allowed to do its thing it accelerates video streaming substantially (approx 30% fewer rebuffers according to reported numbers) since it is geared towards reducing the overhead of renegotiating connections. For us in South Africa this could mean a marked increase in quality of service thanks to a reduction of the length of time spent negotiating with distant servers. Given that I can see noticable improvements when running chrome over other browsers while using networks that don't seem to have a problem with QUIC, (WA and FNBConnect are two I've tested), I really do hope we're not going to be asked to accept second best at the dog show for long.

I've stuck with Afrihost this long because you really have given me the best service experience thus far, so I really do hope your team can come up with a solution.
 
Razotter said:
Disabling QUIC stops the apparent throttling, but when allowed to do its thing it accelerates video streaming substantially (approx 30% fewer rebuffers according to reported numbers) since it is geared towards reducing the overhead of renegotiating connections. For us in South Africa this could mean a marked increase in quality of service thanks to a reduction of the length of time spent negotiating with distant servers. Given that I can see noticable improvements when running chrome over other browsers while using networks that don't seem to have a problem with QUIC, (WA and FNBConnect are two I've tested), I really do hope we're not going to be asked to accept second best at the dog show for long.

I've stuck with Afrihost this long because you really have given me the best service experience thus far, so I really do hope your team can come up with a solution.
Click to expand...

I can understand your frustration around this, but you also need to remember that QUIC is an experimental protocol. It may work sometimes, others it won't.
Regardless, our team will run more checkups on this as per my post earlier in the thread.

I also need to stress that absolutely no throttling is being done here.

AfriGuy said:
We're having things followed up with our team again around QUIC, but for now - a fix is to disable it in Chrome itself.
Click to expand...
 
AfriGuy said:
I can understand your frustration around this, but you also need to remember that QUIC is an experimental protocol. It may work sometimes, others it won't.
Regardless, our team will run more checkups on this as per my post earlier in the thread.

I also need to stress that absolutely no throttling is being done here.
Click to expand...

Its an experimental protocol that is currently making approximately 50% of all calls to google servers via Chrome. http://blog.chromium.org/2015/04/a-quic-update-on-googles-experimental.html I'd say its well in the wild and good to go.

And call it whatever you want Afriman, when a stream hits a steady 25KB/s with no fluctuation up or down, I call it throttling.
 
Razotter said:
Its an experimental protocol that is currently making approximately 50% of all calls to google servers via Chrome. http://blog.chromium.org/2015/04/a-quic-update-on-googles-experimental.html I'd say its well in the wild and good to go.

And call it whatever you want Afriman, when a stream hits a steady 25KB/s with no fluctuation up or down, I call it throttling.
Click to expand...

As I've said, if it's something that we can fix on our end we will. We're checking it out again, but for now - disable QUIC in Chrome.
 
AfriMan said:
I'm pretty sure that people have not had problems with Chrome going back several years, as your post suggests, and this was due to recent changes they had made to how they handle Chrome traffic. MTN's network team would be in contact with Google as a network provider, not us directly.
Click to expand...

I made no such suggestion, I was pointing out that all Google products are experimental and in constant state of flux, much like your network.

I think you have spent so long in denial that you assume any one posting is trying to attack you. Please just occasionally take advice in the manner it was intend and stop being so defensive and negative.

Half of the problem with you services are the attitude of certain support staff.
 
AfriMan said:
This looks to me like packet loss occurs outside of our network at the destination host network (in this case optinet). Generally I would say that packet loss of 1 or 2% is not significant and should not really affect your overall experience, but compounded packet loss (which you seem to see on the destination network) might be different. It does seem like your worst responses in latency on our network are pretty bad, but it's hard to say how often that happens, the average seems pretty acceptable and definitely traffic seems pretty good within our network (from this test).

When was the last correspondence from Critical Care.
Click to expand...

The problem with packet loss is it corrupts data or can make larger chunks have to be resent... increasing bandwith usuage and increasing ping times in games. Well this is how I understand it. It also causes webpages to load incorrectly and audio or video streams to stall.

last communication was 10th october 2014... but i canceled and did not want to give feedback on a prodcut i no longer used.

I have a 4gb capped as backup and it recently dawned on me how badly this performs for gaming or even general browsing.
 
caroper said:
I think you have spent so long in denial that you assume any one posting is trying to attack you. Please just occasionally take advice in the manner it was intend and stop being so defensive and negative.
Click to expand...

+1
 
bgotapen said:
The problem with packet loss is it corrupts data or can make larger chunks have to be resent... increasing bandwith usuage and increasing ping times in games. Well this is how I understand it. It also causes webpages to load incorrectly and audio or video streams to stall.

last communication was 10th october 2014... but i canceled and did not want to give feedback on a prodcut i no longer used.

I have a 4gb capped as backup and it recently dawned on me how badly this performs for gaming or even general browsing.
Click to expand...

That was a while ago, I'm sure stacks has changed since Oct 2014 :)
Drop me a PM with the deets if you'd like me to have anything followed up on for you though.
 
caroper said:
I made no such suggestion, I was pointing out that all Google products are experimental and in constant state of flux, much like your network.

I think you have spent so long in denial that you assume any one posting is trying to attack you. Please just occasionally take advice in the manner it was intend and stop being so defensive and negative.

Half of the problem with you services are the attitude of certain support staff.
Click to expand...

We're definitely here to listen, and to engage with you guys. Let's just take it down to a dull roar :p
 
smtp.afrihost.co.za is timing out. Can't send emails through Outlook. Had to switch to IS.
 
Totempole said:
smtp.afrihost.co.za is timing out. Can't send emails through Outlook. Had to switch to IS.
Click to expand...

Sorry about that :( I'm not seeing any issues on our SMTP server, out of interest, have you tried switching around DNS servers to see if that helps at all?
 
i know 2 for 1 top ups aren't guaranteed every month (except for plus) but are you guys doing it this month ?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X