If DSLReports is giving you an A instead of A+ but you could get an A+ on the R1 why does this occur? Does that mean that Anti-Bufferbloat isn't working?
The reason you do not get an A+ is because our enterprise level deep packet inspection analyses the first few packets of the test, this means that DSLReports misreads the result of the bufferbloat test. It is not Anti-Bufferbloat not being able to get an A+, it is DSLReports misreading our DPI as bufferbloat/latency when it is not.The XR500 also has hardware accelaration which means it is a seriously beast piece of kit meaning it can do QoS at gigabit speeds easily so it has absolutely no trouble mitigating local congestion. You're getting the best QoS on the planet so nothing to worry about!
If you want to know if Anti-Bufferbloat is actually working we recommend using PingPlotter (Here's a quick guide on how to use it doing the following tests):
- Saturate your connection as much as possible (download, stream HD videos etc), then do a PingPlotter test and see how much your ping rises.
- Then do the same test except all you do is set Anti-Bufferbloat to 'Always' and put the sliders down to 70/70. You WILL see a substantial difference here.
Just to reiterate, bufferbloat (lag/latency) only occurs when your connection is saturated. With Anti-Bufferbloat enabled your network is never allowed to become saturated and therefore you do not experience bufferbloat.