How to capture dropouts during a long video meeting

Your meeting freezes for a few seconds, voices break up, or the call disconnects, but everything seems fine again when you check afterward. To find a pattern, note when the problem happens and compare those times with a connection test.

The Connection Stability test measures response time, jitter, lost requests and dropouts over a few minutes. It cannot record the meeting itself or monitor a whole workday, but you can run it around a problem and keep a simple log of what happened.

Capture a dropout while it happens

1. Open the Connection Stability test shortly before the meeting. Run it for its full test window to get a baseline, and note the time and whether you are using Wi-Fi or Ethernet.
2. Keep the meeting open. If the call starts freezing or breaking up, write down the time to the nearest minute and what you noticed, such as frozen video, garbled speech or a reconnect message.
3. If the test is still running, note its response time, jitter and any lost requests or dropouts around the same time. If its test window has ended, run it again when the problem returns. It only checks the connection for a few minutes at a time.
4. Check the meeting app's call statistics, if it has them. Note any reported packet loss, latency or network warnings, along with the time. Do not assume that the meeting app and the browser test use the same server or route.
5. After the call, run another test and add the result to your notes. Include the device, connection type and whether other people were streaming, downloading or uploading at the time.

A short log is often more useful than a long recording. You can note, for example, that the call froze at 10:42 a.m., the browser test reported lost requests at about the same time, and a large upload was running. Avoid recording the meeting just to document a connection issue, especially if it includes private conversations.

What the result means

Lost requests or dropouts appear during the call problem

The browser test could not get a timely response to some requests while you were checking. If this happens at the same time as the meeting trouble, it supports the idea that the connection was interrupted, but it does not prove whether the cause was Wi-Fi, your router, your internet provider or a route beyond your home.

Jitter rises when voices break up

Jitter means that response times vary rather than staying steady. Uneven timing can make live audio or video harder to deliver smoothly, even when a speed test shows a high download rate. Compare several incidents instead of treating one brief spike as a diagnosis.

Response time rises but requests are not lost

The connection is responding more slowly, but the test did not detect a complete request failure during that window. A call can still feel delayed, and the test may not follow the same route as the meeting service. Compare its readings with the meeting app's own call statistics if available.

The test looks steady during a bad call

This does not rule out a network problem. The issue could affect only the meeting service, happen outside the few minutes you tested, or come from the computer, camera or meeting app. Check the call's statistics and repeat the test if the symptom returns.

How to reduce interruptions

1. Pause heavy transfers. Stop large downloads, cloud backups and uploads on your computer and other devices, then see whether the call improves. A connection can become slow to respond when another activity is using most of its capacity.
2. Move closer to the router. If you are on Wi-Fi, move to the same room as the router or use Ethernet if possible. On Windows 11, check the connection under Settings › Network & internet. On macOS, open System Settings › Wi-Fi. On a phone, open Settings › Wi-Fi; Android menu names can vary by device.
3. Compare another device. Join a test call or run the stability test on another device using the same connection. If only one computer has trouble, focus on its Wi-Fi adapter, browser, meeting app or background activity. If multiple devices struggle at once, look at the router or internet connection.
4. Reconnect to the network. Turn Wi-Fi off and back on, then reconnect. If you use Ethernet, check both ends of the cable and try another router port. Avoid changing several network settings at once, so you can tell which change helped.
5. Restart the router if problems continue. Follow the router maker's normal restart procedure, then repeat the test and note whether the pattern changes. A restart can clear a temporary fault, but recurring interruptions may need further investigation.
6. Check VPN or security software. If your work allows it, compare a call with and without the VPN, changing only that one condition. Do not turn off required workplace security controls without permission.

When to check the router or provider

If several devices lose requests at the same time, including one connected by Ethernet, the cause is less likely to be a single computer's Wi-Fi. Repeat the test at different times and keep the timestamps, connection type and readings. Contact your internet provider if interruptions occur across devices and continue after a router restart. If the problem happens only on one computer, check its adapter or ask a repair technician to inspect it.

Why a steady browser test cannot guarantee a steady call

The stability test sends its own browser requests to measure response time, jitter and lost requests. A meeting sends live audio and video to its service, which may use different servers and network paths. The test is useful evidence, not a pass or fail verdict on the meeting. For more ways to document recurring interruptions, see Brief connection dropouts during remote work.