GEARCHECK LABWatch for intermittent response delays that a short speed test can miss. This monitor sends small HTTP probes to the GearCheck Lab server only after you start a run.
No probes sent yet.
Median latency is the middle successful HTTP response time. Maximum latency is the slowest successful response. Variation is the median absolute difference between consecutive successful samples, not a universal jitter standard. Failed probes are counted separately from latency and are never converted into zero milliseconds. A slow request can reduce how many probes fit into the chosen duration. Download the JSON sample to compare runs without relying on a screenshot.
HTTP response times include the browser, server, network path and intermediaries. They are not ICMP ping or raw packet loss, and an unavailable test endpoint can look like a connection failure. Do not conclude that the router or ISP is at fault from one run. Compare a wired connection, another browser and a different time of day. Leaving the tab stops the run and retains the partial sample. No background monitoring continues after you stop.
No. A failed HTTP request may reflect a timeout, server failure, connection problem or browser blocker. The browser cannot turn it into a certified packet-loss reading.
Diagnostic data is processed locally in this tab and is not intentionally sent to analytics. Network tools send only their test probes and temporary payloads to GearCheck Lab’s speed-test server. Media and device access starts only after your explicit action and any required browser permission. Downloaded results stay on your device.
Read the privacy policy and testing methodology. If something fails, report the tool URL and visible message.