Fortnite UPDATE – Battle Royale patch deployed after massive server outage

gamers have today been given a Battle Royale update after a huge server outage hit the popular PS4, Xbox One and PC game yesterday.

Fortnite servers were offline for around 14 hours on Thursday as Battle Royale fans around the world were left unable to play online.

Fortnite originally went down to prepare for the rollout patch V.2.3.0 which brought with it bug fixes, Battle Royale changes and finished up a event.

However, the Fortnite server downtime went on for much longer than anticipated.

Epic Games said during the downtime the Fortnite database ended up going into a “bad state”.

They took the decision to restore it from backup, but the first attempt failed – so they had to try and do it a second time.

At around 11pm GMT on Thursday, Fortnite finally came back online – much to the delight of Battle Royale fans.

And now today Epic Games have pushed out a new Fortnite patch, but it’s only for PC gamers.

The Fortnite update resolves issues that had been affecting AZERTY/FR gaming keyboards.

They tweeted: “We have just deployed this morning a PC-only patch V.2.3.1 which resolves a key binding issue for AZERTY/FR keyboards.” 

Epic Games also revealed that they are working to fix some bugs that made it through with the latest Fortnite patch.

Known bugs that the Fortnite team are trying to address include building selector problems, reloading issues and aiming down sights problems.

The official Fortnite Twitter account said they are working to fix these problems right now.

They tweeted: “Whoops! Looks like some bugs made it through into this weeks patch. 

“That’s not good, but we’ve heard you and are working hard to resolve these issues now.”

When Fortnite went down yesterday, Epic Games published a detailed post explaining why it was offline for so long.

In a forum post they revealed: “During our downtime to upgrade to 2.3, we were performing recommended tasks to resolve a lingering database issue.

“Those tasks ended up causing the database to go into a bad state.

“After significant consideration, we decided our best option was to restore from a backup at the moment we took the servers down for the patch.

“Our first restore failed (due to issues unrelated with the quality of the backup) and we’re working on a second attempt at the restore.”