Microsoft Teams Call Health: Diagnose Upload Speed Before Upgrading

In short, test before you buy. Most remote workers can find the cause of a bad call using the Teams Call health panel, a wired Ethernet cable and Windows Resource Monitor. Only after those checks does it make sense to call an ISP about a bigger upload tier. One disclosure is relevant here: CNET states the piece was made possible in part by T-Mobile, a 5G home-internet provider, and says it was written and edited independently without partner oversight.

Upload Speed Is What Carries Your Teams Video Out of the House​

Internet plans are sold on download speed, which is how fast your devices receive data such as web pages, inbox refreshes and streaming video. Upload speed runs the other way. It is how fast your devices send data, and a video call does this continuously for as long as your camera is on. Sending an email, syncing a file to Google Drive, Dropbox or OneDrive, sharing your screen and keeping a virtual desktop session open all use upstream bandwidth as well.

The problem is asymmetry. CNET gives the example of a cable customer with 500 Mbps or even 1,000 Mbps of download speed and only 35 Mbps of upload. The publication says most cable plans can't deliver upload speeds higher than 35 Mbps, because cable is usually built to favour downloads. 5G home internet is also asymmetric: CNET puts typical 5G upload speeds at 10 to 50 Mbps, compared with downloads of 90 to 500 Mbps, and says latency is higher than on cable or fiber.

Cable adds a second limit. Neighborhood nodes share a pool of bandwidth, so speeds can fall in the evening when more neighbors are online. Fiber-to-the-home is usually symmetrical, with uploads as fast as downloads, and doesn't share a neighborhood node in the same way. That makes it the strongest option for remote work where it's available. CNET reports that cable operators including Xfinity, Spectrum and Optimum are upgrading nodes to DOCSIS 4.0 hardware. Spectrum told the publication it plans to finish network upgrades by 2027 and offer symmetrical multigig speeds across its footprint. That is a provider's own timeline, not a delivered service.

Microsoft Teams Needs Only a Few Megabits, but Households Share the Pipe​

The per-app figures are modest. CNET's comparison table lists Teams at 0.2 Mbps minimum and 1.5 Mbps recommended for 1080p video, Zoom at 0.6 and 3.8 Mbps, and Google Meet at 1 and 3.6 Mbps. Microsoft's planning guidance for Teams gives more detail and shows that the right number depends on the type of call:

The 1.5 Mbps figure that CNET uses for Teams matches Microsoft's recommendation for one-to-one video. For group meetings, Microsoft recommends 2.5 Mbps up. Microsoft also says these figures are per endpoint, so a user who joins the same meeting from a laptop and a phone counts twice. Teams adjusts to the bandwidth it finds. It goes up to 1080p and 30 fps when capacity allows, and when bandwidth runs short it protects audio quality at the expense of video.

So why would a 35 Mbps connection struggle when one Teams call needs about 2.5 Mbps? The answer is everything else sharing that connection. CNET's reasoning is that you can lose half or more of your nominal bandwidth over Wi-Fi, and speeds fluctuate during the day. A 20 Mbps upload plan might effectively deliver 8 or 9 Mbps. That's enough for one person, but it gets tight once a partner is on another call, a child is gaming and cloud backup is running.

CNET's author suggests 35 to 50 Mbps of upload as a comfortable baseline for a two-remote-worker household, and 100 Mbps or more for people who upload large files, such as video editors. These are one writer's planning ranges, not official requirements. They are still a reasonable starting point when you compare plans.

The FCC's 100/20 Mbps Benchmark Is Only the Floor for Cable, Fiber and 5G Plans​

The regulatory baseline is well established. In March 2024 the FCC raised the Commission's benchmark for high-speed fixed broadband to download speeds of 100 megabits per second and upload speeds of 20 megabits per second – a four-fold increase from the 25/3 Mbps benchmark it set in 2015. The same report also sets a 1 Gbps/500 Mbps long-term goal for broadband speeds. Among its reasons, the FCC observed that changes in consumer usage trends, particularly the rise in telework and telehealth since the onset of the COVID-19 pandemic, justified the higher bar.

Two limits apply to that benchmark. It sets the standard a service must meet to count as broadband. It doesn't guarantee what reaches your desk at 10 a.m. on a Tuesday. It also isn't settled policy: according to Broadband Breakfast, a later FCC proposal to scale back broadband standards has met pushback, with some rural and equity groups asking the agency to raise – not lower – its standards, with some pressing for a symmetrical 100 Mbps upload * 100 Mbps download benchmark.

On availability, CNET cites FCC data from the end of 2025 showing 20 Mbps upload available at 99.99% of U.S. addresses and 100 Mbps upload at about 69%. Cable plans with 100 Mbps upload reach roughly 33% of addresses, and fiber with at least 100 Mbps upload reaches 50.1%. We could not match those exact percentages to an FCC publication, so treat them as CNET's reading of the data. What matters for your decision is your own address. The Broadband Facts label that providers must show at sale lists the typical upload speed, and that figure is what you should compare, not the download headline.

Teams Call Health Shows Whether the Network Is Actually the Culprit​

CNET calls upload speed "the most common culprit by far" for dropped calls. Microsoft's documentation lists a wider set of causes. Its Teams network guidance ties slow performance to insufficient bandwidth, dropped calls to firewall or proxy blockers, and robotic or cutting-out audio to jitter or packet loss. Different symptoms call for different fixes, and a faster plan won't solve packet loss on a congested Wi-Fi channel.

Teams can show you which problem you have. During a meeting, select More actions, then Settings, then Call health. The panel refreshes every 15 seconds and splits its readings into network, audio, video and screen-sharing sections. Microsoft publishes typical values to compare against:

• Round-trip time should be under 200 ms. In group calls this measures the path to the Teams service, and in one-on-one calls it measures the path to the other participant.
• Received packet loss should be under 2%, and received audio jitter should be under 30 ms.
• The Teams send limit is typically about 70 kbps for audio and 1.5 Mbps for video.
• Video processing should show hardware encoding where possible, because software encoding puts more load on the CPU.

Read the send limit carefully. Microsoft says it is not your ISP's speed limit. It is the most Teams will send given current conditions. A very low value can mean Teams is holding back because it is competing with other traffic, which fits the upload-congestion theory. Teams also lowers its usage when content is simple or a participant has chosen lower-quality settings.

Microsoft adds that low frame rates don't necessarily mean the network is at fault. Poor video with low frame rates can come from computer performance or insufficient hardware. A laptop that is thermally throttled or encoding video in software can look much like a saturated uplink, and Call health is the fastest way to tell them apart. If your own figures look clean and the video still stutters, the problem may be on the other participant's side.

Ethernet, QoS and Resource Monitor Come Before a Plan Upgrade​

CNET's fixes are sensible when done in order, running a speed test before and after each change so you can see what helped. It suggests Ookla for general tests. Test at your actual desk, not next to the router, and at the times you usually have calls.

Plug in with Ethernet​

Try a cable first. CNET notes that Wi-Fi loses signal with distance and walls, so a router downstairs could halve the speed at an upstairs desk. Ethernet avoids wireless interference and sends and receives at the same time. A wired test also separates a Wi-Fi coverage problem from an ISP problem, which the rest of the troubleshooting depends on. If you have to stay wireless, Microsoft's guidance explains the trade-off between bands: 2.4 GHz reaches further but is crowded by other consumer devices, and 5 GHz suits real-time media better but needs closer access points.

Prioritize the work laptop with router QoS​

Quality of Service (QoS) lets a router favor certain traffic. CNET points out that implementations differ. Netgear Nighthawk routers can prioritize applications such as Zoom, TP-Link Deco mesh systems can reserve a percentage of bandwidth for a specific device, and some routers have no QoS controls at all. On managed corporate networks, Microsoft recommends QoS on every network segment, plus QoS or WiFi Multimedia (WMM) on wireless, so voice traffic stays protected during unexpected congestion.

Find the uploaders with Windows Resource Monitor​

Other devices on the network can use up upstream capacity without you noticing. Your router's admin page or companion app usually shows per-device traffic in real time. On the Windows machine itself, search for Resource Monitor, open the Network tab and sort processes by the Send (B/sec) column to see which apps are uploading and how fast. Mac users can do the same with Activity Monitor's Network tab and the Sent Bytes column. This only shows traffic from that one PC, so a backup running on another computer won't appear. CNET also advises contacting your company's IT department before you investigate or change anything on a work-managed device, and that applies even more to disabling sync or security agents.

Test for bufferbloat before blaming the router​

Bufferbloat is lag caused by too much data queuing up at once. The Waveform Bufferbloat test measures idle latency, then fills the connection with upload and download traffic and records how far latency rises. A large increase suggests the router struggles under load. CNET suggests that a router more than about five years old, especially a Wi-Fi 5 model, may be worth replacing with Wi-Fi 6 or Wi-Fi 7 hardware. A mesh system with an Ethernet cable run from a satellite node in your office can help in a large home. Neither will add upload capacity beyond what your ISP provides.

A note for corporate VPN users​

The guide doesn't cover this, but it is often behind poor Teams quality at home. Microsoft recommends split-tunnel VPN, so Teams traffic goes directly to Microsoft 365 instead of through the corporate tunnel. Microsoft gives these reasons: VPNs usually aren't designed for real-time media, some don't support the UDP that Teams needs, they add a second layer of encryption to media that is already encrypted, and they can route traffic to a more distant service entry point, which adds latency and jitter. Administrators can check this alongside the Call Quality Dashboard and the Teams admin center, which Microsoft provides for looking at call problems across an organization and for individual users.

What this means for you​

Diagnose before you spend. A faster upload tier helps if Teams Call health shows a low send limit while other traffic is competing, and a wired test confirms the ISP connection is the limit. It won't help if the problem is Wi-Fi signal, a CPU running software encoding, a corporate VPN route or the other participant's connection. Households with two people on video calls, or anyone who regularly uploads large files, have the strongest reason to look for more upstream capacity, and fiber is the clearest way to get it where available.

• Open More actions, then Settings, then Call health in your next Teams meeting, and check round-trip time under 200 ms, packet loss under 2% and hardware video processing.
• Run speed tests at your desk, over Wi-Fi and then over Ethernet, and compare the upload result with the typical upload speed on your plan's Broadband Facts label.
• Plan on about 2.5 Mbps of upload per person in a Teams meeting, per Microsoft's recommendation, and leave headroom for backups, cloud sync and other people in the house.
• Sort Resource Monitor's Network tab by Send (B/sec) to find background uploaders on your PC, and check with IT first if the machine is company-managed.
• Use the Waveform Bufferbloat test before replacing a router, and remember that a mesh system extends coverage without adding ISP bandwidth.
• If you're an admin supporting remote staff, check that Teams traffic is split-tunneled around the VPN.

Upload speed is behind many work-call problems, but Teams already reports whether the fault is in your uplink, your Wi-Fi, your laptop or someone else's connection. Checking that first means you only pay for extra upload capacity if you actually need it. That decision will also get easier as DOCSIS 4.0 upgrades and fiber reach more addresses: Spectrum's own target is symmetrical service across its footprint by 2027, which would give many cable customers an alternative to today's 35 Mbps upload limit without switching providers.