📰 News 2026-11-19 · GTA VI News editorial team · GameSpot / jeuxvideo.com / Axios / The Guardian / Mashable

PSN went down five hours before GTA VI unlocked in Europe — and a licence check was enough to block a paid copy

PSN went down five hours before GTA VI unlocked in Europe — and a licence check was enough to block a paid copy
TL;DR

PlayStation Network authentication failed across several regions from roughly 18:00 UTC on 18 November 2026 — five hours before GTA VI unlocked in mainland Europe at 23:00 UTC — and a PS5 holding the full 212 GB download could not verify its licence, so the game would not start.

PlayStation Network stopped authenticating players across several regions on the evening of 18 November 2026, roughly five hours before GTA VI unlocked in mainland Europe at 23:00 UTC. The game was not the problem. The console was: with PSN out of reach, a PS5 that already held the full 212 GB download could not check the licence attached to it, so the title refused to start. That failure mode belongs to Sony's authentication layer, not to Rockstar's servers.

The window, reconstructed in UTC

The first traces came from monitoring rather than from Sony. jeuxvideo.com reported that incident curves on services such as Downdetector started climbing at 19:00 CET, which is 18:00 UTC, alongside a wave of error messages on social media. The site published its account at 20:00 CET, one hour into the incident, at a moment when the PlayStation status page still described the network as healthy.

Wire coverage followed within two hours. Axios framed it at 19:59 UTC as a "major outage hours before GTA VI launch", and The Guardian at 20:37 UTC as "widespread network problems hours before release of GTA VI". Yahoo Tech's version at 21:57 UTC spoke of the network being down "for thousands". None of those dispatches named a cause, and Chinese outlet 3DM, writing at 21:51 UTC, stated explicitly that the cause had not been confirmed.

GameSpot's account, published at 20:55 UTC by Eddie Makuch, is the most specific and the most cautious. It reported that PSN had suffered "a temporary outage for launching games specifically" and that this "has since been fixed", citing a post by @charlieINTEL. The same article noted that Sony's PlayStation Status website said everything was fine — which is a statement about the dashboard, not about the players.

Why a single-player game needed Sony's servers

GTA VI's campaign is a single-player mode, which is why the outage looks strange from the outside: players were not waiting for a matchmaking queue, they were waiting for a console to authorise a file already on its disk. The dependency sits at console level. A digital purchase is a licence, and the PS5 checks that licence against PSN before it hands over the executable; jeuxvideo.com describes the result as a padlock that persists even with all 212 GB sitting on the SSD.

Physical copies were not a clean escape either. Sony's system software 26.07-14.23.00, released on 17 November and mandatory before playing, weighs up to 1.27 GB according to jeuxvideo.com; without it, a disc-based copy would not launch either. The same outlet argues, as analysis rather than as confirmed fact, that the update was pushed to close a jailbreak route before launch — which turned a security patch into a compulsory download landing in the same evening as the game itself.

The load this site flagged the day before

On 18 November this site reported that firmware 26.07-14.23.00 was 1.267 GB and mandatory from day one, and noted the risk in plain terms: anyone who waited until unlock night would be asking Sony's servers for that file at the exact hour the game went live. The outage did not need a dramatic explanation to happen. The arithmetic is enough: 1.267 GB multiplied by one million consoles is 1.267 petabytes, and by two million consoles 2.534 petabytes, before a single byte of GTA VI moves.

For scale, New Zealand's Chorus expected about 5.6 petabytes of pre-load traffic on its own network from roughly 140,000 buyers, as this site reported on 18 November. Europe's unlock at 23:00 UTC put the continent's mandatory firmware download, its last-minute 212 GB pre-loads and its first logins into a single hour, which is precisely the overlap jeuxvideo.com identifies as the bottleneck.

What is confirmed, and what is not

Confirmed: the incident happened, it was reported independently by Axios, The Guardian, GameSpot, Yahoo Tech, jeuxvideo.com and 3DM within three hours, and it was concentrated in the hours before the European unlock. Confirmed too: the launch-games fault was reported fixed before 23:00 UTC, 2 hours 05 minutes ahead of the European unlock, so the evidence available does not show Europe's midnight being missed at scale.

Not confirmed: any cause, any figure for affected players, and any Sony statement. jeuxvideo.com quotes a BetOnline market pricing an 83% chance of console servers collapsing around midnight; that is a betting price, not a measurement, and it should be read as such. Mashable, at 07:03 UTC on 19 November, was still collecting players reporting problems — scattered reports on launch morning, without a second confirmed outage behind them.

The Xbox contrast, and what still lies ahead

The asymmetry was immediate. jeuxvideo.com reports that Microsoft's servers absorbed the load and that the New Zealand region switch worked on Xbox Series X|S from 12:00 Paris time on 18 November — twelve hours of early access — while PS5 owners could not use the same trick, since Sony binds an account to a single region. That difference is structural and predates the outage.

Later regions still face their own peak. The United States unlocks at midnight Eastern, 05:00 UTC on 19 November, and the West Coast at 08:00 UTC, both after the fault was reported fixed but with a far larger share of buyers logging in at once. Anyone installing from disc today should let the 1.267 GB firmware complete before the unlock hour rather than during it.

See also

📚 Sources

← Back to the news