About this connection check.
You ran a speed test. The number looked good. Your call still froze. This site helps you work out what to check next and make sense of the readings.
I'm Jerrod Vick, a software architect with more than 20 years of experience. Before that, I worked in technical support at Dell and Creative Labs. My family still calls when the technology stops cooperating. I maintain this site independently, without endorsement from former employers. The connection check uses Cloudflare's measurement infrastructure. For Cloudflare support, you'll need to contact Cloudflare itself.
A frozen call needs different checks from a slow download. I want you to have something useful to try before installing software or running a test. The guides start with the app that's giving you trouble and explain how download speed and response time affect it. The browser check adds readings from your connection to Cloudflare, though it can't pinpoint a faulty piece of equipment.
What the check can tell you
We start by checking how quickly small requests get an answer and how much that timing changes. Lower response times mean less waiting. Lower variation means steadier responses. Full check estimates download and upload speed while watching how response time changes. If requests take much longer during transfers, that can help explain lag during a backup or download. It then sends small WebRTC probes through a relay to check delivery. Lower data skips upload and packet loss.
Capacity and activity labels describe general headroom, not guarantees for every app or household. Response and variation grades describe this path to Cloudflare. Busy-response grades use added median delay over idle, with no increase shown as zero. Busy jitter is not graded. Missing readings limit what the result can tell you. The check measures your path to Cloudflare, not a particular app, website, game server, or network hop. Transfer values are estimates. Packet loss is unavailable without a supported relay. The results cannot pinpoint a faulty router or ISP.
Full check sends 500 small probes through a WebRTC TURN relay. One missing probe is 0.2%. None observed means none went missing in that short check, not guaranteed zero loss. A failed relay connection is unavailable. Shared links contain percentages, not probe counts.
Keep this tab visible. Backgrounded readings are provisional. Interrupted checks cannot support a complete verdict. Test traffic may disrupt calls or games. Save a baseline link, change one condition, then repeat the same profile on the same device. Comparisons remain in page memory and disappear on reload. Guide examples use invented readings to explain comparisons. They are not customer results, performance promises, or evidence that a particular device or provider is faulty.
How measurements and ratings work · What's changed
Measurements use the Cloudflare Speed Test library. For practical next steps, start with your symptom or read the home-office Wi-Fi investigation.
Check my connectionReport an error or suggest an improvement · Data use and privacy