Hm, only one of our two redundant application servers was getting bogged down, and only intermittently at that, so if the cart script in a given buyer's browser was trying to hit the affected server while load happened to be peaking on it, and if that resulted in a timeout of some operation necessary to service that cart-view request, then a "cart unavailable, back within the hour" message would have automatically popped up. Meanwhile, other cart-view requests hitting the other server, or hitting the affected server off-peak, would have seen no issue or maybe a laggy response at worst. At any rate, the issue should be cleared up now, again with our apologies for the inconvenience.