Technical Glitches Hit Tokyo and Madrid Market Exchanges

Knight Capital saved from its “technical difficulties,” at least for now

2 min read
Technical Glitches Hit Tokyo and Madrid Market Exchanges

Both the Tokyo Stock Exchange (TSE) and Madrid Bolsas y Mercados Españoles (BME) have suffered technical glitches during the past 24 hours.  

The Japan Times is reporting that the TSE halted trading in derivatives this morning for about 95 minutes this morning. While the impact doesn’t seem to be consequential, the “systems problems” as the TSE is calling its computer glitch is yet another major embarrassment. The TSE has a history of repeated outages over the past several years, with the last one occurring in February affecting the TSE for three hours or more. The February incident cost the head of the TSE 30 percent of his salary for one month, while other executives had their pay cut by 20 percent.

In Spain, according to the Associated Press, trading at the BME was interrupted from 1005 to 1450 Madrid time yesterday. The BME would not comment on the cause of the technical difficulty, other than to say that its technicians were studying  it, reported the Financial Times of London. The BME outage, which was termed by the FT as “rare,” doesn’t appear to have caused any lasting consequences either.

In other market glitch news, over the weekend, Knight Capital was able to secure a $400 million bailout to cover the $440 million loss it suffered last week because of its out-of-control trading algorithm. Without the rescue, the brokerage would likely have gone out of business, a prospect that many apparently still think possible.

The U.S. Security and Exchange Commission (SEC) is reportedly about to “require trading firms and other market participants to disclose system failures and test computer-code changes before they go live,” in response to the Knight Capital incident, the flash crash, and several others, according to a story in the FT.

The New York Times reported last week that Knight’s “technical difficulties” were due to it rushing “to develop a computer program so it could take advantage of a new Wall Street venue for trading stocks. But the firm ran up against its deadline and failed to fully work out the kinks in its system, according to people briefed on the matter. In its debut [last] Wednesday, the software went awry, swamping the stock market with errant trades and putting Knight’s future in jeopardy.”

Let’s hope that the SEC (and Congress and the public at large) doesn’t think that a “test your code” mandate (whatever that means) is going to prevent future trading system screw-ups. At best , and assuming the trading companies invest the time, money, and expertise in the most effective testing practices possible (a big assumption to be sure when money is to be made), software-related glitches might be reduced, but they aren’t going to go away. 

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"]}