Just days after APRA warned the banks to lift their game regarding computer systems crashes both the Commonwealth Bank and National Australia Bank have endured extensive system failures, and a consumer tongue-lashing via the social networks.CBA's ATM and Eftpos network failed late on Tuesday night. Although CBA issued a statement yesterday morning saying that the issue had been largely fixed by 8.30am, its Facebook and Twitter pages remained abuzz regarding the lingering problems being experienced by customers throughout the day. Despite CBA's statement that all was well by breakfast-time, some customers attempting to use CBA-issued cards were still being asked to sign for purchases by major retailers in the afternoon, and details of those transactions were not automatically being updated in online statements.The bank's statement had already noted that "some customers may continue to experience difficulties when selecting the 'credit' option while using scheme debit cards such as debit MasterCard. We are working to resolve that issue as soon as possible."But the bank's social media team was sticking to the script that everything was fixed by 8.30am, even though some customers were reporting that they were still facing difficulty using their cards.In a presentation made at an IT news-organised event last week, David Pegrem, the Australian Prudential Regulation Authority's head of IT risk, warned that consumer tolerance for bank crashes was dwindling. He said the rise of social networks meant banks could no longer hide, nor could they expect to have a day or two to fix computer problems.And some of the social network commentary was very high profile. Phil Argy, well known as a mediator of high-profile ICT disputes across Australia and a former head of the Australian Computer Society, tweeted in the early hours of yesterday that NAB's online banking had been offline "for hours" and this was impacting on people's ability to make last minute Business Activity Statements payments.Neither bank is revealing what sparked this latest spate of problems. Some early reports suggested that the rollover to the once-every-four-years leap year date of 29 February may have been the trigger. Neither bank was saying yesterday - although the fact that CBA's problems started on the 28th while NAB's problems only affected some terminals suggests different root causes.For National Australia Bank this was the second time this month that the Hicaps system for medical payments processing which it operates has been offline for a lengthy period of time. In early February, NAB's ATM and Eftpos network crashed for several hours, bringing the Hicaps system down with it.A statement from the bank yesterday regarding the latest outage apologised to customers and noted that: "Due to a software issue, some health care providers using Hicaps terminals may not be able to process health insurance claims or Medicare claims at the moment." It recommended insured patients claimed their health insurance benefit via their health insurance provider.Meanwhile, the Hicaps website noted that while terminals could still be used for Eftpos, some organisations might not have been able to process health-fund claims or