UniSuper/Google Cloud account deletion
Google Cloud accidentally deleted the entire private cloud account of UniSuper, an Australian pension fund managing over $125 billion for more than 600,000 members, locking members out of their accounts for about two weeks.
The damage was public. The root cause was preventable.
Google Cloud accidentally deleted the entire private cloud account of UniSuper, an Australian pension fund managing over $125 billion for more than 600,000 members, locking members out of their accounts for about two weeks.
What the software actually got wrong
A misconfiguration during the provisioning of UniSuper's private cloud service caused Google's systems to set the subscription to automatically expire and delete after a fixed period rather than persist indefinitely, and when it expired the deletion cascaded across both of UniSuper's geographically separate backup regions simultaneously.
A misconfiguration during the provisioning of UniSuper's private cloud...
A misconfiguration during the provisioning of UniSuper's private cloud service caused Google's systems to set the subscription to automatically expire and delete after a fixed period rather than persist indefinitely
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.
When it expired the deletion cascaded across both of...
when it expired the deletion cascaded across both of UniSuper's geographically separate backup regions simultaneously
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.
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.