Connection stability tester
Is your connection steady?
The test asks BenchDevice's server for a tiny file four times a second and times each answer. You see how long round trips take, how much they vary and how many get lost.
- Round trip now: —
- Lost so far: —
- Time left: 1:00
Stability results
—
- Requests sent
- —
- Answered
- —
- Lost
- —
- Longest drop
- —
- Fastest
- —
- Typical (median)
- —
- Slow (95th percentile)
- —
- Slowest
- —
- Jitter
- —
How this test works
The page asks BenchDevice's server for a one-byte file four times a second, each request with a fresh address so nothing answers from a cache, and times every answer. An answer that takes longer than two seconds counts as lost. You choose the length: one, five or fifteen minutes. If you hide the tab the test pauses and says so, then goes on when you come back.
How to read the result
Each bar in the chart is one round trip, newest on the right, and red marks are lost requests. The results give the fastest, typical (median), slow (95th percentile) and slowest round trip; the jitter, which is how much one round trip differed from the next on average; and the longest drop, the longest run of lost requests in seconds. The test shows numbers only and does not judge them.
Common faults
A flat trace with a few tall spikes usually points to Wi-Fi: a weak signal, a crowded channel or something else on the air. Lost requests in long runs point to a link that goes away for a moment, such as a radio that re-joins its network or a modem that re-syncs its line. Round trips that climb and stay high while another device downloads are bufferbloat, which the bufferbloat tester measures directly. To tell Wi-Fi from the line, run the test once on Wi-Fi and once on a cable to the router.
What a browser can't see
A browser can't read your Wi-Fi signal strength, channel or band, or tell which part of the path adds a delay: your Wi-Fi, your router or your provider. Run the test once on Wi-Fi and once on a cable to tell them apart.