Connection Stability Test

Watches a live WebSocket to the desktest edge for about 45 seconds to catch a flaky link that a one-shot check misses. A single open-and-echo can look perfect while the real fault - brief Wi-Fi drops, silent reconnects, or round-trip spikes - only shows up over time. That transport flakiness is what breaks long-running sessions: SignalR (FIS WebScan, Topaz), Microsoft Teams, and remote desktop over the web. This is a stability check, not a speedtest.

Read the Connection Stability Test guide for help reading the verdict.

Keep this tab in the foreground for the whole run. Background tabs get their timers throttled by the browser, which delays the pings and would show up as false drops. Do not switch tabs, minimise the window, or lock the screen until the 45-second run finishes.

Privacy: This opens a single WebSocket to edge.desktest.net and sends only a small sequenced ping token, which the edge echoes back. No credentials, no business data, no telemetry to us, no analytics, no tracking. View source to verify the endpoint and the ping payload.

Configuration

Driver: Browser WebSocket API

Runs for about 45 seconds. Sends one ping every 1.5s over a single WebSocket to the desktest edge; only the ping token is sent, no business data.

Status Check Step

Pending

WebSocket connection opens

Opens wss://edge.desktest.net and confirms the upgrade completes.

1 of 3

Pending

Sustained stability monitor

Sends a sequenced ping every 1.5s for about 45s, tracking round-trip time, missed pings, and reconnects live.

2 of 3

Pending

Stability assessment

Tallies loss, reconnects, and round-trip spikes into a stable / occasional blips / dropping verdict.

3 of 3