PlayStation Network down, so are lots of PS3s

[Mouldingo]

It's unclear exactly what's going on at the moment, but it appears that the PlayStation Network is down and causing a whole host of related problems for PS3 systems, including 8001050F error codes, game crashes, corrupted trophy info, and even the complete inability to launch certain titles. There's no ETA on when things will get back to normal -- looks like it's gonna be a Blu-ray kind of evening for PS3 owners out there.

Update: Sony's tweeted that it's "looking into it," and our boys at Joy say that owners of original PS3s are seeing their clocks reset and even data loss in some cases. We'll keep you updated.

http://www.engadget.com/2010/02/28/playstation-network-down-so-are-lots-of-ps3s/?s=t5

[anya618]

Sony has confirmed that Slim units are unaffected

[indie boi]

Was out the whole day and when I finally got back home, I fired up my PS3. I only found out about the problem AFTER I've turned it off. Good thing nothing happened to my unit.

[techdude]

Maybe those PS3 are expecting February 29 instead of March 1.   

[Mouldingo]

PS3 issues apparently resolved, game on


Rejoice: PS3s across the land are now once again playable. That's the word according to our friends at Joystiq, who say that the clock issue affecting "fat" PS3s has been somehow resolved and games are once again working correctly. We're not sure if this means Sony's fixed something on the network side or if the internal clock just ran past a certain time, but at least our long nightmare is seemingly over. Hit up Joy for a quick Q/A on the whole situation, including a way to potentially save lost trophy data.

http://www.joystiq.com/2010/03/01/ps3-clock-bug-apparently-squashed-games-are-playable/

[Galactus]

Bug plagues PlayStation 3, Sony warns of data loss
(philstar.com) Updated March 02, 2010 09:57 AM 

NEW YORK (AP) — Sony Corp. said a glitch has knocked PlayStation 3 users off the game console's online network, and the company warned that data loss could occur if gamers continued using the machines.

Sony said in a blog post Monday that the problem was likely caused by a bug in the clock functionality incorporated in the system, reminiscent of the Y2K bug a decade ago. The problem is affecting older PlayStation 3 models, but not the newest slim version that went on sale in September.

The company urged customers not to use the older PlayStation 3 systems until the problem is resolved, warning that doing so could cause errors and make it impossible to record gaming achievements and restore some data.

Sony would not say how many users were affected by the problem, which comes just as PlayStation 3 sales are picking up. According to the NPD Group, 276,900 units of the system sold in January in the United States, up from 203,200 a year earlier. In December 2009, meanwhile, nearly 1.4 million PlayStation 3 consoles were sold in the U.S.

Errors that PS3 users started seeing Sunday include the date of the systems being reset to Jan. 1, 2000.

The problem was reminiscent of the Y2K bug, in which programming shortcuts caused some computers to malfunction in the new millennium because they interpreted "00" as the year 1900. Although a mass computer meltdown didn't result, as some people had feared, hiccups were reported around the world.

Other problems resulting from the Sony glitch can include an error message saying the user has been logged out of the online game network. Users' game trophies — their accomplishments — can also disappear.

Sony is not the first to deal with a Y2K-like bug years after 2000. At the end of 2008, thousands of Microsoft Corp.'s Zune media players unexpectedly crashed, prompting references to "Y2K for Zunes." Microsoft said at the time that the failures, which affected only the 30-gigabyte Zune models, were caused by a problem with their internal clock.

Sony said Monday that it hopes to resolve the problem within 24 hours.

http://www.philstar.com/Article.aspx?articleId=554288&publicationSubCategoryId=200


Thank God I bought a a Slim.  Hopefully, luma na nga yung news item, and the issue has already been resolved.