Use ipconfig /flushdns only when a stale Windows DNS entry is plausible.
Close Fortnite and the Epic Games Launcher, open Windows Command Prompt, enter ipconfig /flushdns, then reopen the Launcher and test the connection. The command clears locally cached domain lookups; it does not reset your account or delete game progress. If the issue is server downtime, unstable Wi-Fi or packet loss during a match, DNS flushing alone is unlikely to fix it.
What problem led you to flush DNS?
The command is relevant for certain connection failures, not every kind of lag.
4 simple checks, in the right order
Follow the checks in order, then stop as soon as the issue is resolved. Every change should be easy to undo.
Check Epic status and close affected apps
Before changing Windows settings, verify whether Epic Games services are working. Then exit Fortnite and close the Epic Games Launcher from the system tray so they can make fresh connections when reopened. A provider outage cannot be repaired with a Windows DNS command.
Do this first so you can tell whether the result is actually from your PC.
Run the Windows DNS-cache command
Open Start, search Command Prompt and open it. Type ipconfig /flushdns and press Enter. Windows should report that its DNS Resolver Cache was successfully flushed. This clears remembered name lookups; it does not change Fortnite graphics, remove your login or edit router configuration.
Command: ipconfig /flushdns — this is a Windows networking maintenance command.
Reopen the Launcher and test one connection
Start Epic Games Launcher again and attempt the specific action that failed. If it now succeeds, the cached lookup may have contributed. If the failure persists, collect the exact error message and check proxy/VPN settings, system time and the local network.
Avoid stacking multiple network resets at once; test each change.
If it is actually ping or packet loss, use a different path
If Fortnite launches normally but match latency spikes, focus on your connection quality, overloaded uploads and the selected matchmaking region. Epic explains that routing and subregion choice affect ping. DNS flushing does not change the real-time server route of an active match.
DNS resolution and match packet delivery are different layers of networking.
Epic lists additional Windows commands in its broader troubleshooting flow, but those can interrupt networking. Start with the simple DNS cache command and only escalate when necessary.
If the first four checks do not help
These symptom-specific notes help you avoid unnecessary fixes.
Flush succeeds but Launcher still says offline.
Try official launcher cache/service checks and compare a different network.
DNS command reports an error.
Check that you typed it correctly and are using Windows Command Prompt.
Only Fortnite lags, webpages work.
That points more toward gameplay routing or packet loss than name resolution.
Every device on Wi-Fi has connection trouble.
Investigate the router or ISP rather than one Windows cache.
Still seeing the problem?
Write down the platform, exact symptom and which checks changed the result. Send those details with a screenshot to official support.
Epic Games Support ↗Quick FAQs
What is the exact flush DNS command?
On Windows, ipconfig /flushdns.
Is the command safe for my Fortnite account?
It clears a local network cache and does not alter Epic purchases or progress.
Will DNS flushing reduce ping?
Usually not. Ping during a match depends on routing and connection quality.
Do I have to restart Windows?
For this single command, often not; reopen the affected app and test first.
Does this work on consoles?
The Windows command does not run on Xbox, PlayStation or Switch.
Official support sources
- Epic — Flush Windows DNS cache
- Epic — Connection and launcher troubleshooting
- Epic — How network latency works
- Epic — Live service status
Original Walker Bex troubleshooting guide. Reviewed October 15, 2026. Menus and live issues may change; verify with the linked official support sources.