The NYSE's Year of Living Dangerously Ends With Yet Another Glitch

In fact, officials at several stock exchanges around the world promise – again – to contain operational risks

2 min read
The NYSE's Year of Living Dangerously Ends With Yet Another Glitch

In an apropos finale, the New York Stock Exchange suffered one last trading glitch on New Year’s Eve.  According to Dow Jones Business News, the NYSE issued “an alert to traders at 3:19 p.m. EST that its equity market was experiencing an issue with one of its engines that matches ‘buy’ and ‘sell’ orders and that 26 issues were affected, including BBX Capital Corp. (BBX), Verso Paper Corp. (VRS) and TransAlta Corp. (TAC).”

Although the trading problem was fixed within five minutes, it served to remind everyone of a year of trading-related snafus not only at the NYSE ( August, November), but also at the Johannesburg Stock Exchange (January), the SIX Swiss Exchange (January), the Tokyo Stock Exchange (February,  August), the BATS exchange (March),  the Madrid Stock Exchange (August), Indonesia’s Stock Exchange (August),  the Nasdaq (August, October, November,December,  Australia’s Stock Exchange (October),  India’s National Stock Exchange (October), Sweden’s Stock Exchange - which is operated by Nasdaq OMX - (November), and the Chicago Mercantile Exchange Group  (December), to name only a few.

There was also the infamous August Knightmare on Wall Street, where “zombie software” caused market-maker Knight Capital Group  to lose some US $440 million in about 45 minutes.  Knight Capital had to seek financial help to avoid bankruptcy, and was sold last month to Getco Holding Company LLC for $1.4 billion, one of the firms that financed Knight during its troubles. Knight Capital’s CEO Thomas Joyce conveniently and disingenuously blamed the firm's problem on “knuckleheads” in his IT department.

Last year was supposed to be a year when the world’s stock exchanges were going to clean up their acts, given that, according to the Financial Times, there were over 20 European exchange incidents alone in 2011. But 2012 seemed to be a lost year in that regard.

A story at the Wall Street Journal today reported the exchanges and market participants are promising (again) that this year they really are going to manage their operational risks better. For example, next month a pilot program is being rolled out to strengthen market-circuit breakers, and there will be limits imposed on how much a stock will be allowed to change in their average price within a 5-minute interval.  The U.S. Security and Exchange Commission, which approved the above changes, is also creating a tracking system for U.S. stock activity to help it quickly audit what happens when something goes awry.

The fixes are meant to help convince ordinary investors (and professional traders) that the exchanges haven’t grown too complex to manage, but the changes may be water off a duck’s back at least for the many ordinary investors who, after the great stock sell-off of 2008 and the continued world economic turmoil including the on-going US fiscal cliff brinksmanship, no longer trust the markets.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}