This guide helps you validate whether Teams call lag is caused by upload speed, Wi‑Fi instability, router load, device performance or a wider service issue.
Video call troubleshooting guide
Teams needs stable upload, low jitter and clean packet delivery. Use this guide to validate whether the problem is Wi‑Fi, upload saturation, router queueing, the device or the service route.
Issue
Use these signs to confirm that Microsoft Teams call quality is the closest matching issue before changing routers, providers or devices.
Likely causes
Teams call problems are usually caused by upload pressure, Wi‑Fi instability, device load, router queueing or a wider route/service issue. Validate the exact pattern before changing broadband package.
Video calls send data as well as receive it. Cloud backups, photo sync, CCTV uploads, game updates and file transfers can fill the upstream path and leave Teams with too little headroom.
Even a fast download package can have a much smaller upload allowance, so the upload side often fails first during calls and screen sharing.
Weak wireless signal, interference, long distance from the router, poor mesh backhaul or crowded channels can make latency vary from moment to moment.
Teams may react by dropping video quality, freezing frames or briefly losing audio even if the headline speed test looks acceptable.
Some routers use large unmanaged queues. When the home connection is busy, Teams packets wait behind downloads or uploads and the call feels delayed or broken.
This is why a loaded-latency or bufferbloat test matters more than download speed alone for live calls.
Older laptops, browser-based Teams sessions, VPN clients, antivirus inspection and limited CPU/RAM can overload the device during video, screen share or background updates.
If only one device has the issue while another works in the same room, the bottleneck is probably local to that device.
Business VPNs, privacy relays and provider routing can add delay or packet loss between your home and Teams servers.
If Ethernet, Wi‑Fi and device checks all look healthy but Teams still fails, compare another call service and check provider or Microsoft service status.
Validate
Work through these checks in order. Keep the test device, room and connection method consistent so the results identify the real fault layer.
Record download, upload, ping and jitter. If upload is low or jitter spikes while the call is active, the issue is more likely connection responsiveness than Teams itself.
If Teams becomes stable over Ethernet, fix Wi‑Fi coverage, router placement, mesh backhaul or wireless interference before contacting the provider.
Stop OneDrive, iCloud, Google Photos, console updates, CCTV uploads and large file transfers. If the call improves immediately, household traffic was saturating the line or router queue.
If a second laptop or phone works properly on the same Wi‑Fi, the original device may have a Teams app, browser, VPN, security tool or CPU/RAM issue.
If ping rises sharply during the upload phase, the router or upstream link is queuing traffic badly and Teams will suffer whenever the connection is busy.
Use mobile data to check provider and Microsoft service status. If several real-time apps fail across Ethernet and Wi‑Fi, gather timestamps and test results before escalating.
Fix
Apply the fix that matches the cause you validated. Teams call quality usually improves fastest by protecting upload headroom and reducing jitter.
Pause or schedule cloud backups, photo sync, large file uploads and console updates outside meeting times.
If the household often runs video calls, choose a package with enough upload speed for simultaneous calls and backups.
Use Ethernet for important calls where possible. If Wi‑Fi is required, move closer to the router, reposition mesh nodes, avoid hidden TV cabinets and test again in the same room.
A better router position or wired access point can be more effective than switching provider when Ethernet already works.
Use router QoS or Smart Queue Management where supported, and avoid letting any single device consume the full upload path.
If loaded latency is the proven problem, move to the bufferbloat fix guide rather than focusing only on speed.
Update Teams, try the desktop app instead of a browser or vice versa, close heavy background apps and temporarily disable VPN/security inspection for testing.
If CPU or memory usage spikes during calls, the device may be the bottleneck rather than the broadband line.