Update: The issues described here have now been resolved, see the information at the bottom of the article for more details.
It would appear that users of the older "fat" PS3 are experiencing connection issues when trying to sign into the Playstation Network. Currently it seems that only the older PS3 systems are affected and that owners of the newer "slim" models have escaped the problem, at least for now.
Outages are bound to happen from time to time, but what's frustrating and annoying gamers is that they can't access their trophies, dynamic themes, multiplayer games or paid for content from the Playstation Store. Worse still and this is what's really irking gamers, is that they can't even play offline, single player games. Their systems are in effect expensive bricks for the time being.
According to Kotaku developers are also experiencing problems. Some are saying that their debuging units, those systems that are used to create PS3 titles are caught in a never ending cycling of rebooting due to an endlessly-looping error message. This means that developers are loosing valuable development time.
Sony have been forced to recognise this issue early on as it's affecting so many machines, including those of the developers who actually make content for the platform and have said via the PS blog, "We are currently working to restore service as a matter of priority and will update with further information as necessary."
![[ Playstation 3 Fat Console Image ]](http://images.bit-cast.net/gaming/2010/3/image_ps3fatconsole.jpg)
Some are speculating that the sudden demise of PS3s all over the world has come about because of a problem with the PS3s internal clock. This is pure speculation at this time, but a member of the NeoGaf forums says the problem is to do with the way the PS3 is trying to jump from February to March.
According to forum member 'iammeiam', "What's apparently [gone wrong], as speculation goes, is when the internal GMT-tracking rolls over to 3/1. It's either not rolling, or rolling to 2/29, at which point a system tries to add/subtract from 2/29, which it can't do because the front-end calendar doesn't have a 2/29/2010, and [it all] explodes. Seemed to happen around 4PM PDT, which I think is 12AM GMT, so.
And the PS3 launched in 2006; it's hit 4 2/28s so far. 2007 and 2009 were odd-numbered years; 2008 was an even, and a leap year. 2010 is the first even non-leap-year the system's been around for. If some sort of base-level math is choking on itself, it may have ruled out the odd 2007 and 2009 successfully, but is convinced the even 2010 is a leap year (this part I'm less sure of, but is why leap year could theoretically come into play at some point.)"
If this is the case then the system may right it's self tomorrow as has happened to other products in the past, but for now it's probably a wise idea to avoid turning your PS3 on for today, just in case it's something worse than a calendar malfunction.
Update
Sony have released an update to the situation which confirms that it is indeed a glitch in the consoles clock. The company also confirmed that PS3 Slim models are not affected by the bug. Sony have found the following glitches (this is lifted off the PS blog):
- The date of the PS3 system may be re-set to Jan 1, 2000.
- When the user tries to sign in to the PlayStation Network, the following message appears on the screen; "An error has occurred. You have been signed out of PlayStation Network (8001050F)".
- When the user tries to launch a game, the following error message appears on the screen and the trophy data may disappear; "Failed to install trophies. Please exit your game."
- When the user tries to set the time and date of the system via the Internet, the following message appears on the screen; "The current date and time could not be obtained. (8001050F)"
- Users are not able to play back certain rental video downloaded from the PlayStation Store before the expiration date.
As previously suggested Sony advise all those with a pre slim model to not turn their systems on as it could prevent certain data from being restored once a fix is rolled out. Sony say they are doing their best to resolve the problem and hope it will all be sorted within the next 24 hours. They also issued an apology for the inconvenience and dare I say, distress the fault has caused to gamers.
Update - Issue Resolved
The issues that the pre Slim, Playstation 3 consoles were experiencing over the last 24 hours appear to have corrected them selves as predicted. The Playstation Blog has confirmed that the internal clock thought 2010 was a leap year and added another day to the end of February, which caused things to be out of sync with the Playstation Network. After the 29th day, which was actually March 1st the system has put its self right again.
If your clock is still wrong you can change it manually and Sony say it is safe to turn your systems back on and get back in the game, everything should work and sync up as normal form now it. Although the Slim models were not caught up in the problem, those systems have not yet experienced a leap year, "does a problem lay dormant in their systems?" is a question that some might be asking after recent events. In any case, Sony are aware of the problem with the 'fat' systems and can work to push an update out for the 'Slim' systems, should they require it.