NYSE Consolidated Tape Association price-band software glitch
A New York Stock Exchange technical glitch briefly halted trading in about 40 stocks and showed Berkshire Hathaway's Class A shares erroneously collapsing 99.97% in value, from $627,400 to $185.10, before trading resumed and prices fully recovered.
The damage was public. The root cause was preventable.
A New York Stock Exchange technical glitch briefly halted trading in about 40 stocks and showed Berkshire Hathaway's Class A shares erroneously collapsing 99.97% in value, from $627,400 to $185.10, before trading resumed and prices fully recovered.
What the software actually got wrong
The Consolidated Tape Association, whose systems (run by an NYSE subsidiary) publish the industry-wide reference 'price bands' used to trigger volatility trading halts, rolled out a new software release that miscalculated those bands for dozens of tickers; NYSE resolved it by switching over to a backup data center running the prior software version.
The Consolidated Tape Association, whose systems (run by an...
The Consolidated Tape Association, whose systems (run by an NYSE subsidiary) publish the industry-wide reference 'price bands' used to trigger volatility trading halts, rolled out a new software release that miscalculated those bands for dozens of tickers
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.
NYSE resolved it by switching over to a backup...
NYSE resolved it by switching over to a backup data center running the prior software version
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.