The December 2022 issue of IEEE Spectrum is here!

Close bar

London Stock Exchange Goes Down Again

Outage "Only" Lasts Three and a Half Hours This Time

1 min read
London Stock Exchange Goes Down Again

The London Stock Exchange (LSE) suffered another embarrassing outage on Thursday, the 26th of November. According to news reports and the LSE itself, at 1033 local time, a "connectivity issue" required the suspension of trading in all FTSE 100 Index stocks and order-driven securities. At 1400 local time, trading was able to resume.

LSE CEO Xavier Rolet was quoted as saying: "We regret the inconvenience that today's disruption to trading has caused for our clients.  Having resolved the immediate issue, we are working hard to ensure this doesn't happen again ahead of switching to MillenniumIT's trading platform next year."

On the 9th of November, a server problem caused trading to be suspended in 1 out of every 12 stocks on the LSE; there was another but different problem that caused a short outage in October as well.

Last year,  the LSE went down for seven hours.

In September, the LSE announced plans to replace its Tradelect core trading platform  with one from Sri Lanka-based MillenniumIT, which it bought for £18 million. The LSE introduced Tradelect only two years ago after spending four years and £40 million on its development.

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