I want to understand the differences between the baseline, latency, and outage flags you use for speed testing. Based on your answer, I am fairly informed about what triggers baseline.
> The only differences you might see are because of the automated testing rather than you manually testing at the time you feel there is a problem or not. When you enable speed testing, the test will happen on a regular basis called a baseline but also based on the following two conditions.
The agent software keeps track of pings averages and does an ongoing regular low bandwidth speed test. If pings go over the average that the agent has built up for the connection it is monitoring, this will trigger a speed test. If the result of the low speed test is fairly slower than the average it has built up, this will trigger a speed test.
I still do have a few questions:
* What are the test parameters? e.g.
How much test data is sent when testing download/upload?
Is it also just testing download/upload once?
What specific sites/servers are you pinging/hitting when testing?
Like I said in my earlier post, the closest results to your software I have seen is testmy.net. Not like the ISP's recommended tool which is Ookla's speed test, which I like to contest. SLA with ISP is indeed best effort, but the local governing body mandates 80-90% reliability, with at least 50% when best effort is considered. Which is why I am in mediation with them. I need to ascertain first the authenticity of your speed test methodology vs Ookla and fast.com to build a more solid case. So far, testmy.net is the one which yields the closest to your results. I run it in 5 minute intervals up to 100 times. Only downside is it is not constant like your service.
I would also like to know what triggers latency and outage speed tests. Thank you!