A speed test measures how much capacity is available right now. If something else is already using half of it, the test reports what is left over, and you conclude your connection has a problem it does not have.
What is usually running without you knowing
- Game consoles. The biggest offender by volume. Consoles download updates in standby, and modern games patch in tens of gigabytes.
- Cloud storage. Photo and file sync starts the moment you add anything, and a phone joining home Wi-Fi can begin uploading hundreds of pictures.
- Operating system updates. Computers and phones fetch these silently, often at night but not exclusively.
- Streaming that never stopped. A paused video keeps buffering; a television left on a menu screen may loop a preview indefinitely.
- Security cameras. Continuous upload, which quietly consumes the scarcer upload capacity.
- Peer-to-peer software. Uploads long after your own download finished.
How much damage they do
A console pulling a 60 GB update will take everything it can get. On a 100 Mbps line that can leave a speed test reporting 30 or 40 Mbps, and it will look like a service fault, complete with a plausible story about evening congestion.
The effect on latency is worse still. A saturated connection queues traffic, so ping climbs from a healthy figure into the hundreds of milliseconds and jitter rises with it. That is why calls stutter during a big download even though there is nominally plenty of speed. Our Results Guide explains latency under load, and MyRealSpeed measures it deliberately during the transfer phases.
Finding the culprit
- Check the router first. Most admin pages list connected devices, sometimes with current traffic. The device at the top is your answer.
- Check consoles individually. Look at the downloads or notifications queue rather than assuming they are asleep.
- Check phones on Wi-Fi. Photo backup is the usual suspect.
- Watch your own machine. Task Manager on Windows and Activity Monitor on macOS both show per-application network use.
- Test the elimination way. Turn Wi-Fi off on everything except the test device, retest, and compare.
Testing a genuinely idle connection
Pause active downloads rather than cancelling them, quit sync clients on the test machine, and give the network a few seconds to settle before pressing start. Then run our speed test. The full method is in our guide to running an accurate speed test.
Turning this into a useful diagnostic
Rather than treating background traffic purely as a nuisance, use it. Test once with the connection idle and once with a large download deliberately running. If speed drops roughly in proportion, that is normal sharing. If latency explodes. Idle ping of 20 ms becoming 400 ms. Your router is queueing badly, and a router with smart queue management would transform how the connection feels. That points at a router problem rather than a broadband one.
Frequently asked questions
Can I schedule updates for the night?
Usually yes. Consoles, phones, and computers all have settings for update timing, and many routers can prioritise or limit particular devices.
Does a paused download still use bandwidth?
A properly paused one does not, but some clients keep verifying or seeding. Watch the actual traffic rather than trusting the button.
Why is my upload the thing that suffers?
Because upload capacity is much smaller on most plans, so a backup saturates it easily, and once upload is full, downloads slow too, since acknowledgements cannot get back out. See download vs. upload speed.
