Output
HTTP timing or host transfer throughput
UserBenchmark / All Tools / Internet Stability Test
Network
Internet Stability Test
Sample this website repeatedly for latency spikes and failed requests.
Free to useNo downloadNo sign-up
Internet Stability Test · At a glance
Quick answer: Sample this website repeatedly for latency spikes and failed requests. HTTP failures are application-level request failures.
Internet Stability Test
The test loads when you open it. Device access is requested only after you choose to start.
Detailed guide
How to use this tool
- Sample this website repeatedly while observing latency spikes and failed requests.
- Keep notes about Wi-Fi or other traffic changes.
Input
Requests only to this website
Browser requirement
PHP endpoint; HTTPS hosting
Processing
Requests to this website; hosting can affect the result
How it works and what the result means
Latency is an HTTP round trip including TLS, server processing and browser overhead. Throughput is to this host and may be constrained by hosting, compression, caching or buffers.
Reading the result
HTTP failures are application-level request failures. They are not a measured percentage of lost UDP or IP packets.
What to check next
If failures occur, compare another destination and check the local connection. Server processing can also cause delays.
This is not ICMP ping, UDP packet-loss measurement or a test of every internet route. The PHP endpoint must be enabled on the host. Timeouts are request failures, not measured network packet loss.
Frequently asked questions
Does a failed request mean one network packet was lost?
No. A request can involve many packets and fail for server, protocol or timeout reasons. The page does not inspect packet-level loss.
How do I start the Internet Stability Test?
Start a short test to this website. Keep other downloads quiet when measuring baseline latency or throughput.
Does this tool require a download or an account?
No. Open the interactive tool above in a modern browser. The instructions and explanations are available even with JavaScript disabled; running a test needs JavaScript.
Why can two attempts give different results?
Power settings, background tasks, browser scheduling, operating-system input processing and device settings affect measurements. Compare repeated attempts with identical settings rather than the single highest score.