Connection Stability Test
Sample your latency continuously over minutes and plot it live — the way to catch the intermittent spikes short tests always miss.
Long-run stability monitor
Pings continuously and charts your latency over time so intermittent spikes can't hide.
Idle — choose a duration and press “Start”.
What this test measures
A snapshot test tells you how your connection behaves for a few seconds. A stability test tells you how it behaves over time — which is what actually matters when a call drops at minute 12 or a game rubber-bands once a minute. This monitor pings repeatedly for the duration you choose and plots every sample on a live chart, tracking your minimum, average and maximum latency plus a count of spikes (samples more than double your running average). When it finishes, the result is saved to your test history so you can compare runs or use them as evidence.
How to read your result
A healthy line draws a flat, low chart. The shape matters more than any single number:
| Pattern | Verdict | Likely cause |
|---|---|---|
| Flat line, no spikes | Stable | Healthy connection |
| Occasional spikes | Watch | Wi-Fi interference, background traffic |
| Frequent / regular spikes | Unstable | Bufferbloat, congestion, or ISP fault |
Regular, evenly-spaced spikes often point to bufferbloat — verify it with the bufferbloat test. If samples vanish entirely, you may be dropping traffic; confirm with the packet loss test.
Frequently asked questions
- Why run a long test instead of a quick one?
- Most connection problems are intermittent. A 10-second test can easily miss the spike that drops your call or kills your game. Sampling latency over several minutes catches the brief, periodic spikes that short tests never see.
- What is a 'spike' on the chart?
- A spike is a sample that is well above your typical latency — here we flag anything more than double your running average. A handful of small spikes is normal; frequent or large ones explain stutter, freezes and dropped calls.
- Can I use this as proof for my ISP?
- Yes. Run it during the time your connection misbehaves, note the min/avg/max and spike count, and save the result to your test history. A timed record of repeated spikes is far more convincing than 'the internet feels slow'.
- Should I keep the tab focused while it runs?
- Yes. Browsers throttle timers in background tabs, which can distort a long run. Keep this tab in the foreground for the most accurate sampling.
Caught the spikes? Now find the cause
A spiky chart proves something is wrong. The Doctor combines this with ping, jitter, loss and latency under load to name the culprit — Wi-Fi, router or ISP — and tells you exactly what to do next.