Fortnite server status: How long is Fortnite downtime? Is there an update today? What time

Fortnite servers have been switched off this morning as matchmaking services receive maintenance work on Xbox One, PlayStation 4 and PC. 

Epic Games announced they would be disabling matchmaking services at 9am this morning, stopping players from logging on for the third morning in a row.

The latest update v4.3 has evidently caused several problems with the game’s infrastructure, with Epic Games restricting gamete for players. 

It is currently unknown when matchmaking services will be available, which are still currently unavailable. 

Players have waited for more than three hours for matchmaking services to resume as usual, but Epic Games are yet to announce when the services will be back up.

How long is Fortnite downtime?

Fortnite matchmaking services are currently under maintenance this morning, as Epic Games fix a number of bugs and issues in the game this morning. 

According to the Epic Games status website, all other game services remain operational, including party and voice chat, store, leaderboards and websites.

Epic Games tweeted this morning: “Matchmaking is currently disabled as we undergo service maintenance. Stay updated here - http://status.epicgames.com”

They also included a link to the Reddit site to explain how their maintenance process works. 

The Fortnite servers have suffered three days in a row of technical difficulties, stopping players from logging in for several hours at a time. 

On Wednesday Epic Games added a new update v4.3 which included vehicles to the game. 

Players can now hop into shopping carts and push themselves around the map for faster - though more difficult - travel. 

Other updates included VOIP chat for PC players and several bug fixes. 

Fortnite was then shut down on Thursday morning as Epic Games fixed several bug issues that had arisen from the new update, closing the game off to players for three hours. 

Epic Games announced that they had “identified and are actively looking into a situation where Battle Royale match wins for console players are not reporting correctly.”

As of Friday, this issue appears to have been fixed. 

Fortnite Week 5 challenges were also delayed this week, released on Thursday instead of the usual Tuesday, as the developers fixed a slew of issues. 

The latest server downtime has not been given an end date, with Epic Games remaining quiet on when matchmaking will resume as usual. 

In a post online on Reddit, Epic Games said: “We wanted to give you a heads up that we're planning another maintenance window tomorrow, June 1, at 4 AM ET (8 AM UTC).

“During this time, matchmaking will be unavailable for Fortnite Battle Royale. This will be the third day in a row that we've had a scheduled maintenance window. I can explain.

“We mentioned back in February scaling the backend MongoDB database that we use for much of our account and matchmaking system has been a challenge.

“We've made a ton of progress and our database has never been in a better place than it is right now, but we knew that it wasn't the right fit to handle our continued growth and new types of LTMs.

“The Playground LTM v1, for example, has a maximum of 4 players per game which means we'll need a lot more game instances and matchmaking sessions to support that mode than we do a mode like Battle Royale that can support up to 100 players per instance.”

Epic Games added: “Over the last couple of days we've been working on rolling out a brand new, horizontally scalable, session tracking service to manage sessions for matchmaking.

“Despite extensive testing over the last few weeks, we ran into some problems when we attempted to put it into production.

“First, we ran into an issue with the way the system handled the case of many thousands of empty game servers, just waiting for people to drop at Tilted, that caused a lot more data to be returned by queries to the service than we expected. 

“We solved that problem and tried to deploy again this morning, and while performance looked good we ran into a problem with the way our dedicated server auto-scaling systems interacted with the session tracker that required us to revert to the previous system again.”