Datacenterknowledge.com has more information about last the outage experienced by Chase.com. One of the most telling comments is "The company said its web site crashed Monday evening when a third party vendor’s database software corrupted the log-in process."Now, where I come from if your web site blows up you take responsibility for it and don't go pointing fingers at 3P's (including CDN's - think you may have a problem with 1? Then execute agreements with 3). Pointing fingers at Oracle is just bad form. Chase selected the database and operates it - one would presume that (a) they would have at least one form of redundancy, (b) they would have done much better end-to-end testing and (c) would have been able to fail-over to their standby systems much faster than 12+ hours.
Still pisses me off their their CS folks vacillate between "it was a failure" and "it was scheduled outage".