If upload reads zero while download works, the cause is almost always one of five things: a modem that has lost its upstream channels, a damaged Ethernet cable or port that has negotiated down to a half-working link, a VPN or security tool blocking outbound traffic, a router whose buffers are saturated by a background upload (bufferbloat), or an ISP upstream fault. Slow-but-nonzero upload is usually simpler: cable and DSL plans sell asymmetric speeds, so a “1 Gig” plan may carry only 20 to 35 Mbps upstream. Fix order: power-cycle modem and router, test wired, disable VPN, check the modem’s upstream status page, then call the ISP with that data. Each step is below.
How do I tell “no upload” from “slow upload”?
Run two tests, one on Wi-Fi and one with a laptop plugged directly into the modem (not the router). Use Speedtest and Cloudflare’s speed test, because they use different servers and a disagreement between them points at the test server rather than your line.
Three outcomes, three diagnoses:
- Upload is 0 or the test stalls on the direct connection: modem, cable, or ISP upstream fault. Skip to the modem section.
- Upload is fine wired, bad on Wi-Fi: your router or radio environment. Upload is more sensitive to weak signal than download because the client device transmits with far less power than the access point.
- Upload matches your plan but feels useless: you bought an asymmetric plan. The FCC raised its broadband benchmark to 100 Mbps down and 20 Mbps up in March 2024, and 20 Mbps up is still the floor many cable plans sit at.
Why would upload drop to zero while download still works?
Modem upstream channels. Cable modems (DOCSIS 3.0 and 3.1) bond several upstream channels. Noise on the coax, a corroded fitting, or a bad splitter can knock every upstream channel offline while downstream keeps working, because the two directions use different frequency bands. Open your modem’s status page (commonly 192.168.100.1) and look at the upstream table. Zero bonded upstream channels, or power levels above roughly 51 dBmV, means a line problem the ISP has to fix.
Ethernet negotiated down. Gigabit Ethernet uses all four wire pairs. If one pair is damaged, the link falls back to 100 Mbps, and if the fallback is imperfect you get duplex mismatches that collapse upload to near zero while download limps along. Check the link speed in your OS network settings. If it reads 100 Mbps on a cable that should do 1 Gbps, replace the cable.
VPN or security software. Corporate VPNs often route all traffic through a tunnel with a strict upload cap, and some endpoint-protection suites inspect outbound files and stall large transfers. Disconnect the VPN, pause the security client for one test, and compare.
Bufferbloat. A single device saturating upstream (a cloud backup, an iCloud Photos sync, a Windows update sharing itself to other PCs) fills the router’s transmit buffer. Latency climbs past one second, and every other upload appears dead. The Waveform bufferbloat test measures this directly. A grade of C or worse means the fix is active queue management, described next.
What is the fastest fix for slow uploads at home?
Enable Smart Queue Management (SQM) on your router. It implements fq_codel or CAKE, algorithms standardised in RFC 8290, which keep latency low even when the uplink is full. Set the upload limit to about 90 percent of your measured upstream speed. Most consumer routers from Netgear, TP-Link, and ASUS now expose this under “QoS” or “Adaptive QoS.” OpenWrt, pfSense, and Ubiquiti gear expose it by name.
Then stop silent background uploads. On Windows, Delivery Optimization uploads update files to other PCs on the internet unless you restrict it to the local network. On macOS and iOS, iCloud Photos and iCloud Drive will upload a camera roll at full speed with no throttle setting. Dropbox, Google Drive, OneDrive, and Backblaze all have bandwidth limits in their preferences, and they default to unlimited.
Finally, move the uploading device to Ethernet. Wi-Fi 6E and Wi-Fi 7 routers help in the 6 GHz band, but a phone or laptop still transmits at a fraction of the router’s power. Through two walls, a laptop that downloads at 400 Mbps will often upload at 30.
How much upload speed do I actually need?
| Task | Realistic upstream need |
|---|---|
| Video call, 1080p (Zoom’s published requirement) | 3 to 4 Mbps per participant |
| Livestream at 1080p60 (YouTube recommended bitrate) | 4.5 to 9 Mbps, plus 50 percent headroom |
| Upload a 1 GB phone video | About 7 minutes at 20 Mbps, 1.5 minutes at 100 Mbps |
| Deliver a 10-minute 4K ProRes 422 HQ master (about 53 GB) | About 6 hours at 20 Mbps, 1.2 hours at 100 Mbps, 8 to 10 minutes on symmetric gigabit fiber |
The ProRes figure comes from Apple’s published data rate of roughly 707 Mbps for UHD 422 HQ at 23.98 fps (ProRes white paper). That number is why upload speed matters more to a production company than download.
What does this look like in a working video studio?
We deliver masters and review cuts daily, and upload is the bottleneck on every project. On a cable connection advertised as 1,200 Mbps down, the upstream was 35 Mbps. A single client’s 53 GB master took most of a working day and failed twice when a colleague’s Time Machine backup to the office NAS kicked in and tripped bufferbloat. Moving to symmetric fiber at 1 Gbps cut that same delivery to under fifteen minutes and cost roughly the same monthly fee. If fiber is available at your address, it is the only fix in this article that changes the ceiling rather than the plumbing.
Where fiber is not available, we schedule master uploads overnight with the cloud client’s bandwidth limit lifted, and we send review cuts as 10 to 15 Mbps H.264 or H.265 instead of ProRes. A 10-minute review cut at 12 Mbps is under 1 GB and uploads in minutes on any plan. Frame.io, Vimeo, and Dropbox all transcode on their side, so the client sees no quality difference in a browser review.
One trap we hit repeatedly: cellular hotspots. A 5G phone can show 300 Mbps down and under 10 Mbps up, and carriers deprioritise hotspot traffic under congestion. Hotspot uploads of anything over a few gigabytes should be treated as unreliable.
When is it the ISP, and what do I say to them?
It is the ISP when a direct modem connection shows zero or near-zero upload, the modem’s upstream table shows missing channels or out-of-range power, or speeds collapse at the same hours every evening. The FCC’s Measuring Broadband America program publishes how far each provider’s real speeds fall from advertised ones, which is useful leverage.
Call with three things: screenshots of wired speed tests at different times of day, the upstream power and SNR values from the modem page, and the dates the problem started. Ask specifically for a line technician to check signal levels at the tap, not a “reset from our end.” If the technician finds high upstream noise, the fix is usually a replaced drop cable, splitter, or fitting, and it is done on their side of the demarcation point at no charge.
What changed since the old advice?
Two things. First, the FCC’s 2024 benchmark made 20 Mbps up the legal definition of broadband, and several cable operators have started “mid-split” and DOCSIS 4.0 upgrades that lift upstream to 100 Mbps or more in upgraded markets. If your plan still shows 10 or 20 Mbps up, ask whether a mid-split tier is available before switching providers. Second, QoS advice used to mean prioritising one device over another. Modern SQM with fq_codel or CAKE solves the upload stall for every device at once and is now built into most routers sold since 2022.
Start with a wired test at the modem. If upload is zero there, read the modem’s upstream table and call the ISP with the numbers. If upload is fine there, turn on SQM, cap your cloud clients, and put the uploading machine on Ethernet. If the ceiling itself is the problem, check for fiber or a mid-split cable tier at your address, because no router setting will add bandwidth your plan does not include.
