← Back to the 300 Software Failures Timeline
Case Study #171 — 300 Software Failure Case Studies

Sony PlayStation 3 'leap year' bug

Older-model PlayStation 3 consoles worldwide malfunctioned or became unusable for a day, disrupting games, trophies, and some non-gaming functions for millions of users.

2010-02-29
When it happened
Retail / Consumer Technology
Sector
#171 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

Older-model PlayStation 3 consoles worldwide malfunctioned or became unusable for a day, disrupting games, trophies, and some non-gaming functions for millions of users.

Retail
Sector affected
2010-02-29
Date of the event
#171
Rank in the 300 Software Failure Case Studies
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

A bug in the console's internal clock software caused it to misidentify 2010 as a leap year, an error in its date-handling logic that cascaded into failures across multiple system functions until the clock rolled over to the next day.

01Root Cause

A bug in the console's internal clock software caused...

What Happened

A bug in the console's internal clock software caused it to misidentify 2010 as a leap year, an error in its date-handling logic that cascaded into failures across multiple system functions until the clock rolled over to the next day.

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.