About the Connection Stability Test
The connection stability test sends repeated HTTPS requests from this browser and summarizes completed requests, failures, latency, and jitter. It can reveal intermittent behavior that a single speed or latency measurement may miss.
How to use this tool
Start the test while using the connection you want to evaluate. Leave this tab open until every sample finishes and avoid switching networks during the run. If you are troubleshooting an intermittent problem, repeat the test near and far from the Wi-Fi access point, with and without a VPN, or at different times of day. Those controlled comparisons are more informative than one isolated percentage.
How to read the result
The failed-request percentage is the share of browser samples that did not complete successfully. Jitter describes variation between successful round-trip times, while minimum, average, and maximum latency show the observed range. Zero failed requests with a narrow latency range suggests a stable path during the sample window. A few failures or large timing spikes may warrant a longer test with dedicated network software before drawing a conclusion.
Limits and privacy
Browsers cannot observe IP-layer packet loss directly, so this tool reports failed HTTPS requests rather than raw packet loss from ICMP or UDP probes. Application errors, browser scheduling, server availability, and connection setup can influence the result. It is a short on-demand diagnostic, not continuous monitoring and not proof of an ISP fault. Requests are sent only to buffer.lol for the duration of the test.
Common questions
- Does a failed request always mean a dropped network packet?
- No. A timeout or HTTP failure can occur above the packet layer. The result is best described as browser-request loss or instability.
- Why should I run the test more than once?
- Interference and congestion change over time. Repeated tests help distinguish a recurring pattern from a brief spike.