BATS Global Markets self-IPO withdrawal
Stock exchange operator BATS Global Markets was forced to withdraw its own initial public offering within minutes of trading, after a software bug disrupted trading in its own and other companies' shares, including briefly crashing Apple's stock price.
The damage was public. The root cause was preventable.
Stock exchange operator BATS Global Markets was forced to withdraw its own initial public offering within minutes of trading, after a software bug disrupted trading in its own and other companies' shares, including briefly crashing Apple's stock price.
What the software actually got wrong
A bug in BATS's IPO-auction matching software malfunctioned as soon as its own newly listed shares began trading, and rather than risk further chaos, BATS canceled all trades in its own stock and withdrew the IPO entirely.
A bug in BATS's IPO-auction matching software malfunctioned as...
A bug in BATS's IPO-auction matching software malfunctioned as soon as its own newly listed shares began trading
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.
Rather than risk further chaos, BATS canceled all trades...
rather than risk further chaos, BATS canceled all trades in its own stock and withdrew the IPO entirely
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.