Around 19:30 UTC on Tuesday, October 24th 2017, and for a period of about two hours, Spreedly returned 500 response codes for requests to list created gateways and requests to show or list transactions. This was due to maintenance work on a secondary data store that resulted in an individual query running for much longer than expected. At no point were revenue-affecting endpoints down or inaccessible.
We’ll be evaluating and adjusting our practices to accurately determine the activity and performance of queries to our secondary data store to ensure a clear understanding of our current load before performing maintenance. Additionally, we’ll be updating our documentation to distinguish the differences between our revenue-affecting API endpoints and secondary concerns such as reporting to provide more clarity on the specific impact of degraded API performance.
At Spreedly, our priority is to ensure you are able to collect money from your customers and execute the financial transactions that power your business. We prioritize the uptime of revenue-affecting API calls over other secondary concerns like reporting and visualization, though we also acknowledge that many businesses do rely on these abilities for some of their business processes. While we don’t consider the endpoints in this incident to not be revenue-affecting, we realize it had the potential to disrupt to transaction flow given the specific integration points with Spreedly and apologize for the inconvenience posed by their degradation.