Fortnite Packet Loss: How to Fix It
You line up a clean headshot, pull the trigger, and nothing happens. Your walls won't place. Your character snaps back ten meters like the server just rewound time. You open the network debug overlay and see the dreaded packet loss percentage climbing. Sound familiar?
Packet loss in Fortnite is one of the most frustrating problems you can deal with because it breaks the fundamental contract between your inputs and what happens on screen. Unlike raw ping, which at least feels consistent, packet loss is unpredictable. One second you're fine, the next you're rubber-banding into the storm. Builds appear a full second late — or never appear at all. Shotgun shots phase through opponents. Edits feel sluggish even though your FPS is fine.
Fortnite is especially punishing when it comes to packet loss because the game relies on a constant stream of small, time-sensitive updates between your client and Epic's servers. Every building piece, every weapon swap, every movement tick is a packet. When those packets go missing, the server and your client disagree about what's happening, and the server always wins. That's the rubber-banding — the server correcting your client's wrong assumptions about where you are and what you've done.
The good news is that most Fortnite packet loss problems are fixable on your end. This guide walks through exactly how to diagnose what's going wrong, what's causing it, and how to fix it step by step.
How to Check Packet Loss in Fortnite
Fortnite's Built-In Net Debug Stats
Fortnite has a built-in network overlay that shows you real-time connection data. To enable it, go to Settings → Game → HUD → Net Debug Stats and toggle it on. Once enabled, you'll see a small overlay on your screen during matches showing several key metrics:
- Ping — Your round-trip latency to Epic's servers in milliseconds. Under 30ms is excellent, 30-60ms is good, above 100ms is where you'll start to feel delay.
- Packets Up / Down — The number of packets per second being sent and received. These should stay relatively consistent. If the "Down" number drops to zero intermittently, you're experiencing packet loss.
- Packet Loss % — The percentage shown directly. Anything above 0% is a problem. Even 1-2% packet loss in Fortnite will cause noticeable issues because of how frequently the game sends updates.
- Up % — Upload packet loss specifically. If this is high but download loss is low, your outgoing packets are being dropped. Your inputs (shots, builds, movement) aren't reaching the server.
Pay attention to when the loss spikes. Does it happen consistently, or only during busy fights with lots of players? Does it get worse at certain times of day? These patterns tell you a lot about the root cause.
Testing Outside of Fortnite
Fortnite's overlay is helpful, but it only tells you what's happening between your PC and Epic's servers while you're in a match. To get a clearer picture of whether the problem is your connection or Epic's servers, you need to test independently.
PacketProbe measures packet loss, latency, and jitter using the same type of UDP-like traffic that games use. Run a test with the Gaming preset before you launch Fortnite. If PacketProbe shows packet loss, the problem is your network — not Fortnite's servers. If PacketProbe shows a clean connection but Fortnite's overlay shows loss, the issue is likely on Epic's end or in the routing path to their specific servers.
Run tests at different times of day to spot patterns. If your packet loss is always worse in the evening, network congestion during peak hours is likely the cause.
What Causes Packet Loss in Fortnite
Wi-Fi Instability
This is the number one cause of packet loss in Fortnite, and it's the one most players don't want to hear. Wi-Fi is inherently unreliable for real-time gaming. Even a strong Wi-Fi signal doesn't guarantee consistent packet delivery. Interference from other networks, walls, electronic devices, and even people moving around your home can cause momentary packet drops that show up as rubber-banding in game.
The 2.4GHz band is especially problematic because it's shared with Bluetooth devices, microwaves, baby monitors, and every other Wi-Fi network in range. The 5GHz band is better but has shorter range and is more affected by walls.
Server Region and Routing
Fortnite runs on AWS (Amazon Web Services) infrastructure. When you connect to a match, your packets travel from your home, through your ISP's network, through various internet exchange points, and eventually reach an AWS data center. Any congestion or routing issues along that path can cause packet loss.
If your game is set to Auto region selection, Fortnite picks the server it thinks has the lowest ping. But lowest ping doesn't always mean lowest packet loss. You might get routed to a server with 20ms ping but 3% packet loss, when a different region at 35ms ping has 0% loss. The second option will feel better in game.
ISP Routing to AWS Infrastructure
Some ISPs have poor peering arrangements with AWS, the cloud provider that hosts Fortnite's servers. This means your packets take inefficient or congested routes to reach Epic's infrastructure, even if your overall internet connection is fast. This is particularly common with smaller regional ISPs and during peak evening hours when backbone links are saturated.
Peak Hour Congestion
Fortnite packet loss that only shows up between 7pm and 11pm is almost always ISP congestion. Your neighborhood node is shared with other households, and when everyone gets home and starts streaming, gaming, and downloading, the available bandwidth gets squeezed. Your ISP may not be dropping packets on their own network, but the congestion causes buffer overflow at key routing points.
Epic Server Issues
Sometimes it genuinely isn't your fault. Epic's servers experience issues, especially during major events, new season launches, or popular limited-time modes. When millions of players flood the servers simultaneously, packet loss can spike even for players with perfect home networks. We'll cover how to tell if the problem is server-side later in this guide.
Background Applications
Anything consuming bandwidth in the background can compete with Fortnite for your network resources. Common culprits include cloud sync services (OneDrive, Google Drive, Dropbox), Windows Update downloading in the background, other game launchers updating games, streaming apps, and browser tabs with active video or audio.
How to Fix Packet Loss in Fortnite
1. Use a Wired Ethernet Connection
If you're on Wi-Fi and experiencing packet loss, switching to Ethernet is the single most impactful change you can make. A direct cable connection eliminates wireless interference entirely. If running a cable isn't practical, a powerline Ethernet adapter is a decent alternative — it won't be as good as a direct cable, but it's usually much more reliable than Wi-Fi for gaming.
After switching to wired, run a PacketProbe test to confirm the loss is gone. If it is, your problem was Wi-Fi. If it persists, keep troubleshooting.
2. Select Your Server Region Manually
Don't rely on Fortnite's Auto region setting. Go to Settings → Game → Matchmaking Region and manually select the region closest to you. In North America, you'll see options like NA-East and NA-West. Try each one and note both the ping displayed and your actual in-game packet loss using Net Debug Stats. Sometimes a region showing slightly higher ping will have less packet loss because of better routing.
3. Change Your DNS Servers
Slow or unreliable DNS resolution can cause connection hiccups. Switch to a fast public DNS provider:
- Google DNS: Primary: 8.8.8.8, Secondary: 8.8.4.4
- Cloudflare DNS: Primary: 1.1.1.1, Secondary: 1.0.0.1
On Windows, go to Settings → Network & Internet → your connection → DNS server assignment → Edit and enter these manually. This won't directly fix packet loss in most cases, but it eliminates DNS as a variable and can improve initial connection times.
4. Set Up Port Forwarding
Fortnite uses specific network ports. If your router's firewall is being overly aggressive with traffic it doesn't recognize, opening these ports can help:
- UDP 5222 — Used for XMPP (Epic's presence and chat system)
- UDP 5795-5847 — Used for game traffic
Log into your router's admin panel (usually 192.168.1.1 or 192.168.0.1) and set up port forwarding rules for these ranges, directed at your PC or console's local IP address. If your router supports UPnP, make sure it's enabled as Fortnite can negotiate ports automatically through UPnP.
5. Enable Quality of Service (QoS)
QoS settings on your router let you prioritize gaming traffic over bulk downloads and streaming. Most modern routers have some form of QoS — look for it in your router's admin panel under Advanced settings or Traffic Management. Prioritize traffic from your gaming device, or if your router supports application-based QoS, prioritize game traffic specifically.
This is especially important in households with multiple people using the internet simultaneously. QoS won't increase your total bandwidth, but it ensures Fortnite's small, time-sensitive packets get through first.
6. Close Background Applications
Before launching Fortnite, close or disable anything that might be consuming bandwidth:
- Pause cloud sync services (OneDrive, Google Drive, Dropbox, iCloud)
- Close browser tabs — especially those with video, music, or social media
- Pause or schedule Windows Update for later
- Quit other game launchers (Steam, Battle.net) that may be downloading updates
- Disable any VPN — VPNs add latency and can increase packet loss
7. Verify Game Files
Corrupted game files can cause network-related bugs. In the Epic Games Launcher, go to your Library, click the three dots next to Fortnite, and select Verify. This checks all game files against Epic's servers and redownloads anything that's been corrupted or modified.
8. Reinstall Easy Anti-Cheat
Easy Anti-Cheat (EAC) occasionally causes network issues, especially after Windows updates. To reinstall it, navigate to your Fortnite installation folder (typically C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\Win64\EasyAntiCheat), run EasyAntiCheat_Setup.exe, select Fortnite from the list, and click Repair Service. Restart your PC afterward.
9. Restart Your Router
A simple router restart clears congested buffers, refreshes connection tables, and can resolve intermittent loss. Unplug your router for 30 seconds, then plug it back in. If you find yourself needing to do this regularly, your router may be due for a firmware update or replacement.
Best Settings to Reduce Lag in Fortnite
Beyond network fixes, there are in-game settings that reduce the load on your connection and make the game feel more responsive even when your network isn't perfect.
Disable Replays
Go to Settings → Game → Replays and disable Record Replays, Record Large Team Replays, and Record Creative Replays. The replay system writes data constantly during gameplay, which consumes system resources and can contribute to hitching that feels like network lag.
Limit Matchmaking Ping
Under Settings → Game → Max Matchmaking Ping, set this to a reasonable value like 50-65ms. This prevents Fortnite from putting you into matches on distant servers with high ping. A lower value means potentially longer queue times but better connection quality once you're in a match.
Disable Cosmetic Streaming
In Settings → Game → Content, set Cosmetic Streaming to Off. When enabled, Fortnite downloads skin data on-the-fly during matches. This uses bandwidth that could otherwise be dedicated to game traffic and can cause micro-stutters when new players come into view.
Use Performance Mode
Under Settings → Video → Rendering Mode, switch to Performance mode if your system struggles with frame rate. While this is primarily a GPU/CPU optimization, maintaining consistent frame timing helps the game's network interpolation code run smoothly, which reduces the perception of lag even if your network metrics haven't changed.
Disable High-Quality Audio
In Settings → Audio, consider setting quality to Low if you're on a marginal connection. High-quality spatial audio processing can cause occasional CPU spikes that affect network tick processing on lower-end systems.
When It's Not Your Fault
Sometimes you've done everything right — wired connection, clean network, all the right settings — and you still get packet loss in Fortnite. Here's how to tell if the problem is on Epic's end.
Check Epic's Server Status
Visit status.epicgames.com to see if there are any active incidents affecting Fortnite. Epic posts updates here for server outages, degraded performance, and scheduled maintenance. You can also follow @FortniteStatus on X (formerly Twitter) for real-time updates.
Compare Your Results
Run a PacketProbe test. If your connection shows 0% packet loss and low jitter in the test, but Fortnite is still showing loss in the Net Debug Stats overlay, the problem is almost certainly between your ISP and Epic's servers, or on Epic's servers themselves. This is especially common during:
- New season launches — Server load spikes massively in the first 24-48 hours
- Major in-game events — Live events like concerts or story events draw millions of simultaneous players
- Weekend evenings — Peak player counts combined with peak ISP congestion
- Patch days — Servers can be unstable immediately after updates
Check Community Reports
If Fortnite's servers are having issues, you won't be the only one affected. Check platforms like Reddit (r/FortNiteBR), Downdetector, and X for other players reporting similar problems. A sudden spike in complaints from players in your region confirms a server-side or routing issue.
What You Can Do About Server-Side Issues
Unfortunately, not much — beyond waiting. Epic's infrastructure team is generally fast at resolving outages. In the meantime:
- Try a different server region to see if the issue is isolated to one data center
- Play a less populated mode (Creative, Save the World) while Battle Royale servers stabilize
- Use the time to run diagnostics on your own network so you're confident the issue isn't on your end
If you consistently experience packet loss to Epic's servers but not to other destinations, your ISP's routing to AWS may be the bottleneck. In this case, a VPN that routes through a different path can occasionally help — but VPNs also add latency, so this is a tradeoff. Test with and without to see which is better for your specific situation.
For a deeper understanding of packet loss, what the numbers mean, and how to interpret your test results, read our packet loss guide.