Onlink notes
Why a fast speed test does not prove your internet is reliable
A fast speed-test result is good news. It means the connection moved a lot of data during that test.
It does not prove that the connection stayed healthy before the test or will stay healthy afterward.
Throughput rewards sustained transfer
Speed tests are designed to measure capacity. They send enough traffic to estimate how quickly data can move over a short period.
That makes them good at finding bandwidth problems.
They are much less suited to detecting a five-second outage that happened ten minutes earlier.
Reliability failures can hide between tests
A connection may have excellent throughput and still suffer from:
- brief disconnects;
- DNS failures;
- unstable Wi-Fi;
- severe latency spikes;
- high jitter;
- repeated failed requests.
If the problem has recovered by the time the test begins, the speed result can be completely normal.
This is why intermittent outages need history.
A test can also change the network
A full throughput test deliberately creates load.
That is useful when measuring capacity, but it is not neutral background observation. Continuously running heavy tests would consume bandwidth and could influence the latency and stability you are trying to measure.
Onlink therefore keeps Cloudflare and M-Lab speed tests explicit. It pauses the lightweight main monitor during full speed tests so those measurements do not contaminate each other.
Automatic incident diagnosis also refuses to launch a full speed test.
Reliability should use different evidence
Onlink’s Internet Reliability Score excludes manual speed-test throughput.
Instead it combines:
- availability;
- incident stability;
- latency;
- jitter;
- failed lightweight connection checks.
That design allows a 500 Mbps connection with repeated outages to score worse than a slower connection that stays consistently usable.
Read How to read an Internet Reliability Score for how coverage and component scores affect the result.
When a speed test is the right tool
Run one when you need to answer questions like:
- Is my download capacity close to what I expect?
- Is upload unusually slow?
- Does performance change significantly between providers or networks?
- Is a large transfer limited by the connection?
Those are throughput questions.
When the complaint is “it keeps cutting out,” “calls freeze,” or “sites sometimes stop resolving,” combine a speed test with reliability history rather than treating the speed result as the final verdict.
Use both without confusing them
A complete picture can include both capacity and reliability.
The mistake is assuming one number represents every aspect of the connection.
Internet speed vs. internet reliability explains the distinction in more detail, while latency and jitter cover the interactive side of connection quality.
A fast connection is valuable. A dependable connection is valuable. They are related, but they are not the same measurement.