Overwatch 2 lag and high ping: causes and fixes

Overwatch 2 has one of the best built-in tools for finding lag: a network graph that shows not just your ping, but when it's high enough to cause trouble. Here's how to read it, and what to do about what it shows.

Open the network graph

Press Ctrl + Shift + N in a match. A graph appears with your connection over time, and each line has three numbers beside it: the lowest, the average and the highest value so far.

• Latency: the round trip to the server. A high average is distance or a long route; a high maximum with a normal average means spikes.
• Interpolation delay: how far behind the game shows other players, so their movement looks smooth.
• Orange bars: the moments your latency went above the interpolation delay. That's when heroes warp and abilities fire late. Lots of orange means a connection problem.
• Loss, in and out: data that didn't arrive. Even a little shows up as stutter.

Play a whole match with it on, and look at where the orange is. A steady problem and one that comes in bursts have different causes.

Why Overwatch lags

Blizzard's servers run each match and send every player what happened. Your game predicts your own actions so they feel instant, and the server confirms or corrects them. When your updates arrive late or unevenly, corrections show: you're pulled back, a hook connects that you dodged on your screen, a shield you raised went up late.

Distance to the server and the road your provider takes to Blizzard decide the steady part of your latency. Wi-Fi, a busy line at home and a provider's evening queues decide the spikes.

What helps

1. Use a cable. It removes most of the spikes that turn into orange bars. Wi-Fi or Ethernet explains.
2. Keep the line quiet during matches: uploads, downloads, streams elsewhere in the home.
3. Fix the router's queue (SQM, or QoS that's actually set) if the connection is shared.
4. Note when it happens. Every evening at the same time is your provider's busy hours, not your PC. What causes ping spikes shows how to prove it.
5. Change the route when your average latency is higher than distance explains.

A low frame rate also feels like lag in a fast hero shooter. If the network graph is clean and the game still feels heavy, it's the PC: Windows settings for FPS.

Where NoSpike fits

NoSpike's Overwatch 2 entry is a beta: its servers are still being mapped, so NoSpike may not carry all of a match's traffic yet. While you play, its page in the app says what it carries, and on a server NoSpike doesn't route it shows your own ping and says "Match not routed".

Where it does carry the game, it measures your own route and the routes through its relays in Europe, and routes Overwatch 2 only when a relay is faster. It doesn't move you in the middle of a match unless the route fails.