5xx Responses
Incident Report for Spreedly
Resolved
At 12:05, we saw timeouts from a decryption service running on one of our servers, which caused Core to return 5xx responses for ~38 transactions over a period of ~15 seconds.

The server is having storage capacity added, and since the decryption service runs completely in-memory, the drive reconfiguration was not expected to have any effect on it. Clearly it did, and going forward we will ensure that the decryption service on a server being grown is taken out of rotation so that this does not happen again.

We know that every transaction counts for your business, and we apologize if you were affected by these errors. As always, if you have any questions or concerns, please contact success@spreedly.com.
Posted about 1 year ago. Nov 02, 2017 - 13:57 EDT