Packet Loss in Escape from Tarkov: How to Measure and Fix It

Packet loss means some of the data packets between your PC and the raid server never arrive. In Tarkov it shows up as rubber-banding (your character snaps back), doors and loot that react late, shots that seem to vanish and, when it is bad, a disconnect. It is different from high ping, which is steady delay, and from low FPS, which is your own hardware.

Settings and menu names below match the game as of patch 1.3.0 (October 2026).

Step 1: Measure it in the game

The official wiki's Debug Console page (last edited 18 August 2024, not re-tested for patch 1.3.0) documents an overlay command, fps [mode]. The console opens with the ~ key (or the key set in your controls):

Mode	What the overlay shows
0	Overlay off
1	FPS limit and current FPS
2	FPS limit, current FPS, RTT/Ping, packet loss and Player RTT
3	Everything in mode 2 plus update, game update, render and total frame times, and hardware measurements

Use mode 2 during a raid and watch whether packet loss rises when the symptoms start. If the number stays at zero while the game still stutters, the problem is more likely FPS or hardware than the network.

Step 2: Find where the loss starts

Windows has two built-in tools, both described in Microsoft's documentation.

• ping -t <address> keeps sending echo requests until you press Ctrl+C. A line that says "Request timed out" is a lost packet. By default Windows waits 4,000 ms for each reply.
• pathping -n <address> lists every router on the path, then sends 100 echo requests to each (the default) and reports lost and sent packets per hop and per link. Microsoft's own example runs for about 125 seconds before it prints results.

Run both once against your own router and once against a public site. Microsoft's guidance for reading pathping is useful here: loss shown on a link between two hops points to congestion on that link, while loss shown only on a router's own row can be that router ignoring traffic addressed to it, which does not affect forwarded traffic. In practice:

• Loss on the first hop is your own network: Wi-Fi, a bad cable or a busy router.
• Loss that begins at a later link and continues to the end of the list is on the route, usually with your provider or beyond.
• Loss that appears on one middle router and then disappears on the next hops is not a problem.

Step 3: Fix your own side first

None of these is Tarkov-specific, but they remove the most common local causes:

1. Use a wired Ethernet connection. Wi-Fi is the first suspect when loss shows on the first hop.
2. Stop other heavy transfers (cloud sync, game downloads, video streams) while you play, since they compete for the same line.
3. Restart the modem and router, then repeat the pathping test.
4. If loss appears on later hops in every test, send the pathping output to your provider so they can see where it starts.

Step 4: Check the region and the game version

Since 28 November 2022 the launcher lets you choose a region, not an individual data center. A region far from you adds steady delay, not packet loss, so a region change will not cure loss on its own. See the server region explainer.

Battlestate has also changed the server side several times. Patch 0.16.1.1.34993 (14 February 2025) adjusted the server logic to reduce packet loss and rubber-banding during character movement. Update 1.2.0 (6 October 2026) improved server-side position synchronization and said that more network work is planned. Earlier, patch 0.13.5.1.26165 (10 September 2023) partly rolled back changes to networking and inventory operations because they caused stutters. If the problem starts right after an update and your own tests are clean, wait for the next hotfix before changing your setup.

Common mistakes

• Blaming the network for low FPS. Check fps 2 before changing anything.
• Running pathping once and reading the middle rows as the proof. Loss on a single router row is not enough.
• Using Wi-Fi to test a wired fix. Test on the cable.
• Confusing packet loss with desync, where both sides are connected but disagree about what happened. The desync explainer covers that.

Related terms

• Ping, packet loss, queues and Error 213: the short glossary entry.
• Ping abuse: deliberate latency manipulation, and how it differs from a bad line.
• Error 213: a different connection error.
• Queue times: the wait before the raid starts.

The patch 1.0.2.5 breakdown lists one of the server improvement rounds.

FAQ

How do I see packet loss in Tarkov?

Open the debug console and enter fps 2. The wiki says the overlay then shows RTT/Ping, packet loss and Player RTT next to your FPS.

What causes packet loss in Tarkov?

Either your own line (Wi-Fi, a busy router, a provider fault) or the route to the server. A pathping to your router and to a public address shows which one.

Does a wired connection fix it?

It removes Wi-Fi as a cause, which is the most common reason for loss on the first hop. It will not help if the loss starts later on the route.

Did a patch fix packet loss?

Patch 0.16.1.1.34993 (14 February 2025) reduced loss and rubber-banding tied to server logic during movement, and 1.2.0 (6 October 2026) improved position sync. The notes do not claim that loss is fully gone.