9:00am Pacific / 4:00pm GMT — Our engineers have confirmed that the issues were due to slow responsiveness from a centralized database.  They have addressed the problem, and message processing is returning to normal levels.  The operations team is working to assess the cause of the database issue so that we can take corrective action as appropriate.