First National Bank (FNB) customers were unable to carry out transactions this morning, due to bank mainframe problems.
Customers unable to access ATM services became aware of the greater extent of the problem as they turned to FNB`s eBucks Internet banking portal, and then to branches, without success.
FNB said in a statement that the downtime, due to a mainframe problem, had affected its ATM network, branch transaction processing capability and online banking site. "The ATM system was inoperable for 55 minutes, while other services were impacted for approximately two hours," the bank said. The briefly-worded statement apologised for the inconvenience and said an investigation was under way to determine the cause of the service interruption.
The downed services were gradually restored, with most systems up and running just after 11am. The last service to be restored was the eBucks banking portal, which featured in the media last year when unscheduled downtime and two weeks of intermittent service at the end of September frustrated many Internet bankers.
After last year`s disruptions, eBucks took several steps, including installing increased capacity servers and more sophisticated service demand indicators to prevent a recurrence of the problem.
Share
