Fortnite’s servers have vanished for 12 hours straight, leaving millions of players stranded-and Epic Games’ latest blunder has them fuming.
While a hotfix like this usually has a 4-hour downtime window, it’s been over 6 hours since the servers went down. They are still under maintenance at the time of writing, and frankly, that’s a bit worrying. As players were getting jumpy, dataminers uncovered the reason behind the delay, and it seemingly looks like you will have to wait for around 12-15 hours until you can become Superman in Fortnite once again.
Lengthy Downtime Inbound As Epic Assigns Wrong Patch Name to Latest Fortnite Update
Fortnite players are voicing concern after a roughly 12-hour outage, sparked by Epic accidentally labeling the latest patch with the wrong name, adding to ongoing frustration with server downtime.
According to the latest round of leaks on social media, Fortnite players may need to wait even longer than usual until Epic’s servers are back online and they are able to play the Battle Royale title again. As per dataminers, “Epic pushed today’s update with a build number that is lower than 36.10. This means it is impossible to end downtime until they build a new version.”
Its effect on the new update, you ask? Well, the last time a new build was needed to rectify such an error, it took Epic nearly 15 hours to correct it and push out an update.
the version itself did go up but the changelist went down. that means that the build is actually older than the version we had before. changelists are always supposed to go up with every update and not down. which means some of the changes from the last update are missing pic.twitter.com/fa9eaFFVD2
— Osirion (@osirion_gg) July 15, 2025
After some more digging, dataminers like Osirion found out that the latest v36.20 patch was developed before the July 9 hotfix in a changelist. This means the new version will need to be modified once more until Epic can push a build across and it’s set live.
As of now, Epic has also posted on X on their Fortnite Status page about the downtime as they wrote, “Hey everyone, we’re extending downtime while we work to resolve an issue discovered during offline checks. We’ll do our best to get Fortnite servers online ASAP. Keep an eye on this thread for any future updates.”
What caused the wrong patch name in Fortnite v36.20
Fortnite v36.20’s extended downtime stemmed from Epic Games deploying a build with an incorrect version number lower than the prior v36.10 patch. This error prevented servers from transitioning out of maintenance until a new build was created. Dataminers noted the patch originated from a changelist predating a July 9, 2025 hotfix, requiring further modifications before rollout.
Deployment Error Details
Epic pushed the update with a mismatched build number, halting the downtime process automatically. Similar past incidents took up to 15 hours to resolve by rebuilding and redeploying. No official Epic statement detailed the root cause beyond this sequencing fumble.
Player Impact
The mishap fueled 12+ hour outages, sparking frustration over repeated update delays. Patch notes later focused on bug fixes like UI glitches and weapon perks, unrelated to the deployment issue. Epic resolved it without altering v36.20 content like new skins or maps.
Why was v36.20 developed before the July 9 hotfix
Fortnite v36.20 was branched from a development changelist created before Epic Games released the July 9, 2025 hotfix. This sequencing occurred because Epic prepared the major mid-season patch during their annual summer break content pause, ahead of v36.10’s rollout on June 18. The hotfix addressed urgent post-v36.10 bugs, but integrating it required modifying the existing v36.20 build later.
Development Timeline
Chapter 6 Season 3 launched June 8, 2025, with v36.10 as the last update before Epic’s summer break. v36.20 was prepped as the penultimate patch before Season 4 on August 7, setting competitive changes like new POIs and mythics. Dataminers confirmed the changelist predated the hotfix, forcing a rebuild during deployment.
Deployment Consequences
Pushing the outdated build caused the lower version number error, extending downtime to 12+ hours. Epic resolved it by creating a new version incorporating the hotfix without altering core content like buffs or new weapons. No official Epic explanation detailed the branching decision beyond this workflow overlap.
