TSB 2018: The Core-Banking Migration That Locked Out Millions of Customers
TSB's 2018 migration moved customer data successfully to Proteo4UK, but the new platform immediately suffered severe technical failures that disrupted banking for millions.
Theo Mercer is the editorial pen name used for research and historical synthesis published by the CodeHistory Research Desk. Articles are sourced, reviewed, and revised according to CodeHistory’s published research standards.
TSB's 2018 migration moved customer data successfully to Proteo4UK, but the new platform immediately suffered severe technical failures that disrupted banking for millions.
Nasdaq's 2013 SIP outage combined extreme reconnect traffic with a latent redundancy flaw, halting trading in Nasdaq-listed U.S. stocks for roughly three hours.
Robinhood's March 2020 outages were widely rumored to involve a leap-year bug, but the company and FINRA identified overloaded infrastructure, cascading failures, and inadequate capacity planning instead.
Knight Capital's 2012 deployment left old code active on one server, causing its router to flood U.S. markets with millions of erroneous orders and create a loss of hundreds of millions of dollars.
RBS' 2012 outage began with a batch-scheduler software upgrade and an untested rollback to an incompatible version, disrupting account updates for millions of customers.
Nasdaq's Facebook IPO opening exposed a design loop in the IPO cross, a testing-scale mismatch, and operational decisions that left tens of thousands of orders stuck for hours.
BATS' first corporate IPO on its own exchange failed when new auction software drove a matching engine into an infinite loop, making its own symbol and other stocks inaccessible.
Bank of New York's 1985 securities-processing failure let incoming Treasury deliveries pile up without matching redeliveries, producing a historic Fed overdraft and overnight emergency loan.
TAURUS was meant to modernize London's share settlement after Big Bang, but scope, timetable, stakeholder complexity, and repeated redesigns turned it into a landmark failed IT program.
Mizuho Securities' 2005 J-COM order error combined a dangerous order-entry workflow with a Tokyo Stock Exchange cancellation defect, turning one mistyped trade into a major market incident.