To reduce high latency, first measure it with ping and traceroute to find where delay accumulates. Then fix the specific cause: switch Wi-Fi to Ethernet, remove bufferbloat with SQM/QoS on your router, disable background traffic, update firmware, or escalate a bad ISP hop. Guessing wastes hours; measuring narrows the fix in minutes.
Symptoms
- Voice and video calls stutter, freeze, or lag behind the speaker by a noticeable delay
- Ping to 8.8.8.8 or 1.1.1.1 shows spikes above 100 ms during normal browsing
- Online games display rubber-banding, hit registration issues, or 'high ping' warnings
- Remote desktop, SSH, or cloud IDE feels sluggish even though download speed tests look fine
- Web pages hang on 'Waiting for...' before loading, especially the first request to a domain
Common Causes
Bufferbloat on the home router
Cheap routers over-buffer packets when the link saturates. Downloads or backups fill the queue and idle traffic waits behind it, pushing ping from 20 ms to 300+ ms.
Wi-Fi interference or weak signal
Overlapping 2.4 GHz channels, thick walls, or distance force retransmissions. Each retry adds milliseconds and jitter, especially in apartment buildings with dense Wi-Fi neighbourhoods.
Congested ISP or peering hop
A slow hop inside your provider's network or at a peering point delays every packet you send. Traceroute usually shows the offending hop with consistently high RTT.
Bad routing to distant servers
Geographic distance and inefficient paths add unavoidable propagation delay. A game server in Singapore will never feel local from Berlin, no matter what you tweak.
Aging hardware or outdated firmware
Old routers with weak CPUs choke on modern traffic. Missing firmware updates can leave known driver bugs, memory leaks, and inefficient packet handling in place.
Step-by-Step Fix
- Measure baseline latency with ping and traceroute
Run ping -n 100 1.1.1.1 on Windows or ping -c 100 1.1.1.1 on macOS/Linux. Note average, max, and packet loss. Then run tracert (Windows) or mtr (Linux/macOS via Homebrew) to your target server. Consistent delay at hop one means your LAN; a jump at hop three or four points to the ISP. - Rule out Wi-Fi by testing on Ethernet
Plug directly into the router with a known-good Cat5e or better cable and repeat the ping test. If latency and jitter drop significantly, the problem is wireless. If numbers stay identical, focus on the router, WAN link, or upstream path. - Test for bufferbloat under load
Open waveform.com/tools/bufferbloat or dslreports speed test. Run it while pinging 1.1.1.1 in another window. If idle ping is 20 ms but jumps to 200+ ms during the upload phase, you have bufferbloat. This is the single most common cause of 'fine speed test, terrible calls'. - Enable SQM or QoS on your router
On routers that support it (OpenWrt, pfSense, Ubiquiti, most modern ASUS/Netgear), enable Smart Queue Management (fq_codel or cake). Set the shaper to roughly 85–95% of your measured upload and download. This trades a small amount of throughput for a large drop in latency under load. - Optimise Wi-Fi if Ethernet is not an option
Move to the 5 GHz or 6 GHz band, pick a clear channel with a scanner like WiFi Analyzer, and set channel width appropriately (80 MHz on 5 GHz in low-noise environments, 40 MHz in dense ones). Position the router away from metal, microwaves, and Bluetooth hubs. - Update router firmware and network drivers
Log into the router admin page and apply the latest stable firmware. On the client, update the Wi-Fi or Ethernet adapter driver from the vendor site, not just Windows Update. Reboot both devices after updating so the new stack is fully loaded. - Trim background traffic and chatty apps
Cloud backup clients, OS updates, torrent apps, and video calls in another room all compete for the same uplink. Pause them, or reserve bandwidth for the critical app in QoS. On managed networks, check for a rogue device by looking at DHCP leases. - Escalate to your ISP with evidence
If traceroute or mtr shows sustained high latency starting at a specific ISP hop across multiple days, open a ticket with the mtr report, timestamps, and the affected destinations. Vague complaints get closed; hop-level data gets engineers involved.
Latency ranges and what they mean for common tasks
| Round-trip time | Category | Typical experience | Suggested action |
|---|---|---|---|
| Under 20 ms | Excellent | Ideal for competitive gaming, VoIP, real-time collaboration | Maintain baseline, monitor for drift |
| 20–50 ms | Good | Smooth video calls, responsive remote desktop | No action needed |
| 50–100 ms | Moderate | Occasional lag in games, minor voice delay | Check Wi-Fi, background traffic, bufferbloat |
| 100–200 ms | High | Noticeable lag, echo on calls, sluggish SSH | Enable SQM, test on Ethernet, update firmware |
| Above 200 ms | Severe | Unusable for real-time apps, timeouts likely | Run mtr, isolate hop, contact ISP with evidence |
Prevention
- Run a monthly baseline ping and bufferbloat test so you notice degradation early
- Keep router firmware on a scheduled update cadence, not 'when something breaks'
- Prefer wired connections for VoIP, video conferencing, and remote desktop workstations
- Replace consumer routers older than five years; ASIC and CPU limits compound over time
FAQ
Why is my ping high even though my download speed is fast?
Speed and latency measure different things. A 1 Gbps line can still deliver 300 ms ping if the router is bufferbloated or a hop is congested. Speed tests report peak throughput, not queue behaviour. Run a bufferbloat test under load to see the real-world latency your applications actually experience.
Does a VPN reduce or increase latency?
A VPN almost always adds latency because packets take a detour through the VPN server. In rare cases it can reduce latency if your ISP has poor routing to a specific destination and the VPN provider has better peering. Test both paths with mtr before deciding.
Will upgrading to a faster internet plan fix high ping?
Usually not. Extra bandwidth only helps if you are constantly saturating the link. If your idle ping is already high, the bottleneck is Wi-Fi, the router, or the ISP path, none of which change when you buy more Mbps. Fix the cause first, then decide if bandwidth is genuinely the limit.
Contact our network team for a latency audit of your office or home-office setup.