If Fortnite keeps looping on “Connecting,” check whether the game is actually blocked locally or just waiting on services.
A Fortnite connecting loop often clears after a simple restart if the cause is temporary service congestion. If it happens repeatedly, use a clean order: check Epic status, restart the game and device, test your network, then verify or repair the client on PC. Only after you know the loop is local should you spend time on deeper fixes.
When does the connecting loop happen?
The exact stage of the loop determines whether you should suspect services, account sign-in or client state.
4 easy things to try, in order
Use the following order so you do not waste time on a reinstall during a temporary outage.
Check service status and wait out obvious outages
Open the Epic status page and see whether Fortnite login or matchmaking is degraded. If the service is unstable, repeated relaunches usually do not help. Wait for the incident to clear before making local changes.
This prevents unnecessary troubleshooting during a live outage.
Restart Fortnite, then the device and router if needed
Fully close Fortnite. Relaunch it once. If the connecting loop returns, restart the device. If other apps or games also show network trouble, reboot the router and reconnect.
Use a calm restart sequence rather than endless rapid retries.
Use platform-safe client repair
On PC, verify Fortnite from the Epic Games Launcher. On console, power-cycle the system and retest before taking larger steps. If the problem is isolated to one device, that is useful evidence even if other users are online.
Do not delete saves or linked accounts to fix a connecting screen.
Document the loop pattern if it persists
Note whether the issue occurs before the lobby, after a login prompt, or only when your network changes. That pattern helps support separate a local login loop from broader service issues.
A precise timeline matters more than a vague “it gets stuck.”
A connecting loop is usually not solved by changing account links or deleting cloud data. Those actions add risk without addressing the common causes.
What the loop pattern tells you
These comparisons help decide whether you are looking at a service event or a local issue.
The loop disappears after the service incident ends.
That strongly suggests a temporary outage rather than damaged local files.
One device loops, another device on the same account does not.
That points to the local client or device state.
One network works but another does not.
Investigate the network path, DNS or local firewall/router conditions.
Verification changes the behavior.
That makes local file integrity more likely than a pure server issue.
Need help with a persistent connecting loop?
Include your platform, whether friends could log in, what the Epic status page showed, and whether verification or a reboot changed anything.
Epic service status ↗Quick FAQs
Is this always a server problem?
No. Some connecting loops are local to one device, network or client install.
Should I reinstall immediately?
Usually not. Status, restart and verification checks should come first.
Can my router cause a connecting loop?
Yes, especially if only your network shows the problem.
Do I need to clear cache on console?
A restart or full power cycle is a reasonable early console step.
What should I tell support?
Explain where the loop occurs, which devices were tested, and whether service status was normal.
Official support sources
Original Walker Bex article. Reviewed October 12, 2026. Use current official support instructions if menus or services change.