How to fix high ping, lag and packet loss in Deadlock

Find out whether it’s your PC, your network or the server: turn on the Telemetry HUD, read it, and fix what you can control.

Is it your PC, your network or the server?

Turn on the Telemetry HUD under Settings > Video > HUD Telemetry, play a match, and watch which number turns red when the game stutters. High ping means distance or a bad route, missed ticks mean packet loss or jitter, and frame-time spikes mean the problem is your PC, not your connection.

Most lag fixes fail because they fix the wrong thing. In a fight a frame-time hitch and a network hitch feel identical: rubber-banding, a dash that snaps back, bullets that don’t land. Work out which one you have before you change anything.

How to show ping and packet loss in Deadlock

Deadlock shares the Source 2 Telemetry HUD with Counter-Strike 2. In Settings > Video > HUD Telemetry, each readout can be set to never show, always show, or show only when conditions are poor, with your own warning threshold for each. A value that crosses its threshold turns red.

Set ping and the network readouts to always while you diagnose. Once you know your normal numbers, switch them back to show only when poor, so the HUD stays clean until something goes wrong.

1. 01Set the frame-time warning slightly above your usual worst frame. A red frame time then means the hitch came from your PC.
2. 02Set the tick miss warning low, around 0.1% to 0.5%, as Valve suggests. A red miss rate then means the hitch came from the network.
3. 03Turn on the detailed network view for the raw loss and jitter numbers next to ping.

Reading the Telemetry HUD

Ping is round-trip latency in milliseconds: how long a packet takes to reach the server and come back. It measures the network trip only, not how fast your PC renders.

The two numbers with up and down arrows are the tick miss rate, and Deadlock runs at 60 ticks per second. Down is how often your client needed the next server update and it hadn’t arrived; up is how often the server needed your input and it hadn’t arrived. 0% doesn’t mean your connection is perfect, only that it isn’t costing you ticks right now.

The detailed view adds loss (packets that never arrived) and jitter (packets that arrived late or in clumps). Jitter matters as much as loss, because a packet that turns up too late is as useless as one that never comes.

The jitter graph draws one bar per network message. A solid red line is a dropped packet, a purple line is packets arriving out of order, and red bars are jitter high enough to risk a missed tick.

What your numbers mean

Steady high ping with no misses is distance. You’re on a far server or your traffic is taking a long route, so everything feels late but consistent. No setting fixes that; only a closer server or a better route from your ISP does.

Normal ping with red tick misses is packet loss or jitter, and it’s the classic rubber-band: you dash, snap back, and a parry you were sure you hit never happens. This one usually starts at home, with Wi-Fi, another device downloading, or a struggling router.

Normal ping and no misses but a red frame time means your PC hitched, and your network is fine. Lower your graphics settings, close background apps and update your GPU driver.

Buffering to smooth over packet loss

Settings > Game has an option called Buffering to smooth over packet loss / jitter. Raising it adds one or more ticks of delay, so when a packet drops or arrives late the game already has the next one and can fill the gap.

The engine already adjusts buffering on its own, which handles steady, noisy jitter well. Manual buffering is for rare, big spikes: a connection that’s calm for a minute, then drops a burst of packets in the middle of a fight.

You pay for it in latency. Each tick of buffering adds about 17 ms at 60 ticks per second, so only raise it if the HUD shows red tick misses, one step at a time.

1. 01On a stable wired connection, leave it at default. Raising it there only makes you later.
2. 02Raise it one step if you see red misses in most matches and can’t fix the cause.

Fix packet loss on your end first

Most packet loss and jitter starts between your PC and your router, which is also the part you can fix. Go through this before you blame the servers.

1. 01Plug in an ethernet cable. Wi-Fi is the most common cause of jitter, and a cable fixes more lag than any setting.
2. 02If you’re stuck on Wi-Fi, use the 5 GHz band and get closer to the router.
3. 03Pause Steam downloads, cloud backups and streams on other devices while you play. Uploads hurt as much as downloads.
4. 04Restart the router if loss shows up out of nowhere.
5. 05Test your local network: open Command Prompt and run ping -n 100 followed by your router’s IP address. Lost packets or big spikes to your own router mean the problem is inside your home.
6. 06If the router test is clean but the game still shows loss, the problem is further down the line. Run the same test against a public address, note when it happens, and take the results to your ISP.

How to check your server region

The matchmaker picks your region automatically, so the best you can do is let it see your real connection. Close any VPN before you queue: it changes the route the game measures and can land you on a server further from home.

There’s a console variable, citadel_region_override, described as overriding the client’s region. The community wiki lists it as not working at the moment and players report it doesn’t stick, so don’t count on it.

Custom lobbies are different. When you host a private match you choose which region’s server it runs on, which helps for scrims with friends across a border: pick the region in the middle.

Console commands for network info

Turn on Dev command console in Settings, then press F7 to open it. These commands only report information. They don’t change your connection or give you an edge, so they’re safe in any match.

1. 01net_print_sdr_ping_times prints your ping to each of Valve’s relay points and the route you’re using.
2. 02net_status shows your current connection state.
3. 03cl_hud_telemetry_ping_show 2 always shows ping. 0 is never and 1 is only when poor, same as the menu.
4. 04cl_hud_telemetry_net_detailed 2 always shows the loss and jitter breakdown.
5. 05cl_showfps 1 adds a simple FPS counter, separate from the Telemetry HUD.

Do you need a VPN or ping booster?

Usually not. Deadlock already connects through Valve’s own relay network, the SDR points of presence you see in net_print_sdr_ping_times, which picks a route for you. A VPN only adds another stop to that trip.

If your ping is high because you live far from the nearest servers, no app changes the distance. If it’s loss or jitter, the cause is almost always local, and a cable fixes it for free.

When it’s not you

If the whole lobby rubber-bands at once, or your HUD is clean and the game still feels off for everyone, it’s probably the server or a wider outage. Check the official Deadlock forums for reports before you touch your settings, or you’ll end up undoing changes that were never going to help.