O2/SoftBank Ericsson software certificate expiry outage
A software fault in network equipment supplied by Ericsson caused mobile data outages for tens of millions of customers across multiple carriers worldwide, including O2 in the UK (about 32 million customers) and SoftBank in Japan.
The damage was public. The root cause was preventable.
A software fault in network equipment supplied by Ericsson caused mobile data outages for tens of millions of customers across multiple carriers worldwide, including O2 in the UK (about 32 million customers) and SoftBank in Japan.
What the software actually got wrong
Ericsson attributed the outage to an expired software certificate in two of its software versions, an oversight in software lifecycle/configuration management that caused affected network nodes to stop processing traffic correctly once the certificate lapsed.
Ericsson attributed the outage to an expired software certificate...
Ericsson attributed the outage to an expired software certificate in two of its software versions, an oversight in software lifecycle/configuration management that caused affected network nodes to stop processing traffic correctly once the certificate lapsed.
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.
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.
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.
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.