How to record connection drops during a class
Track connection drops during an online class, then compare their timing with response time, jitter and lost requests to find where to troubleshoot.
Your online class freezes for a few seconds, the teacher’s voice cuts out, or you get disconnected and rejoin. These brief interruptions can be hard to explain afterward, especially if everything seems normal when you check it later.
Use the Connection Stability test while the problem is happening. It measures response time, jitter, lost requests and dropouts over a few minutes. Keep a simple time-stamped note alongside the results so you can compare the interruptions with what happened in class.
Track connection drops during class
- Open Connection Stability on the same device and network you use for class. Start the test shortly before class or as soon as you notice a problem.
- Keep the test page open for several minutes. If the class is already running, leave the call open too. Avoid starting a download or speed test at the same time, since extra network activity can change the connection you are trying to observe.
- When the class audio or video stutters, note the time and what you noticed: for example, “10:18, audio stopped for about three seconds” or “10:26, call reconnected.” Also note whether the Wi-Fi icon changed or the class app showed a reconnect message.
- After the test ends, compare your notes with its response time, jitter, lost requests and dropouts. Repeat the check during another class if the issue comes and goes.
A short note is often more useful than trying to remember the interruption later. Use the computer’s clock for the time, and note whether you were on Wi-Fi or a wired connection. The test measures the connection from your browser to TooLab’s server, not the class audio or video itself.
What the result means
Lost requests or dropouts appear when the class freezes
The test also saw requests fail or a break in the connection during the same period. That supports the idea that the interruption was network-related, but it does not identify whether the cause was your Wi-Fi, router, internet provider, or the path to the class service. Check the fixes below, then compare results from another location or connection.
Response time or jitter rises, but requests are not lost
Response time is how long a request takes to get a response. Jitter is how much that delay changes from one request to the next. Sharp increases can make live audio and video arrive unevenly, even when the connection does not fully drop. Compare the timing with your class notes, and check whether another device or a large upload was using the network.
The class stutters, but the test stays steady
The test may have missed a very brief interruption, or the route to the class service may be having a problem while the route to the test server is fine. The class app itself can also freeze. Run the check again during another incident, and compare with a second device on the same network. A clean result does not prove that every connection used by the class is working.
The Wi-Fi connection itself disappears
If the device shows that Wi-Fi disconnected or reconnecting at the same time, the local wireless link is a strong place to investigate. If Wi-Fi stays connected but the test records failed requests, the problem could be farther along the network. A browser test cannot read Wi-Fi signal strength in dBm, so use the results to compare connection behavior in different places, not as a signal-strength reading.
How to reduce the interruptions
- Pause heavy network activity. Stop large downloads, cloud backups, game updates and video streams on other devices for a few minutes. Ask other people on the network to pause them too, then see whether the class and test become steadier.
- Move closer to the router. Try the same class setup in the room where the router is located. If the drops stop there but return in your usual spot, distance or obstacles may be weakening the Wi-Fi connection. Keep the device away from enclosed cabinets and other sources of interference where possible.
- Reconnect to Wi-Fi. On Windows 11, open Settings › Network & internet › Wi-Fi and check that Wi-Fi is on and connected to the intended network. On macOS, open System Settings › Wi-Fi and check the connected network. If you disconnect and reconnect, do it between class sessions when possible.
- Try a wired connection or another network. If your computer has an Ethernet port, test with a cable connected to the router. You can also compare using a phone hotspot, but watch mobile data use. If the class works reliably on one connection and not another, that comparison helps narrow down the source.
- Restart the router after class. A restart can clear a temporary router problem, but it will disconnect everyone using it. If drops return soon afterward, contact your internet provider or whoever manages the network and share the times you recorded.
Why the test and class can disagree
A live class and a browser stability test do not necessarily use the same servers or network routes. The test sends requests to measure connection behavior. It does not record the class stream, and its results cannot show exactly what the conferencing app received. A test that runs for a few minutes can also miss a drop that happens only once an hour.
For a useful comparison, repeat the check from the same device and spot, and note the time of each interruption. The stability test sends requests to TooLab’s server, but it does not capture your class audio or video.
