Why stability needs its own test
An unstable connection is one that works well most of the time and fails for a few seconds at a time. That is exactly the kind of fault a quick test misses. A three-second speed test that happens to fall between two drops reports a perfect line, and you are left wondering why the call froze ten minutes ago.
This internet stability test defaults to 60 seconds and 3,000 packets, one every 20 milliseconds. Every packet is drawn on the strip, so a drop shows as a cluster of red marks at the moment it happened and a spike shows as a tall tower. After the run, the detail panel counts the "spiky seconds": seconds in which at least 5% of packets were lost or the median ping more than doubled. One spiky second in a minute is normal life. Several is a pattern worth chasing.
Reading the timeline
- Flat and clean. Low even ticks and no red. The connection is stable; if you still have problems, they are further away than your own line.
- Red marks spread evenly. A constant small loss. Usually a physical fault: a damaged cable, a bad connector, or a line running at its limit.
- Red clusters. Short bursts of loss. Almost always wifi interference, a router that is struggling, or another device starting a big transfer.
- Towers without red. Ping spikes. Packets arrive but late. Usually a queue building up somewhere, often on your own upload.
- A gap of red across the whole strip. The connection dropped completely for that moment. If it happens repeatedly, check the router's log for disconnections.
Testing stability properly
Run the test at the time your problem usually happens. A connection that is stable at 10 in the morning and unstable at 9 in the evening is telling you about congestion on your provider's network, and a morning test will never show it. Run it from the room where the problem happens, on the device that has it: the phone in the kitchen, not the desktop next to the router.
Then change one thing and run it again. Move closer to the router, switch the laptop to a cable, turn off the console downloading in the background. Because every run shows the same timeline, two runs side by side make the cause obvious in a way an average never does. The wifi versus ethernet guide walks through that comparison.
Stability for streaming, calls and games
Different uses fail at different points. Streaming video buffers several seconds ahead, so it survives short drops that would end a call. Video calls buffer a fraction of a second and freeze or drop to low quality during a burst of loss. Online games buffer almost nothing and show a burst as rubber-banding or a disconnect. The verdict list under the result rates the run for each use separately, so an unstable line that is still fine for Netflix will say so.