Fortnite Servers Down: Massive Queues After Chapter 7 Patch
Servers Struggle to Cope with Sudden Traffic Spike
Fortnite players trying to jump into the game today were met with a frustrating surprise. Instead of dropping straight into the action, millions found themselves stuck staring at a countdown timer.
Epic Games unexpectedly deployed the highly anticipated Chapter 7 patch early this morning. While the update was supposed to usher in a brand-new era of gameplay, it instead brought the game’s infrastructure to its knees. Almost immediately after the patch went live, players began reporting massive login queues, connection timeouts, and severe matchmaking errors.
A Chaotic Morning for Gamers
The problems started around 6:00 AM Eastern Time. That is when the scheduled maintenance window was supposed to wrap up. Eager gamers who had pre-downloaded the massive update rushed to log in all at once. They were immediately greeted by digital lines that quickly stretched past the one-hour mark.
Even the lucky players who bypassed the initial loading screen could not do much. Matchmaking was virtually non-existent. Lobby screens threw up generic error codes—most notably Error Code 91 and constant check-for-update loops—instead of loading players into the Battle Bus.
Epic Games quickly acknowledged the situation. Taking to their official Fortnite Status account on X, the developers confirmed they were actively investigating the widespread stability issues. “We are investigating an issue that is preventing players from logging in and matchmaking,” the company posted. A few hours later, they temporarily disabled matchmaking entirely to ease the strain on their authentication servers.

Players React to the Outage
This unexpected downtime has left the community in a frenzy. Social media platforms like Reddit and TikTok are currently flooded with screenshots of ridiculous queue times. Some players reported seeing wait times as high as three hours. Others complained about waiting patiently, getting to the front of the line, and then having the game crash. That crash sent them right back to the end of the queue.
“I woke up early just to check out the new map,” said one player on a community forum. “I’ve been sitting in this queue for ninety minutes, and it just reset. It’s incredibly frustrating.”
These kinds of launch-day hiccups are not entirely new for Epic Games, but the scale of today’s disruption is particularly severe. Chapter transitions always draw massive crowds. However, because this specific patch dropped with very little prior warning, the sudden, massive influx of concurrent users seems to have caught Epic’s server architecture completely off guard.
The hype surrounding Chapter 7 explains the heavy traffic. Rumors of a revamped map, brand-new weapon mechanics, and highly anticipated crossover skins had players incredibly eager to log in. When the servers finally opened, the sheer volume of traffic essentially acted as an accidental overload on Epic’s login portals.
What to Do While You Wait
If you are trying to play right now, here are a few tips to keep in mind:
- Do not close your game: While it is tempting to restart the app when the timer stops moving, doing so will lose your spot. You will end up at the very back of a line that is now hundreds of thousands of players deep.
- Avoid rapid lobby changes: Do not try to join friends’ lobbies repeatedly. This action sends rapid requests to the matchmaking system, which can trigger automatic temporary lockouts on your account.
- Check official channels: Monitor official status pages rather than repeatedly restarting your console or PC, as the issue lies entirely on Epic’s backend.
As of this writing, Epic Games has not provided an exact timeline for when the servers will return to normal. Engineers are reportedly working on scaling up server capacity and patching the login gateway, but progress has been slow. For now, Fortnite fans will just have to practice some patience. We will continue to monitor the situation and update this article as soon as Epic shares a breakthrough or if the server status begins to stabilize.