It is entirely possible for Game A to show 25 ms and Game B to stay near 90 ms on the same PC and broadband line. They may connect to different cities, providers, relays, and matchmaking systems. When only one game has high ping, first identify where that match actually placed you, then compare the route in that direction. Reinstalling drivers or replacing the router before that check attacks the wrong layer.
Match the symptom to the first check
| Symptom | Suspect first | First action |
|---|---|---|
| One game and one region are high | Server selection or that regional route | Check the in-game server and compare alternatives |
| Every region in one game is high | Local network, ISP exit, or game service | Pause traffic, test Ethernet, check service status |
| High ping starts only in a party | Leader, party locations, or matchmaking rules changed the server | Record the actual server in solo and party play |
| Browser region tests look normal, game is high | Game server, relay, or client path differs | Trust in-game statistics and check official status |
| Ping is normal, but the picture stutters | It may not be network latency | Check FPS, frame time, device load, and server performance |
Ping from one game cannot prove another route is healthy
Ping measures a round trip to a specific destination. Change the destination and the number has no reason to remain the same. One game may place you in a local data center; another may choose a distant server because of account region, party members, queue population, or capacity.
The network design can also differ. Games such as CS2 and Dota 2 may use Steam Datagram Relay. Riot operates its own server and backbone system. Other titles use cloud regions or let matchmaking select data centers dynamically. Congestion at one interconnection can therefore affect only one game.
“Every other game is fine” is useful evidence because it narrows the search. It does not prove the publisher is at fault, nor does it clear the ISP automatically.
Step 1: identify the actual match region
Look in the lobby, performance display, or network graph for a region, data center, or ping. Some games let you select a preferred server, some only show the chosen data center, and others hide the decision behind matchmaking.
Compare solo and party play. A cross-region group can change the candidate server; waiting time and available capacity may also change placement. If the problem appears with particular friends, compare every member against the same regions instead of examining only the host's connection.
Step 2: decide whether the problem is global or directional
Run a multi-region test during the hours when the issue normally occurs:
- Every direction worsens: inspect local traffic, Wi-Fi, router, and ISP exit first.
- Only the game's direction worsens: distance or routing toward that region becomes more likely.
- Several directions are stable, but in-game ping is high: the PartyPing Probe and game server use different paths; continue with the actual game node and official status.
- Ethernet improves every direction: the home wireless link probably contributed.
PartyPing measures WebTransport round-trip time from the browser to PartyPing Probes, not directly to any publisher. It is useful for regional comparison and elimination; the game client's measurement remains the final evidence for the current match.
Step 3: act only on the layer supported by evidence
If changing server region fixes the issue, stop there. If Wi-Fi and Ethernet both fail only toward one direction, save comparable results from multiple times and give the ISP the destination region and timestamps.
If a nearby PartyPing direction is stable while the game suddenly degrades, check official service status, patch notes, and the client's network graph. A clean browser test does not prove the game server is healthy, but it prevents endless changes to a home network that is not implicated.
If the game looks choppy while network statistics stay clean, investigate shader compilation, frame time, temperature, and device load. Rendering stutter and network delay can both look like “lag,” but their fixes are unrelated.
Do not treat these as universal fixes
- Changing DNS: mainly changes name resolution, not the established match route.
- Repeated router restarts: can clear a temporary device fault but cannot shorten server distance.
- Buying more bandwidth: capacity and round-trip delay are different metrics.
- Using a VPN or game booster blindly: a new route helps only if it avoids the old congestion; compare the same region before and after.
- Keeping only the lowest ping sample: one lucky packet does not represent a full match; inspect range and loss.
The goal is not to win an argument about “ISP versus game server.” It is to find the next action supported by the evidence: change region, use Ethernet, pause traffic, wait for service recovery, or send useful data to the responsible party.
Official references
- Riot Games: network architecture and Riot Direct
- Valve: Steam Datagram Relay
- EA: Apex Legends data centers, ping, and packet loss
Sources reviewed: 2026-09-17.