Call of Duty WW2 Error Code 103295: "connectivity issues" strike on release day
Update: connectivity problems have been resolved, according to Activision.
Original story: Call of Duty: WW2 multiplayer servers are having a rough time coping with a couple of million players. Nobody's surprised, right?
Call of Duty: WW2 soft-launched today, rolling out in New Zealand and Australia before unlocking in Europe and the UK and finally landing on the US just about an hour ago.
The Call of Duty: WW2 multiplayer servers are live, truly - but they went down almost as soon as the Americans came on the scen, with players reporting Error Code 103295, which prevents them accessing online services.
There's no fix or solution, unfortunately. Activision Support's official word is that there are "connectivity issues", and it is investigating.
The problem seems to affect all platforms and even other Call of Duty games, so it looks like the issue is something on Activision's end rather than a platform holder or Sledgehammer Games.
Given the timing, we naturally suspect the problem is player volume - everyone in the US who stayed up till midnight ET to start playing, along with all the Europeans waking up and starting their day with it. Call of Duty regularly shifts about 30 million copies each year, which is five times what most bestselling titles can expect, and a significant number of these players pre-order and dive in as soon as the game unlocks.
Since hype has been pretty damn high (Call of Duty: WW2 reviews are looking great), we anticipated a few teething troubles. Let's keep our fingers crossed things settle down and Activision and Sledgehammer Games can sort out Call of Duty: WW2's issues before its community managers resign in despair over the flood of angry tweets and messages.
We'll keep you updated if we hear anything further from Activision. In the meantime, be sure you've got the 9GB day one Call of Duty WW2 patch.