AfterDawn: News

Fixed! Sony repairs PS3 glitch, gamers can access PSN again

One of the most popular stories of the day has been the ongoing PlayStation 3 glitch which has blocked gamers from accessing the online PlayStation Network.

Sony promised a fix within 24 hours and has delivered, repairing the glitch and giving users access again to the Internet from their consoles.



The official reason for the bug was problems with the internal clock on older "fat" PS3 consoles. Affected models recognized 2010 as a leap year, which it is not.

"Having the internal clock date change from February 29 to March 1 (both GMT), we have verified that the symptoms are now resolved and that users are able to use their PS3 normally," writes Sony.

As a last resort, the company had told affected gamers to not turn their PS3s on, or risk losing data and trophies.

Written by: Andre Yoskowitz @ 1 Mar 2010 23:50

• Previous article

• European Commission clears Orange, T-Mobile merger

• Next article

• Google acquires Picnik, cloud photo editing

• 14 comments

• jony218

  I knew "the man" wasn't going to let us down. He can be very resourceful when "profit" is at stake. I take my hat off to "the man", job well done.

  2.3.2010 00:01 #1

• cleverick

  Originally posted by jony218: I knew "the man" wasn't going to let us down. He can be very resourceful when "profit" is at stake. I take my hat off to "the man", job well done.
  Yep and hats off to the tech people fixing the issue.

  2.3.2010 00:17 #2

• etan1085

  Hat's off to the techies, however this should not have been a problem to begin with.

  2.3.2010 00:20 #3

• djeazyg

  Originally posted by etan1085: Hat's off to the techies, however this should not have been a problem to begin with.Nothing is perfect.

  2.3.2010 01:17 #4

• xnonsuchx

  Originally posted by djeazyg: Originally posted by etan1085: Hat's off to the techies, however this should not have been a problem to begin with.Nothing is perfect.I beg to differ...not that nothing is perfect, but that this really shouldn't have been a problem. Programming date calculations (especially post-Y2K) incorrectly is just outright lazy/incompetent work. It was stupid when the Zune had it; it was stupid in this case too (though it didn't require factory resetting your PS3, at least).

  2.3.2010 01:28 #5

• dstbd

  i beg to differ with most of you, sony didnt fix a thing, the ps3 itself found a date that worked, the date is wrong, sony havent done anything, and the internall clock is still buggered... so no, i dont give creds to sony for this :P they got lucky!
  
  so for all we know this can happen again next month...

  2.3.2010 07:22 #6

• vidsteve

  wait , wait , wait...they promised a fix within 24 hrs. ? and the problem was with the clock right??? They didint do shit but wait for the clock to tick over. They could not have changed the code and sent out an update to all of the older PS3s that quickly unless A. they knew of the problem and just waited to see what would happen , or B. They just waited for the clock to click over to the next day and hope that it rights itself via the internet clock and not have to pay a Butt Load of $$$ to re write code , etc.!!

  2.3.2010 11:23 #7

• kikzm33z

  Quote:Originally posted by djeazyg: Originally posted by etan1085: Hat's off to the techies, however this should not have been a problem to begin with.Nothing is perfect.I beg to differ...not that nothing is perfect, but that this really shouldn't have been a problem. Programming date calculations (especially post-Y2K) incorrectly is just outright lazy/incompetent work. It was stupid when the Zune had it; it was stupid in this case too (though it didn't require factory resetting your PS3, at least).The 360 got heavy RROD incidents at RELEASE, which shouldn't happen, not at 30% chance of failing and yet people still tolerate it.
  
  TBH, one day without a PS3 is do-able.

  2.3.2010 13:19 #8

• xnonsuchx

  Originally posted by dstbd: i beg to differ with most of you, sony didnt fix a thing, the ps3 itself found a date that worked, the date is wrong, sony havent done anything, and the internall clock is still buggered... so no, i dont give creds to sony for this :P they got lucky!
  
  so for all we know this can happen again next month...Next month is a leap year month in some years??? ;-)

  2.3.2010 16:56 #9

• dstbd

  Quote:Originally posted by dstbd: i beg to differ with most of you, sony didnt fix a thing, the ps3 itself found a date that worked, the date is wrong, sony havent done anything, and the internall clock is still buggered... so no, i dont give creds to sony for this :P they got lucky!
  
  so for all we know this can happen again next month...Next month is a leap year month in some years??? ;-)you know what i mean, they did not fix the internal clock, godknows what more bugs awaits ;)

  2.3.2010 19:38 #10

• xnonsuchx

  Quote:Quote:Originally posted by dstbd: i beg to differ with most of you, sony didnt fix a thing, the ps3 itself found a date that worked, the date is wrong, sony havent done anything, and the internall clock is still buggered... so no, i dont give creds to sony for this :P they got lucky!
  
  so for all we know this can happen again next month...Next month is a leap year month in some years??? ;-)you know what i mean, they did not fix the internal clock, godknows what more bugs awaits ;)The actual fix should be in the next 1 or 2 firmware updates...for something that was going to rectify itself in 24 hours, it wasn't worth the risk of pushing out a quick, not-fully-tested emergency update that people would have to download on a computer and put on a flash drive to update the PS3.
  
  Some of us are still waiting for them to fix the HDMI glitches introduced w/ FW 3.10.

  2.3.2010 19:50 #11

• MasterHan

  Anyone else have their blu-ray drive go out after the leap year glitch? Mine worked find the day before all the shenanigans and then decided to quit working the day after. The disk will spin but nothing comes up on the XMB.

  3.3.2010 21:46 #12

• bosnian69 (unverified)

  Originally posted by jony218: I knew "the man" wasn't going to let us down. He can be very resourceful when "profit" is at stake. I take my hat off to "the man", job well done. Originally posted by vidsteve: wait , wait , wait...they promised a fix within 24 hrs. ? and the problem was with the clock right??? They didint do shit but wait for the clock to tick over. They could not have changed the code and sent out an update to all of the older PS3s that quickly unless A. they knew of the problem and just waited to see what would happen , or B. They just waited for the clock to click over to the next day and hope that it rights itself via the internet clock and not have to pay a Butt Load of $$$ to re write code , etc.!!
  it dosent matter all thats important is that its fixed

  22.4.2011 09:30 #13

• Jemborg

  Originally posted by dstbd: i beg to differ with most of you, sony didnt fix a thing, the ps3 itself found a date that worked, the date is wrong, sony havent done anything, and the internall clock is still buggered... so no, i dont give creds to sony for this :P they got lucky!
  
  so for all we know this can happen again next month... Hey, you were right! LOL
  
  
  

  Its a lot easier being righteous than right.
  
  
  

  22.4.2011 12:39 #14