Delay compensation can make multiplayer games look smoother, but it doesn't remove network delay. Prediction, interpolation, rollback, and server rewind can hide or manage late data; they can't lower ping, repair packet loss, or fix a congested Wi-Fi connection.

During the next lag spike, check the game's network statistics. Then compare Wi-Fi with Ethernet, repeat the test while the household connection is busy, and see whether every game is affected or only one title. That evidence points to the right next step: adjust your home network, contact your internet service provider (ISP), or report the problem to the game publisher.

This guide is for players in the United States. Game-networking policies and ISP complaint procedures can differ in other countries.

Delay compensation: what it can and can't fix

Games use several techniques to make unavoidable delay less noticeable:

• Client-side prediction shows your movement immediately instead of waiting for the server.
• Server reconciliation corrects the client when its prediction differs from the authoritative game state.
• Interpolation smooths the movement of other players between received updates.
• Rollback netcode restores a previous game state and replays inputs when a late input arrives.
• Server rewind or lag compensation uses a recent historical state when checking events such as a shooter hit.

These features are controlled by the developer and game server. Players generally can't turn rollback, server rewind, or reconciliation on through a console or PC setting. They can make a game feel smoother, but they can't eliminate the time needed for data to travel or repair a damaged Wi-Fi connection.

As a result, movement may look smooth while hit registration still feels delayed. A prediction can also be rejected by the server, causing rubber-banding. Whether a title favors the player who fired, the player who was hit, or the latest server state is a game-specific design decision.

What multiplayer lag looks like

These problems can overlap. For example, a busy upload can increase latency and jitter at the same time, while weak Wi-Fi can cause both packet loss and repeated prediction corrections.

Test the connection before changing your plan

A single speed test won't tell you everything. Speed tests usually connect to a nearby test server, while your game may use a server in another city or country. Download speed measures capacity, not the complete quality of a real-time game connection.

Use this process:

1. Enable the game's network graph or statistics. Record ping, packet loss, and server region during several matches.
2. Test at different times. Compare a quiet period with the hours when lag is most noticeable. A problem that appears mainly in the evening can point to congestion.
3. Compare Wi-Fi and Ethernet. Connect the console or computer directly to the router with Ethernet, if possible. Keep the game, server region, and time of day similar.
4. Repeat the test while the connection is busy. Check whether another person is streaming, uploading photos, using cloud backup, or downloading a large file.
5. Check more than one game. If only one title is affected, changing your internet plan may not help.

For a basic external test, send repeated pings to a stable public address:

Windows: ping -n 50 1.1.1.1
macOS/Linux: ping -c 50 1.1.1.1

You can also inspect the route:

Windows: tracert 1.1.1.1
macOS/Linux: traceroute 1.1.1.1

These commands don't measure the exact path to a game server. They can still show large variations or loss somewhere outside the game. An individual intermediate hop isn't automatically the cause; some routers don't respond to diagnostic traffic even when they forward normal data correctly.

Record the date, time, connection type, game server region, and results. A short record gives an ISP or game-support team something concrete to investigate instead of a report that the game is simply "always laggy."

Fix common causes in the safest order

1. Try Ethernet first

A wired connection removes much of the interference and signal variation associated with Wi-Fi. It won't shorten the physical distance to a game server, but it can reduce local packet loss and jitter.

If Ethernet isn't practical:

• Move the console, computer, or streaming device closer to the router.
• Keep the router in an open, elevated location rather than inside a cabinet.
• Try the router's 5 GHz or 6 GHz network when the device is nearby.
• Avoid placing the router beside thick walls, large appliances, or other wireless equipment.
• Test the connection without a wireless extender. An extender can improve coverage but may add another point of delay or interference.

2. Stop competing traffic

Pause cloud backups, large downloads, video uploads, and automatic updates while playing. Upload traffic can be especially disruptive because a connection may become congested even when download speed looks generous.

If lag appears only when someone else is using the connection, check whether your router supports Quality of Service (QoS) or Smart Queue Management (SQM). These features can control queues so one upload or download doesn't dominate the connection. A reasonable starting point is to set the bandwidth limit near 90-95% of the repeatable speed you measure, then retest. That isn't universal: setting it too low can waste capacity, while setting it too high may not control congestion.

3. Choose a nearby game region

Use the game's automatic or recommended region unless it consistently selects a distant server. If the game allows a manual choice, select the nearest region that provides stable ping and low packet loss.

Don't assume a VPN or "gaming route" service will reduce lag. It can occasionally improve a poor route, but it can also add distance, encryption overhead, or another congested connection. Compare it with a normal connection under the same conditions before paying for a subscription.

4. Check platform and router settings

A strict NAT can interfere with matchmaking, voice chat, or joining other players, but NAT status isn't the same as high ping. Don't open a large range of ports as a first response.

Instead:

• Run the platform's built-in network test.
• Check for double NAT if you use an ISP gateway with a separate router.
• Update router firmware and console or PC network software.
• Review the router's UPnP or port settings using the game's official instructions.
• Check the game's and platform's service-status pages when multiple players report problems.

A factory reset can erase useful router settings and usually shouldn't be the first troubleshooting step.

5. Separate network problems from performance problems

If the network graph is stable but the picture stutters, check frame rate, overheating, background applications, storage space, and display settings. On a TV, game mode can reduce display processing delay. On a PC, compare network statistics with frame-time or FPS data.

A game that feels slow because of low frame rate needs a device or graphics adjustment, not a new ISP plan.

PS Portal and Remote Play lag

Remote Play adds another connection path. The PS Portal must maintain its Wi-Fi link to the home network, while the PS5 and PlayStation service must maintain their own network connections. A problem on either side can affect the experience.

PlayStation's PS Portal troubleshooting guidance recommends upload and download speeds of at least 5 Mbps as a general baseline. That number isn't a guarantee of smooth play: stable latency, low jitter, and a reliable Wi-Fi signal still matter.

For a PS Portal problem, test the Portal close to the router, compare it with a different Wi-Fi band, and connect the PS5 to the router by Ethernet if possible. If other devices also have trouble, investigate the home connection. If regular console play is stable but Remote Play remains problematic, focus on the Portal, PS5 settings, and the Remote Play path rather than buying more download speed.

Should you buy a faster internet plan?

A faster plan may help when the connection is regularly saturated, particularly during uploads or heavy household use. It usually won't fix high ping caused by a distant game server, poor routing, or weak Wi-Fi.

Mobile 5G can be a useful alternative where its local route is better than fixed broadband, but its latency can vary with signal, network load, and location. A "5G" label doesn't guarantee lower gaming latency.

When to contact your ISP

Contact the ISP when the problem appears across several games or services, remains present over Ethernet, or gets worse during a repeatable time window.

Give support:

• The dates and times of the failures
• Whether the test used Ethernet or Wi-Fi
• Ping, jitter, and packet-loss results
• The affected devices and games
• The server regions you tested
• Your modem and router models
• Whether other household devices were using the connection
• Any case numbers or earlier technician visits

Ask the ISP to check line errors, packet loss, and latency under load, not just the advertised download speed. If the issue is consistently worse during evening hours, mention that pattern and request escalation to a network or technical support team.

For U.S. consumers, the FCC's internet complaint categories include concerns involving internet latency and equipment. Keep your provider's responses and test records if you use that route. An FCC complaint is an internet-service escalation path; it can't change a game developer's netcode or repair a problem limited to one game server.

When to contact the game publisher

Contact the publisher or platform when:

• Other games work normally on the same connection.
• Players in the same match report the same issue.
• The problem follows one server region or matchmaking pool.
• The game shows packet loss or server errors even on Ethernet.
• A recent patch changed the behavior.

Include a short video, match or session ID, server region, local time and time zone, network graph, and whether you used a VPN, Wi-Fi, or Ethernet. This gives support enough detail to compare your report with server logs.

Common questions

Does Ethernet always lower ping?

No. Ethernet can't remove latency caused by server distance or routing. It can reduce Wi-Fi interference, packet loss, and jitter, so it often makes the connection more consistent.

Is 100 ms ping unplayable?

There is no universal cutoff. Competitive reaction-based games expose delay more clearly than turn-based, strategy, or casual games. Consistent 100 ms latency can feel more usable than a connection that jumps between 30 ms and 100 ms.

Why does a speed test look good while my game lags?

The speed test may use a nearby server, while the game uses a different route. The game can also be affected by packet loss, jitter, server load, or household congestion that a short speed test doesn't reveal.

Can I enable rollback netcode or server rewind?

Usually not. Those features are built into the game and its networking model. You can improve the connection feeding the game, but only the developer can change how the server handles late inputs and hit detection.

What should I do first?

During the next lag spike, record the game's network statistics, stop other uploads, and repeat the match over Ethernet if possible. If the same issue appears across multiple games on a wired connection, send that evidence to your ISP. If it affects only one title, send it to the game's support team.