Fortnite: Server apparently overloaded after update to v25.10

2023-06-20 18:12:57
FORTNITE Jun 20, 2023 at 8:12 p.m

First Fortnite was not playable due to maintenance work, now the servers are apparently on their knees due to the ensuing onslaught. There are also problems with the “Ranked” mode.

June 20th is a black day for Fortnite fans. First the popular shooter was due Maintenance work Temporarily unavailable, now a rush on the servers after the update to version v25.10 is evident the game lame. Players worldwide are reporting connection problems.

After the update there are also restrictions. The ranked modes for Battle Royale & Null Build have been temporarily disabled as the development team is still investigating reported issues.

It is unclear when the disruption will be resolved. You can keep yourself up to date in our malfunction reporter.

Current Fortnite disruption map

This disruption map was last updated on June 20, 2023 at 20:34. A more recent version can be found in our Glitches for Fortnite. We will also try to help you – as far as possible – with troubleshooting.

Affected cities and regions

Berlin Hamburg Frankfurt am Main Cologne

Most common disorders

Other issues (2.06%) Console issues (13.91%) PC issues (10.86%) Playstation issues (20.30%) Xbox issues (4.81%) Gaming issues (4, 91%) Download (1.75%) Login (36.89%) Store (1.24%) Website (1.00%) Problems with Epic Games (2.27%) Report fault

Fault indicator from netzwelt.de

We continuously measure the availability of the Fortnite servers and services and show you any problems or disruptions. You can find the current one here Malfunction Status for Fortnite, support addresses and reports from the manufacturer about this problem. There you can also see whether the disruption is a local or national problem.

You can always see current faults and problems in our fault indicator. There we list the most important Internet providers, network providers, online games and streaming services for you. You can also check with ours whether there is a problem with your own line Speedtest to test.