High ping is a symptom, not a diagnosis. It can come from Wi-Fi interference, an overloaded uplink, a failing fiber path, a saturated upload, a busy router, a poor upstream route, or the remote server itself. Changing DNS or adding random firewall rules rarely solves the real cause. The fastest approach is to measure where latency begins to increase.
Video walkthrough
Step 1 — Establish a baseline
Test from a wired client when possible. Ping the local gateway, the ISP next hop if visible, a stable public IP, and the actual game or service endpoint if it responds. Record normal latency when the network is quiet. Without a baseline, every later change becomes guesswork.
Step 2 — Test while the line is busy
Run a controlled download and upload while keeping continuous pings running. If gateway latency stays low but public latency jumps, the bottleneck is likely beyond the LAN. If even the local gateway spikes, inspect Wi-Fi, Ethernet errors, CPU, and local queueing.
Step 3 — Check upload saturation
A fully saturated upload can make a network feel worse than a busy download because acknowledgements, DNS requests, game packets, and control traffic all compete for the same upstream queue. Shape both directions where you control the bottleneck, and leave enough headroom that your router—not the modem or upstream provider—does the queueing.
Step 4 — Inspect physical health
Check Ethernet error counters, optical power, LOS events, ONT logs, connector cleanliness, and switch port flaps. A physical problem can cause retransmissions and packet loss that users describe as lag. Do not hide these symptoms with more bandwidth rules.
Step 5 — Separate local congestion from upstream routing
Use traceroute and multiple destinations. If only one service has high latency while other destinations remain stable, the issue may be peering, routing, or the service itself. If every public destination becomes slow at the same time, inspect your uplink utilization and upstream handoff.
What to change only after measuring
Once you identify the bottleneck, choose the smallest appropriate fix: correct Wi-Fi channel planning, repair a bad link, move a heavy client, add shaping, upgrade an overloaded router, increase backhaul capacity, or raise the issue with the upstream provider using timestamps and measurements.
Frequently asked questions
Does changing DNS lower game ping?
Usually not after the game session is connected. DNS resolves names; the ongoing game traffic follows IP routing.
Is 1 ms always possible on fiber?
No. Fiber reduces access delay, but total latency also includes distance, routing, processing, and the remote server.
What is the most useful first test?
Compare gateway latency and public latency while the network is both idle and saturated.
Next step
Document the result of your test and keep a known-good export. If your network behaves differently from the example, diagnose the topology rather than adding more rules blindly. Continue with a related guide from the tutorial library.