These are all normal transactions that usually post fairly promptly (or when expected, like the CC points) and these are all automatic processes - given it's for many disparate transaction types/sources, I am going to guess the actual activities are registered within the system (by that I mean, for example, QF Premier Card points updates are coming in as they should) but the bottleneck is in the actual posting to the activity statement/record. Without knowing anything about the internals there that's just a guess. None of this should involve human interaction though as they're all common well automated processes (and IF human involvement is somehow required, that would be an incredible indictment on the IT area imo).
What worries me more, with a tinfoil hat on, is that when things like this happen that indicates potential changes afoot.. er I mean.. enhancements. Now usually this involves the website per se, but well... who knows.
Mostly though I just think there's some sort of proecssing fart going on in the back end. Probably some job crashing out and maybe having to be restarted while a Root Cause Analysis is done and a fix put in. That seems the most plausible to me looking in as a total outsider.