Is your PS3 borked this morning? [update@23:53]
Widespread reports are suggesting that many non-Slim PS3 owners are suffering at the hands of various DNS errors relating to PSN on their consoles. The issue stems from a server-side bug that has hit all original PS3 units (the fat ones), rendering them useless for the time being. This appears to be an issue related to a DNS server that handles Trophies.
The symptoms from a user perspective appear to be when launching into a game, or trying to access the Playstation Store. The system stalls for a moment and then crashes.
The Sony Twitter account (EU version) has confirmed this issue does not affect slim PS3 units at all. The related error code has been identified as 8001050F. Some are suggesting this is a millenium bug style issue that affects the FAT32 formatted original-PS3 units.
It also appears that fat-PS3 owners are reporting data corruption from this bug, with their date reverting back to 31/12/1999. Given this is a corrupting of data issue, we would recommend not booting up your PS3 for the time being.
SCEE have commented;
We are aware that some users are experiencing a network connection failure when signing on to PlayStation Network. Those of you with the newer, “slim” PS3s (120GB/250GB) seem to be unaffected.
We are currently working to restore service as a matter of priority and will update with further information as necessary. We apologise for the inconvenience and appreciate your understanding and continued support.
Keep an eye here and on the PS Blog for updates. As we say, don’t bother booting up the PS3 just in case it causes data corruption to files on the hard drive.
[b]Update@12:01[/b] Keep an eye on this thread on boards.ie. Easier to follow the conversation, as the official forums have gone into meltdown after being reported on CNN in America.
[b]Update@14:02[/b] 10 hours after the original tweet from Sony in the US and we’ve nothing new to give. So let’s laugh…
[b]Update@15:17[/b] These are the units confirmed to be affected:
CECHA01 – affected
CECHC04 – affected
CECHE01 – affected
CECHG01 – affected
CECHG04 – affected
CECHH01 – affected
CECHK01 – affected
CECHK04 – affected
CECHL01 – not affected
CECHL04 – not affected
CECHP01 – not affected
It also appears the issue could be the internal clocks thinking today is the last day of February, rather then the first of March, thus keeping everything nicely out of sync and screwing everything up. Whether or not this will be fixed today remains to be seen but Sony’s lack of communication suggests they’ll rest on their laurels and just let it fix itself tomorrow. However, there is no way of knowing if data corruption is permanent (i.e. if saved game files or even HD-installed content will be ruined).
[b]Update@23:51[/b] Aaaand we’re done. The issue has been resolved, and appears our assessment above of it being the internal clocks on PS3′s not syncing with the time on PSN being correct. No word on whether affected (and switched on) units have any detrimental effects as of yet, but I doubt it’ll take too long to find that out.
Social comments and analytics for this post…
This post was mentioned on Twitter by kev_d: RT @shoryuken_ie: New on shoryuken – Is your PS3 borked this morning? http://is.gd/9rBn4...
this is ridiculous
It was fine last night but yeah better not use it for a while, shame as getting into Heavy Rain at the moment.
If this drags on and really is causing data corruption, it could cause massive, massive problems for Sony.
This is insane, some serious head scratching is going down over at Sony HQ right bout now.
Quite borked.
80GB 12 months old.
i only went and turned mine on forgetting it auto signed in, I leapt to pull out the lan cable, i hope i got there in time.
Gah, was gna have another killzone 2 session tonight!
It won't matter if it signed in or not. My PS3 isn't connected to a network, but I now have a number of games that can't start up due to this error.
The article is incorrect. It is NOT a server-side bug.
Your PS3 isn't connected to anything and your still getting the error's?Holy shit its Y2K. Sony how you gna fix peoples PS3's who don't have the web? Most be an internal clock thing.
Does seem a bit of a coincidence that it's the leap year day (if it was a leap year). could the ps3 not be aware it is not a leap year lol