Cloudflare edge testPerformance, not guesswork
Fortnite connection check.
Test your connection, then follow the game-specific fixes and settings below.
Jump to fixes, settings & platform help ↓Fortnite: fix lag, high ping and packet loss
Check Fortnite ping spikes, packet loss and delayed building or editing, with separate advice for network lag and rendering stutter.
Find out what is actually lagging
Use the network display during actual play. Players snapping back or delayed edits with rising latency suggest a connection issue; a choppy camera with falling FPS may be rendering load. Compare Battle Royale, Creative or another experience carefully: different workloads and match servers can produce different results.
High ping or jitter
Actions arrive late, or delay fluctuates. Compare the in-game latency reading with your usual baseline.
Packet loss
Updates may be missing and movement can snap back. Look for a loss reading, not just a low average ping.
Low FPS or input delay
A choppy image or delayed controls can come from the device or display. Check an offline/local mode when available.
Settings worth checking in Fortnite
Menu names can change with patches, editions and platform. Use the controls available in your build; do not apply PC-only instructions to a console.
Net Debug Stats
From the lobby, open Settings → Game UI → Net Debug Stats, switch it On and Apply.
What it does: Shows network details during play. Record the display when the problem occurs.
Matchmaking region
Review your matchmaking region in Game settings. Use the lowest sensible latency for your location; compare Auto with the appropriate nearby region.
What it does: A distant party or region can increase latency. A larger download package does not shorten this route.
Subregion Preference
Where available, find Settings → Game → Language and Region → Subregion Preference. Compare a nearby preference with your baseline.
What it does: Epic notes this can increase queue times and affect match quality; it is not a guaranteed server lock.
Rendering options
On PC, lower demanding video options or compare an available performance-oriented rendering mode. Restart if the game asks.
What it does: Use this for FPS problems, not as a cure for ping or loss.
PC troubleshooting, step by step
- Pause Epic Launcher downloads, streaming and cloud uploads before testing. Take a quiet baseline, then play normally and note when latency changes.
- Epic's ping guidance describes pre-downloading High Resolution Textures through the launcher's Fortnite Options. Consider this only with adequate storage and download allowance; complete downloads before playing.
- If the picture stutters but Net Debug Stats stays stable, compare a lower graphics preset and a sustainable FPS cap. Keep the same region and connection for the comparison.
Console support and fixes
- Enable Net Debug Stats through the same Game UI settings where available. Compare the result with another match rather than treating a single spike as a diagnosis.
- Use Ethernet where the console supports it; a Nintendo setup may need a compatible dock or LAN adapter. If using Wi-Fi, compare close to the router before buying equipment.
- Pause game updates and other household uploads. Use a supported performance mode for smoother rendering, but judge network improvement using the network display rather than FPS.
Check the console connection itself
PS5: Settings → Network → Connection Status → Test Internet Connection. Xbox: Settings → General → Network settings → Test network speed & statistics. Other models can use different labels. These tests assess platform connectivity, not your game's exact match server.
Record errors and NAT warnings if joining or party chat fails. NAT changes are not a general cure for high ping. Avoid DMZ mode or opening ports without a diagnosed need and the platform's own guidance.
A controlled checklist for ping spikes and loss
- Record a baseline. Note your game mode, platform, time, connection type and the in-game reading. Run RaceMyNet outside a match. Keep two or three results rather than relying on one unusually good test.
- Remove local wireless uncertainty. Compare Ethernet directly to the main router where possible. A cable into a wireless mesh satellite may still use a wireless backhaul. If Ethernet is unavailable, compare close to the main router.
- Pause heavy traffic. Stop downloads, cloud backups and livestream uploads across the household for one comparison. If lag disappears only when traffic stops, investigate congestion and your router's supported queue-management options.
- Check the simple physical causes. Reseat Ethernet plugs, try a known-good cable or another router port, and restart network equipment once using its manufacturer's instructions. Do not factory-reset it as the first step.
- Change one thing and retest. Compare similar matches at your normal playing time. Keep improvements that repeat. A faster DNS service, a VPN or more Mbps is not a guaranteed reduction in game-server ping.
Prefer the game's own loss display for game traffic. If RaceMyNet reports an HTTPS fallback, request failures are not a direct measurement of the game's UDP packet loss.
If Fortnite still has connection problems
- Check Epic's service information linked from its support page before changing settings during an outage.
- Record the exact experience and region in a support report. A clean browser test can coexist with a poor route to a particular Fortnite match server.
If several games and devices struggle on a wired connection, give your ISP the times, results and affected services. If only this game or mode is affected, start with the publisher's support and service information below. Include the platform, region, timestamps and a short clip of the indicators. Share diagnostic logs privately through official support.
Why is Fortnite ping higher than my speed-test ping?
The tests contact different servers and may use different protocols. Fortnite also chooses a match server within a region. Compare repeated results and the in-game network display; do not expect both ping numbers to match.
Official guidance and further help
Menu instructions were checked against the publisher guidance below. General comparison steps are troubleshooting suggestions, not a promise of a particular ping or a guaranteed fix.
Use the test as a baseline. Verify the result in your game.
A browser test and a game match use different servers. Compare repeat measurements, in-game indicators and the same playing conditions before deciding whether a change helped.