Hardware fault causes more RBS service outages

News

Hardware fault causes more RBS service outages

Karl Flinders

Customers of Royal Bank of Scotland (RBS) and NatWest have experienced further disruptions as ATM, online and telephone banking services were hit by IT problems again.

The problems, caused by a hardware fault, began at around 10pm last night when customers reported difficulties making cash withdrawals and debit card payments as well as disruption to online and telephone banking.

RBS.jpg

RBS said in a statement: “We are disappointed that our customers have faced disruption to banking services for a period yesterday evening and apologise for that. All services are now running as normal again.”

"Between roughly 9-11pm customers were not able to access online banking and also had problems with ATM use and point of service payments,"added RBS.

This follows software issues that struck RBS, NatWest and the Ulster Bank in June which meant customers had major issues with their accounts.

The glitch in the CA7 batch process scheduler ended with 12 million customer accounts frozen. Customers were left unable to access funds for a week or more as RBS, NatWest and the Ulster Bank manually updated all the account balances.

RBS said the problems cost the bank £175m.

As a result of the software glitch, the Financial Services Authority (FSA) demanded details of how major banks planned to prevent a repeat.

RBS said the latest outage was not related to the problems last year. "This problem was caused by a hardware fault and was not related to the issues we experienced last summer. It was much easier to fix, though clearly an unacceptable failure."

 

 

 

 


Email Alerts

Register now to receive ComputerWeekly.com IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
 

COMMENTS powered by Disqus  //  Commenting policy