DBS Bank Singapore repeated digital-banking outages
Singapore's largest bank suffered at least five major digital-banking outages between late 2021 and late 2023, repeatedly locking customers out of online banking, PayLah! and PayNow; regulators eventually raised DBS's capital requirements to roughly S$1.6 billion and, in late 2023, barred the bank from new business acquisitions and IT changes for six months.
The damage was public. The root cause was preventable.
Singapore's largest bank suffered at least five major digital-banking outages between late 2021 and late 2023, repeatedly locking customers out of online banking, PayLah! and PayNow; regulators eventually raised DBS's capital requirements to roughly S$1.6 billion and, in late 2023, barred the bank from new business acquisitions and IT changes for six months.
What the software actually got wrong
Singapore's Monetary Authority found DBS's IT systems and recovery processes were not resilient enough to restore critical digital services quickly; specific incidents were traced to problems including a malfunctioning access-control server, and MAS's review pointed to broader weaknesses in the bank's system architecture, change-management practices and technical recovery capability rather than any single one-off bug.
Singapore's Monetary Authority found DBS's IT systems and recovery...
Singapore's Monetary Authority found DBS's IT systems and recovery processes were not resilient enough to restore critical digital services quickly
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.
Specific incidents were traced to problems including a malfunctioning...
specific incidents were traced to problems including a malfunctioning access-control server
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
MAS's review pointed to broader weaknesses in the bank's...
MAS's review pointed to broader weaknesses in the bank's system architecture, change-management practices and technical recovery capability rather than any single one-off bug
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
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.