Broadband is advertised on one number. A plan is “300 Mbps”, and the upload figure sits in the footnote or nowhere at all. For a household that only watches things, that is a reasonable simplification. For anyone who joins video calls, backs up to the cloud, works over a VPN or uploads anything larger than a photograph, the second number is the one that determines how the connection feels.
Symmetric, asymmetric, and where the split came from
An asymmetric connection provides more downstream capacity than upstream — 300 down and 30 up, say, or 100 and 10. A symmetric connection provides the same in both directions: 300/300, 1000/1000.
The asymmetry is a historical artefact of copper. DSL and cable both divide a fixed slice of radio spectrum on a wire between the two directions, and in the 1990s the obvious allocation was to give almost all of it to downloads, because consumers consumed. The “A” in ADSL stands for asymmetric; it was a design decision, and a sensible one at the time.
Optical fibre has no equivalent constraint. Downstream and upstream ride on separate wavelengths, and modern PON systems can be provisioned symmetrically — XGS-PON is symmetric at roughly 10 Gbps by design. When a fibre plan is sold as 300/30, the 30 is a commercial provisioning choice, not a property of the glass. Understanding that changes the conversation you have with a provider.
What actually consumes upstream
Downstream demand is easy to picture. Upstream demand is less visible, which is why people underestimate it. In a typical connected household or small office, upstream is consumed by:
- Video calls. Every participant sends a stream. A single HD video call typically needs on the order of 1.5–3 Mbps upstream, and group calls and screen sharing push it higher. Two people on calls in the same house is not an unusual Tuesday.
- Cloud backup and file sync. Photo libraries, document sync and endpoint backup are pure upstream, and they run continuously in the background.
- Remote work. VPN sessions, remote desktop, pushing code, uploading builds and design files.
- CCTV with offsite recording. Continuous, 24 hours a day, and it scales with the number of cameras.
- Creators and live streaming. Delivering video to a streaming platform, or uploading finished footage. This is where upload becomes the entire product.
The counterintuitive part: a saturated upload slows your downloads
This is the mechanism most people have never had explained, and it is the reason a “fast” connection can feel broken while nothing is downloading.
TCP — the protocol underneath almost everything — is a conversation. As data arrives, your device sends small acknowledgement packets back to the sender confirming receipt. The sender uses those acknowledgements to pace itself. They are tiny, but they must get through promptly.
Now saturate the upstream with a backup job. Those acknowledgements queue behind megabytes of backup traffic in the router’s upstream buffer. They arrive late. The remote server, seeing delayed acknowledgements, concludes the path is congested and slows down. Your download collapses because your upload is full. The same queueing spikes round-trip latency, which is what makes the video call in the next room fall apart at the exact moment somebody hit “sync”.
Modern queue management — the family of algorithms usually discussed under the heading of “bufferbloat” — mitigates this considerably by keeping buffers short and prioritising small packets. Good routers implement it. But mitigation is not capacity: the reliable fix is to have enough upstream that ordinary use does not saturate it.
Doing the arithmetic for your own household
Add up the concurrent upstream you actually need, then leave headroom. A worked example for a two-person work-from-home household:
- Two HD video calls: roughly 4–6 Mbps
- Continuous photo and document sync: 5–10 Mbps when active
- One CCTV camera to cloud: 2–4 Mbps
- Someone pushing a large file: whatever is left
That is already 15–20 Mbps of steady demand before anyone does anything unusual — which is to say, a 30 Mbps upstream is not comfortable, it is marginal. Headroom is what stops the last item on that list from wrecking the first three.
Who genuinely does not need symmetry
It would be dishonest to claim everybody does. A household that streams video, browses, games and makes occasional calls will be perfectly served by an asymmetric plan with a decent upstream. Gaming in particular is a low-bandwidth, latency-sensitive workload — what matters there is consistent latency and low jitter, not raw upload capacity.
Symmetry earns its price when upstream is sustained and concurrent: several people working from home, a small office, a creator workflow, offsite backup of anything substantial, or a business running services others connect into. At that point the calculus shifts toward dedicated, contracted capacity as well.
What to ask
- What is the upload speed, as a number, in writing?
- Is it symmetric, or a fixed fraction of download? Does it change if I upgrade the download tier?
- Is upstream subject to different fair-usage or shaping rules than downstream?
- Does the supplied router implement modern queue management, or can I use my own?
ValoNet publishes symmetric residential plans — the upload figure equals the download figure rather than being a tenth of it — which removes the arithmetic above as a thing you have to worry about. The broader point stands regardless of provider: if the upload number is hard to find on a plan page, find it before you sign.