Krafton has confirmed the PUBG Maintenance schedule for today’s PC server downtime and the launch of update 16.1 on consoles.
PUBG servers are down tonight and on February 24 for several hours, with different schedules in place for PC and consoles players.
The good news is that PC servers will be offline before PS4 and Xbox One, meaning you can switch between types if you’re desperate to avoid downtime.
PUBG | A Lucky Day Cinematic Trailer
BridTV
8249
PUBG | A Lucky Day Cinematic Trailer
https://ift.tt/4fMtylK
951970
951970
center
13872
PUBG Maintenance Schedule For Console And PC
Krafton has confirmed that there will be two running maintenance periods on Console and PC. PC downtime starts tonight at 12:30am GMT on February 23 and will last a total of four hours. This means that PC maintenance should end by 4:30am GMT.
Console downtime: The PUBG Maintenance schedule for PS4 and Xbox One starts at 4am GMT on February 24 and is scheduled to last longer. This is due to it including the new version of the game – PUBG update 16.1 on PS4 and Xbox One. PUBG maintenance on consoles will last seven hours and will end at around 11am GMT on the same day.
The official post from Krafton explains: “Live servers will undergo maintenance for approximately 7 hours on Feb 23th, 8:00pm PST / Feb 24th, 5:00am CET / Feb 24th, 1:00pm KST.”
Update 16.1 is already available on PC platforms, meaning this new patch will bring versions back in line.
The PUBG Maintenance Console Schedule for February 24 is as follows:
PST: February 23, 2022, 8 PM – February 24, 2022, 3 AM
CET: February 24, 2022, 5 AM – 12 PM
KST: February 24, 2022, 1 PM – 8 PM
Krafton has confirmed that this week’s new PUBG update for consoles will now make Squad-FPP for Ranked mode available alongside the default Squad-TPP queue in NA and EU regions. It should also be noted that Ranked Play restarts with this update, with new rewards unlocking for Season 16.
In other news, Elden Ring preload time, download size and PC Steam requirements
from WordPress https://ift.tt/dAukml3
via IFTTT
No comments:
Post a Comment