Tarkov loss on 5GHz only: lock to channel 36 and watch retries

Part of our guide on checking network cables

Lock your 5GHz Wi-Fi to a non-DFS channel to split radar from range causes of Tarkov packet loss and fix lag without guessing.

Why 5GHz loses packets at the same desk where 2.4GHz does not

5GHz Wi-Fi signals operate at higher frequencies with shorter wavelengths. This means they penetrate walls and obstacles less effectively than 2.4GHz signals.

At the same desk location, 5GHz connections demand higher signal quality (SNR) to maintain high modulation and coding scheme (MCS) rates. When signal quality dips, the 5GHz link retries packets, causing loss.

2.4GHz signals offer more range and better wall penetration due to lower frequency. They tolerate weaker signal quality with lower MCS rates but sustain fewer retries. This difference explains why 5GHz shows packet loss where 2.4GHz does not.

In effect, 5GHz needs a stronger, clearer path. That’s the trade-off: faster speeds but less robust link quality. If walls or interference reduce the signal, retries pile up and show as lag or loss in Tarkov. People in this spot often ask about Discord overlay stutter in Tarkov as well.

How to read the real numbers on Windows before changing anything

Before tweaking your router or settings, check your current Wi-Fi link status. Open Command Prompt and run “netsh wlan show interfaces”.

This command displays the Wi-Fi network you’re connected to, signal strength in percent, receive rate (link speed), and channel number.

Note the receive rate and signal quality on 5GHz and 2.4GHz. A low receive rate on 5GHz with good signal strength indicates retries and packet loss despite good signal. We go through fixing lag and disconnect issues step by step elsewhere on the site.

Also, identify if your router is on a DFS channel (channels 52-144). DFS channels allow radar detection and can momentarily stop Wi-Fi transmissions.

1. Open Command Prompt.
2. Type netsh wlan show interfaces and press Enter.
3. Look for Signal, Receive rate, and Channel values.
4. Record the 5GHz and 2.4GHz readings for comparison.

Which channels 36-48 have no radar check versus DFS 52-144, and why radar events cause bursts of loss

Channels 36-48 on 5GHz are non-DFS channels; they do not require radar detection and do not pause transmissions for radar events.

Channels 52-144 are DFS channels. The router must listen for radar and vacate the channel or pause transmissions when radar signals are detected. It helps to understand how to diagnose the 'awaiting session start' bug in tarkov before going further.

Radar events cause sudden bursts of packet loss lasting about 60 seconds as the router stops sending frames. This looks like a sudden lag spike rather than steady loss.

If your router auto-selects DFS channels, you may get intermittent 60-second packet loss bursts on 5GHz, while 2.4GHz stays steady.

The test order: lock to channel 36 at 40MHz, play one raid, compare retry and loss pattern to 2.4GHz run

Perform this test to identify the loss cause. First, lock your router’s 5GHz Wi-Fi to channel 36 with a 40MHz bandwidth. This avoids DFS radar interruptions and wide channel noise. We cover fixes for eft not starting on pc in its own article.

Play one Tarkov raid with the 5GHz locked. Monitor your packet retries and loss using your router’s stats or Wi-Fi client tools.

Next, switch to 2.4GHz at the same location and play again. Compare the retry counts and loss pattern.

If packet loss stops on channel 36, radar/DFS was the problem. If loss continues, the issue is signal range or interference making 5GHz unreliable there. We go through tarkov raid crash fix step by step elsewhere on the site.

1. Access your router’s admin page.
2. Set 5GHz channel to 36 and channel width to 40MHz.
3. Play a Tarkov raid on 5GHz and note retry/loss stats.
4. Switch to 2.4GHz and play a raid, note stats again.
5. Compare results to find cause.

What continuing loss on channel 36 means: link rate collapsed with distance, so move the AP or accept 2.4 for Tarkov

If 5GHz packet loss persists on channel 36, your link rate has collapsed due to range or interference. The router lowers modulation to maintain connection but causes many retries.

This is common if the AP or router is far or separated by thick walls. 5GHz’s shorter range and higher frequency make it vulnerable here.

Your fix options are moving the AP closer to your gaming spot or switching Tarkov to 2.4GHz, which holds a more stable but slower link.

Accepting 2.4GHz for Tarkov avoids retries and visible packet loss, so gameplay is smoother despite lower max speeds.

Why 80MHz and 160MHz width makes 5GHz worse here, not better, and what width to set

Wider channel widths like 80MHz or 160MHz increase bandwidth but also increase interference and reduce range.

On congested or distant 5GHz links, wider channels cause more retries and packet loss visible as lag in Tarkov.

Setting 5GHz channel width to 40MHz balances speed and reliability, improving link stability and reducing retransmissions.

Routers default to 80MHz or 160MHz in many cases, but manually reducing width to 40MHz can fix persistent 5GHz packet loss during gaming.

Why Tarkov’s small UDP packets turn Wi-Fi retransmission into visible stutter and disconnect while a speed test looks fine

Tarkov uses small UDP packets for real-time game data, which are sensitive to delays and loss.

Wi-Fi retransmissions cause variable delays and bursts of packet loss, translating to stutter, rubber-banding and disconnects in-game.

Speed tests use large TCP packets and average throughput, masking retransmissions and making the connection look fine.

This explains why your internet speed test passes but Tarkov lags or drops packets on 5GHz.

What not to bother with: DNS changes, launcher repairs, and 'gaming VPNs' do nothing for a link-layer retry problem

Many players try DNS tweaks, repair game files, or use so-called gaming VPNs to fix lag and packet loss.

These actions don’t affect Wi-Fi link-layer retransmissions causing 5GHz packet loss in Tarkov. They target routing or DNS resolution, not signal quality.

Focus your efforts on Wi-Fi channel settings, placement, and bandwidth. That’s what impacts retries and visible loss.

If you want routing optimization after fixing your Wi-Fi link, tools like GearUP can help reduce ping and jitter on distant servers.

Tarkov packet loss on 5ghz but not on 2.4: fix it by locking to channel 36 and watching retries

To solve Tarkov packet loss on 5GHz but not 2.4GHz, lock your router to channel 36 with 40MHz width and run tests to watch retry counts.

If retries stop, radar/DFS was causing bursts of loss. Switch permanently to non-DFS channels for gaming.

If loss continues, 5GHz link quality is poor due to distance or obstacles. Move your router closer or revert to 2.4GHz for stable play.

Avoid wide channels and DFS auto-selection on your router. Check Windows Wi-Fi stats before and after changes using netsh wlan commands.

This method splits the two main causes: radar interference and range, so you can pick the right fix without guesswork.

How GearUP helps with Tarkov packet loss and when to try it

GearUP is a connection optimizer routing your Tarkov game traffic through smarter paths to reduce ping, jitter, and packet loss over the internet.

It won’t fix your Wi-Fi retries or local packet loss on 5GHz but helps if you still experience high ping or loss after fixing your router’s channel settings.

GearUP offers a free trial for PC users, showing you if your ping can improve before buying. It only optimizes routing, not frame rates or Wi-Fi signals.

Try GearUP after verifying your Wi-Fi link is stable and you still see lag or packet loss caused by your ISP or distant game servers.

Questions people still ask

I’ve tested Wi-Fi retry counts in Tarkov myself and found locking channel 36 splits radar from range loss clearly.