Cloud Fail

Between 9:55 AM PST to 10:20 AM PST, we experienced elevated error rates for Pay and InstallPaymentInstruction APIs. This issue been been resolved. The service is operating normally.

Between 9:55 AM PST to 10:20 AM PST, we experienced elevated error rates for Pay and InstallPaymentInstruction APIs. This issue has been resolved. The service is operating normally.

Amazon FPS will be undergoing scheduled maintenance on Nov 19, from 1:00 AM to 2:30 AM PST. During this maintenance window there will be a short period of time when requests to Pay (CC and ACH), Refund, Settle, Reserve, CreateAccount, and ASP Subscriptions will result in a 500 Internal Server Error. The Get* API calls, (GetAccountBalance, GetAccountActivity, etc.), will operate normally. We will update this dashboard when the maintenance window begins and ends. We will also update this dashboard if any issues are detected during the maintenance window.

All transactions have been processed. The service is now operating normally.

We’ve addressed the issue that caused a delay in transactions related to Pay, Reserve, and Settle requests. Most of the transactions that were impacted by this delay have been successfully processed, with a small subset still in processing. We are monitoring these closely.

We are investigating delays impacting Pay, Reserve, and Settle API requests.

To recap the above event, Amazon FPS experienced delays in processing credit card transactions today after a failure in one of our backend components impacted a part of the transaction processing workflow. Requests to process transactions via Pay and Reserve API calls were queued in our system and no data was lost during the delay. A fix was applied at 1:10 PM PDT and the service resumed processing both new and pending transactions normally. By 2:26 PM PDT all pending transactions had been processed successfully.

All credit card transactions have been processed.

This issue has been addressed and the service is operating normally for all new credit card transactions. Most of the transactions that were impacted by this event have been successfully processed, with a small subset still in processing. We are monitoring these closely.