There are conflicting stories coming out of the UK concerning the IT-related problem Barclays Bank experienced on Saturday afternoon. Barclays is Europe's sixth largest bank by market value.

According to this story in ComputerWorldUK, Barclays' customers were denied access to their accounts beginning about 1200 GMT. Customers were not able to use their debit or credit cards, access ATM machines or their on-line bank accounts. Telephone banking was also said not to work.

Barclays, which refused to say specifically what caused the problem or how many customers were directly affected (according to ITPRO, Barclays has some 1,720 branches and over 15 million customers in the UK alone), stated in the ComputerWorldUK article that its IT systems were restored in about 20 minutes.

This Reuters story, however, says that the problem hit about 1230 GMT, with complaints still being reported indicating that Barclays' on-line banking was still out at 1915 GMT Saturday.

Then this story in the Wall Street Journal reported that the IT problems were caused by a power outage. It also notes that, "It is thought the problems were associated specifically with LINK ATMs, the system that connects the U.K.'s ATM network, allowing customers from various banks or building societies to use other bank's machines."

The Journal article says that LINK processes some 1 million transactions every hour from 63,000 ATMs during peak times - like a Saturday afternoon. Barclays' customers were reportedly not very happy, especially concerning the lack of information coming out of the bank about what was going on.

A Barclays spokesperson, per usual, stated that, "We apologise to our customers for the inconvenience caused."

Why the Barclays feels the need to remain so closed-mouthed about the exact cause for its IT systems' failure has not been explained, however.

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
A plate of spaghetti made from code
Shira Inbar

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